Hi, I struggled long to migrate fully from initd to systemd. Now before I do the step from 12.3 to 13.2, i have concerns of ifup being replaced. Not much answers found googling around. A. can ifup be used instead of wicked B. is migration easy? following setup (IPv4 only): 2 physical network cards (RTL8111/8168) eth0: LAN (DHCPd running on the machine) eth1: (static ip) as connection to VDSL2 modem dsl0: PPPoE dial-up device lo tun0: openvpn server running tun1: vpnc connection (manually created on demand using vpnc) isdn0: backup ISDN dial-in connection (started manually) modem0: backup UMTS dial-in connection (started manually) C. firewall configuration I adjusted SuSEfirewall2 configuration a lot (routing,masquerading,forwarding,...) and added custom scripts for traffic shaping using tc and iptables. have i take care of anything regarding this?
Thank's a lot in advance for any info/hints. It is very hard to find information about, especially point C.
Regards, Paul
В Tue, 11 Nov 2014 16:06:29 +0100 (CET) Paul Neuwirth mail@paul-neuwirth.de пишет:
Hi, I struggled long to migrate fully from initd to systemd. Now before I do the step from 12.3 to 13.2, i have concerns of ifup being replaced.
How is it related to systemd?
Notmuch answers found googling around. A. can ifup be used instead of wicked
As far as I know - not officially. You may be able to removed wicked and install sysconfig back, but I did not look how difficult it is (I use NM).
B. is migration easy? following setup (IPv4 only): 2 physical network cards (RTL8111/8168) eth0: LAN (DHCPd running on the machine) eth1: (static ip) as connection to VDSL2 modem dsl0: PPPoE dial-up device lo tun0: openvpn server running
That may be a problem, someone recently posted that tunX interfaces were not activated by wicked on startup.
tun1: vpnc connection (manually created on demand using vpnc) isdn0: backup ISDN dial-in connection (started manually) modem0: backup UMTS dial-in connection (started manually) C. firewall configuration I adjusted SuSEfirewall2 configuration a lot (routing,masquerading,forwarding,...) and added custom scripts for traffic shaping using tc and iptables. have i take care of anything regarding this?
I believe that firewall does not depend on underlying networking implementation, but I may be wrong here.
Thank's a lot in advance for any info/hints. It is very hard to find information about, especially point C.
Regards, Paul
On Tuesday 2014-11-11 16:31, Andrei Borzenkov wrote:
Date: Tue, 11 Nov 2014 16:31:51 From: Andrei Borzenkov arvidjaar@gmail.com To: opensuse@opensuse.org Subject: Re: [opensuse] migration from openSUSE 12.3 to 13.2 - from ifup to wicked
В Tue, 11 Nov 2014 16:06:29 +0100 (CET) Paul Neuwirth mail@paul-neuwirth.de пишет:
Hi, I struggled long to migrate fully from initd to systemd. Now before I do the step from 12.3 to 13.2, i have concerns of ifup being replaced.
How is it related to systemd?
No relation, just mentioned I have concerns doing such "big steps".
B. is migration easy? following setup (IPv4 only): 2 physical network cards (RTL8111/8168) eth0: LAN (DHCPd running on the machine) eth1: (static ip) as connection to VDSL2 modem dsl0: PPPoE dial-up device lo tun0: openvpn server running
That may be a problem, someone recently posted that tunX interfaces were not activated by wicked on startup.
do you mean http://lists.opensuse.org/opensuse-factory/2014-11/msg00207.html luckily that doesn't seem to be unsolvable.
tun1: vpnc connection (manually created on demand using vpnc) isdn0: backup ISDN dial-in connection (started manually) modem0: backup UMTS dial-in connection (started manually) C. firewall configuration I adjusted SuSEfirewall2 configuration a lot (routing,masquerading,forwarding,...) and added custom scripts for traffic shaping using tc and iptables. have i take care of anything regarding this?
I believe that firewall does not depend on underlying networking implementation, but I may be wrong here.
I read opensuse uses a wicked extension as firewall. Maybe i should build up a test machine. but hard to test the corresponding scenarios on a different machine.
Thanks Paul
* Paul Neuwirth mail@paul-neuwirth.de [11-11-14 10:46]: [...]
I read opensuse uses a wicked extension as firewall. Maybe i should build up a test machine. but hard to test the corresponding scenarios on a different machine.
And then there is VirtualBox....
Hi, I struggled long to migrate fully from initd to systemd. Now before I do the step from 12.3 to 13.2, i have concerns of ifup being replaced. Not much answers found googling around. B. is migration easy? following setup (IPv4 only): 2 physical network cards (RTL8111/8168) eth0: LAN (DHCPd running on the machine) eth1: (static ip) as connection to VDSL2 modem dsl0: PPPoE dial-up device lo tun0: openvpn server running tun1: vpnc connection (manually created on demand using vpnc) isdn0: backup ISDN dial-in connection (started manually) modem0: backup UMTS dial-in connection (started manually)
Regards, Paul
Hallo, back to this topic, as support for 12.3 ended, I am now testing wicked on a similair testing machine. I struggle at the first step: I cannot setup a network interface with static ip. Yast does not mention an error. But the interface does not get up with static ip. generated config by yast:
/etc/sysconfig/network/ifcfg-enp5s0 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='172.19.0.1/24' MTU='' NAME='NetXtreme BCM5721 Gigabit Ethernet PCI Express' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto'
wicked output: # wicked --log-level debug ifup enp5s0 wicked: __ni_config_parse_ifconfig_source: Adding ifconfig firmware: wicked: __ni_config_parse_ifconfig_source: Adding ifconfig compat: wicked: __ni_config_parse_ifconfig_source: Adding ifconfig wicked:/etc/wicked/ifconfig wicked: trying to discover netif config via firmware service "ibft" wicked: ni_netconfig_firmware_discovery: buffer has 0 bytes wicked: ni_ifconfig_read_firmware: location: firmware:, line: 0 wicked: ni_sysconfig_read(/etc/sysconfig/network/config) wicked: ni_sysconfig_read(/etc/sysconfig/network/dhcp) wicked: Reading sysctl file '/etc/sysctl.conf' wicked: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-lo) wicked: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-enp4s0) wicked: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-enp5s0) wicked: ni_compat_generate_interfaces: location: compat:/etc/sysconfig/network/ifcfg-lo, line: 0 wicked: ni_compat_generate_interfaces: location: compat:/etc/sysconfig/network/ifcfg-enp4s0, line: 0 wicked: ni_compat_generate_interfaces: location: compat:/etc/sysconfig/network/ifcfg-enp5s0, line: 0 wicked: No valid configuration files found at /etc/wicked/ifconfig wicked: device enp5s0: operation timed out enp5s0 setup-in-progress
??
thanks for any hints, Paul
Paul Neuwirth wrote:
Hallo, back to this topic, as support for 12.3 ended, I am now testing wicked on a similair testing machine. I struggle at the first step: I cannot setup a network interface with static ip. Yast does not mention an error. But the interface does not get up with static ip. generated config by yast:
/etc/sysconfig/network/ifcfg-enp5s0 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='172.19.0.1/24' MTU='' NAME='NetXtreme BCM5721 Gigabit Ethernet PCI Express' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto'
After testing/preparing it for a few weeks, I only just yesterday switched our main router/firewall to 13.2. I have 5 static interfaces, I see no problems - sofar :-)
Here's one example config, looks a lot like yours:
BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.2.7/21' MTU='' NAME='NetXtreme BCM5703X Gigabit Ethernet' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' IPADDR_='2001:8e0:2010:1ff::1:1/64'
wicked: device enp5s0: operation timed out enp5s0 setup-in-progress
??
Is the cable plugged in?
Paul Neuwirth composed on 2015-03-02 08:53 (UTC+0100):
I struggled long to migrate fully from initd to systemd. Now before I do the step from 12.3 to 13.2, i have concerns of ifup being replaced. Not much answers found googling around. B. is migration easy? following setup (IPv4 only): 2 physical network cards (RTL8111/8168) eth0: LAN (DHCPd running on the machine) eth1: (static ip) as connection to VDSL2 modem dsl0: PPPoE dial-up device lo tun0: openvpn server running tun1: vpnc connection (manually created on demand using vpnc) isdn0: backup ISDN dial-in connection (started manually) modem0: backup UMTS dial-in connection (started manually)
back to this topic, as support for 12.3 ended, I am now testing wicked on a similair testing machine. I struggle at the first step: I cannot setup a network interface with static ip. Yast does not mention an error. But the interface does not get up with static ip. generated config by yast:
/etc/sysconfig/network/ifcfg-enp5s0
You don't need to use bizarro NIC names like enp5s0 if you don't want. IOW, if you want eth0 & eth1, use net.ifnames=0 on your kernel cmdline or /etc/udev/rules.d/80-net-setup-link.rules or one of the other avoidance configs from the bottom of http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface...
BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='172.19.0.1/24' MTU='' NAME='NetXtreme BCM5721 Gigabit Ethernet PCI Express' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto'
The fixed IP 13.3/13.2 box I currently have booted only has 5 non-null lines: BOOTPROTO BROADCAST IPADDR NAME STARTMODE='onboot'
wicked output: # wicked --log-level debug ifup enp5s0 wicked: __ni_config_parse_ifconfig_source: Adding ifconfig firmware: wicked: __ni_config_parse_ifconfig_source: Adding ifconfig compat: wicked: __ni_config_parse_ifconfig_source: Adding ifconfig wicked:/etc/wicked/ifconfig wicked: trying to discover netif config via firmware service "ibft" wicked: ni_netconfig_firmware_discovery: buffer has 0 bytes wicked: ni_ifconfig_read_firmware: location: firmware:, line: 0 wicked: ni_sysconfig_read(/etc/sysconfig/network/config) wicked: ni_sysconfig_read(/etc/sysconfig/network/dhcp) wicked: Reading sysctl file '/etc/sysctl.conf' wicked: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-lo) wicked: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-enp4s0) wicked: ni_sysconfig_read(/etc/sysconfig/network/ifcfg-enp5s0) wicked: ni_compat_generate_interfaces: location: compat:/etc/sysconfig/network/ifcfg-lo, line: 0 wicked: ni_compat_generate_interfaces: location: compat:/etc/sysconfig/network/ifcfg-enp4s0, line: 0 wicked: ni_compat_generate_interfaces: location: compat:/etc/sysconfig/network/ifcfg-enp5s0, line: 0 wicked: No valid configuration files found at /etc/wicked/ifconfig wicked: device enp5s0: operation timed out enp5s0 setup-in-progress
thanks for any hints,
Does /etc/udev/rules.d/70-persistent-net.rules exist with non-zero size, with content including enp5s0 or eth0 or eth1?
What's your output from ifconfig -a?
On Monday 2015-03-02 09:11, Per Jessen wrote:
After testing/preparing it for a few weeks, I only just yesterday switched our main router/firewall to 13.2. I have 5 static interfaces, I see no problems - sofar :-)
Here's one example config, looks a lot like yours:
BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.2.7/21' MTU='' NAME='NetXtreme BCM5703X Gigabit Ethernet' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' IPADDR_='2001:8e0:2010:1ff::1:1/64'
wicked: device enp5s0: operation timed out enp5s0 setup-in-progress
??
Is the cable plugged in?
plugged in. now working. i also managed to get openvpn work and could dial in via pppoe (using this great manual: https://forums.opensuse.org/showthread.php/502199-UPGRADING-REMOVES-PPPOE- ) enp4s0 Link encap:Ethernet HWaddr 00:0E:B6:29:4F:60 inet addr:172.18.0.3 Bcast:172.18.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9919 errors:0 dropped:528 overruns:0 frame:0 TX packets:5730 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2162570 (2.0 Mb) TX bytes:1333701 (1.2 Mb) Interrupt:6
enp5s0 Link encap:Ethernet HWaddr 00:0E:B6:29:4F:61 inet addr:172.19.0.1 Bcast:172.19.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1353 errors:0 dropped:0 overruns:0 frame:0 TX packets:43 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:279771 (273.2 Kb) TX bytes:2754 (2.6 Kb) Interrupt:5
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:336 (336.0 b) TX bytes:336 (336.0 b)
ppp0 Link encap:Point-to-Point Protocol inet addr:92.79.27.69 P-t-P:82.82.6.200 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1488 Metric:1 RX packets:1277 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:237368 (231.8 Kb) TX bytes:54 (54.0 b)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:172.17.0.1 P-t-P:172.17.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
this now looks quiet similiar to what I have on 12.3: dsl0 Link encap:Point-to-Point Protocol inet addr:92.79.27.69 P-t-P:82.82.6.200 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1488 Metric:1 RX packets:24745 errors:0 dropped:0 overruns:0 frame:0 TX packets:23320 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:21615463 (20.6 Mb) TX bytes:13421697 (12.7 Mb)
eth0 Link encap:Ethernet HWaddr 94:0C:6D:80:6E:34 inet addr:172.18.0.1 Bcast:172.18.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:14734369 errors:0 dropped:4 overruns:0 frame:0 TX packets:10360402 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:13369312130 (12749.9 Mb) TX bytes:7588754967 (7237.2 Mb)
eth1 Link encap:Ethernet HWaddr 48:5B:39:CA:14:4A inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9072592 errors:0 dropped:0 overruns:0 frame:0 TX packets:7271748 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:7638837699 (7284.9 Mb) TX bytes:3771938242 (3597.2 Mb)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:969211 errors:0 dropped:0 overruns:0 frame:0 TX packets:969211 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1232251670 (1175.1 Mb) TX bytes:1232251670 (1175.1 Mb)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:172.17.0.1 P-t-P:172.17.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:4422586 errors:0 dropped:0 overruns:0 frame:0 TX packets:2287687 errors:0 dropped:127 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:5424942159 (5173.6 Mb) TX bytes:146516942 (139.7 Mb)
I hope there won't be problems with asterisk and CAPI on 13.2 - I do not have a second AVM B1 controller to test.
Thanks a lot for your help.
Paul
Felix Miata wrote:
[snip]
You don't need to use bizarro NIC names like enp5s0 if you don't want. IOW, if you want eth0 & eth1, use net.ifnames=0 on your kernel cmdline or /etc/udev/rules.d/80-net-setup-link.rules or one of the other avoidance configs from the bottom of
It's also very easy to set up with yast.
On Monday 2015-03-02 09:52, Felix Miata wrote:
Does /etc/udev/rules.d/70-persistent-net.rules exist with non-zero size, with content including enp5s0 or eth0 or eth1?
file exists zero-sized.
What's your output from ifconfig -a?
after plugging in a cable/switch the interface came up (ifup never claimed that?) # ifconfig -a enp4s0 Link encap:Ethernet HWaddr 00:0E:B6:29:4F:60 inet addr:172.18.0.3 Bcast:172.18.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:10347 errors:0 dropped:596 overruns:0 frame:0 TX packets:5895 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2212013 (2.1 Mb) TX bytes:1401585 (1.3 Mb) Interrupt:6
enp5s0 Link encap:Ethernet HWaddr 00:0E:B6:29:4F:61 inet addr:172.19.0.1 Bcast:172.19.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1420 errors:0 dropped:0 overruns:0 frame:0 TX packets:68 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:294744 (287.8 Kb) TX bytes:4354 (4.2 Kb) Interrupt:5
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:4 errors:0 dropped:0 overruns:0 frame:0 TX packets:4 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:336 (336.0 b) TX bytes:336 (336.0 b)
tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:172.17.0.1 P-t-P:172.17.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
thank you :)
On 03/02/2015 12:52 AM, Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
That said, I can't remember how I ended up with old-school names on my fresh install of 13.2 laptop, but I did, and didn't bother to change it.
John Andersen wrote:
On 03/02/2015 12:52 AM, Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
Even if I look directly at the port and it is numbered, I am unable to work out which bizarro name it is likely to have. Except for desktops and laptops (which both typically have only one interface), I always rename to ethX.
On 03/02/2015 10:46 AM, Per Jessen wrote:
Even if I look directly at the port and it is numbered, I am unable to work out which bizarro name it is likely to have. Except for desktops and laptops (which both typically have only one interface), I always rename to ethX.
Well I guess that's what permanent markers were invented for. Regardless of name scheme chosen, you don't want to be opening the case, to check chip-set. So I do that once, get out pen, done.
At least we only have a few fake (software) adaptors to ignore. The last time I ran ipconfig in a windows box I was agast.
John Andersen composed on 2015-03-02 10:15 (UTC-0800):
Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
Oh? Maybe you can "just look" if the machine is freestanding, the end(s) of the cable(s) is/are visible, and/or the cover is easily opened, but many are not so when the need or desire arises.
On Mon, Mar 2, 2015 at 1:15 PM, John Andersen jsamyth@gmail.com wrote:
On 03/02/2015 12:52 AM, Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
That said, I can't remember how I ended up with old-school names on my fresh install of 13.2 laptop, but I did, and didn't bother to change it.
Add net.ifnames=0 to your grub configuation
-- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Mon, 02 Mar 2015 10:15:31 -0800 John Andersen jsamyth@gmail.com пишет:
On 03/02/2015 12:52 AM, Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
Could you give example (especially of "which cable goes there")?
That said, I can't remember how I ended up with old-school names on my fresh install of 13.2 laptop, but I did, and didn't bother to change it.
В Mon, 02 Mar 2015 19:46:51 +0100 Per Jessen per@computer.org пишет:
John Andersen wrote:
On 03/02/2015 12:52 AM, Felix Miata wrote:
You don't need to use bizarro NIC names like enp5s0 if you don't want.
Personally, I like the bizarro rules. (There's always SOMEBODY ;-)
Gotten use to them with openbsd, and they aren't as bizarro as they first seem. You can just look at the nic to know which name its using and know which cable goes there.
Even if I look directly at the port and it is numbered, I am unable to work out which bizarro name it is likely to have.
If your system supports returning slot names, you should get sX for them. As long as you trust vendor to implement it correctly :)
Except for desktopsand laptops (which both typically have only one interface), I always rename to ethX.
One reason for inventing new names was avoiding name clash with automatic kernel assignment. This still applies. If you do not like "predictable" names (I do not) use something like netXX. But do not use ethXX, as it puts you back on square one. The only case when it is sure to work is when your names are the same as autossigned by kernels, in which case you can simply leave it to kernel in the first place.
-
Andrei Borzenkov -
Darin Perusich -
Felix Miata -
John Andersen -
Patrick Shanahan -
Paul Neuwirth -
Per Jessen