Am 12.05.2016 um 21:46 schrieb Chris Friesen:
So...anyone have any ideas why this isn't working?  Is it because I'm
trying to use the "eth" namespace which could possibly collide with the
kernel naming?

likely yes

the config below has a reason while using network.service and classical ifcfg-files

[root@srv-rhsoft:~]$ ifconfig | grep flags
br-guest: flags=67<UP,BROADCAST,RUNNING>  mtu 1500
br-lan: flags=4675<UP,BROADCAST,RUNNING,ALLMULTI,MULTICAST>  mtu 1500
br-wan: flags=67<UP,BROADCAST,RUNNING>  mtu 1500
lan-guest: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
lan-phone: flags=67<UP,BROADCAST,RUNNING>  mtu 1500
lan-spare: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
lan-tv: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
vmnet1: flags=67<UP,BROADCAST,RUNNING>  mtu 1500
vmnet8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
vpn-client: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1472
vpn-server: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
wan: flags=67<UP,BROADCAST,RUNNING>  mtu 1500
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
wlan1: flags=67<UP,BROADCAST,RUNNING>  mtu 1500

Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Reply via email to