summaryrefslogtreecommitdiff
path: root/system-dummy.c
diff options
context:
space:
mode:
authorMatthias Schiffer <mschiffer@universe-factory.net>2017-02-10 06:30:17 +0100
committerFelix Fietkau <nbd@nbd.name>2017-02-11 21:48:38 +0100
commit6397f5edb977b5963aa8eec1deaa709355bbbc7d (patch)
treee8e8bf3c162794e574e458b06a3b9d6d8c2c0afb /system-dummy.c
parent6228d0f21b2dcf20d7b2223c43f8b90b9b51bc4d (diff)
downloadnetifd-6397f5edb977b5963aa8eec1deaa709355bbbc7d.tar.gz
device: add veth support
The veth config code mostly handles the primary interface of a veth pair, the secondary interface is not explicitly referenced and will be found as an unrelated interface after the pair has been created. This doesn't only allow us to keep the veth code simple (and similar to existing device handlers), but will also avoid complicating handling unnecessarily in case the secondary interface is moved into another network namespace. Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Diffstat (limited to 'system-dummy.c')
-rw-r--r--system-dummy.c10
1 files changed, 10 insertions, 0 deletions
diff --git a/system-dummy.c b/system-dummy.c
index 2ea25ac..165438c 100644
--- a/system-dummy.c
+++ b/system-dummy.c
@@ -281,6 +281,16 @@ int system_macvlan_del(struct device *macvlan)
return 0;
}
+int system_veth_add(struct device *veth, struct veth_config *cfg)
+{
+ return 0;
+}
+
+int system_veth_del(struct device *veth)
+{
+ return 0;
+}
+
int system_vlandev_add(struct device *vlandev, struct device *dev, struct vlandev_config *cfg)
{
return 0;