[opensuse-factory] 13.1 - why network eth0 is named instead ens33?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I installed 13.1 under vmplayer. On second boot, there was no network, but rcnetwork started it. However, the name is abusrd: ens33. Where is eth0? Why the change? How do I revert that change? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJG5PsACgkQtTMYHG2NR9WG7gCfS3H16eYR4dyzeMWGV6K3RID1 SgIAnR/zBAXAHnIS8gbSJlXgk9OikpLx =PudE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
В Sat, 28 Sep 2013 16:17:23 +0200 (CEST)
"Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I installed 13.1 under vmplayer.
On second boot, there was no network, but rcnetwork started it.
However, the name is abusrd: ens33.
What makes ens33 more absurd than eth0?
Where is eth0? Why the change? How do I revert that change?
One possibility is to add net.ifnames=0 to kernel command line. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJG6QQACgkQR6LMutpd94w5+wCfbbSactelobHowtOr1p/qKP2d eyEAnjTFZCcQl7OUssU/kjDJn46lzbU1 =6BPc -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-09-28 at 18:34 +0400, Andrey Borzenkov wrote:
В Sat, 28 Sep 2013 16:17:23 +0200 (CEST) "Carlos E. R." <> пишет:
However, the name is abusrd: ens33.
What makes ens33 more absurd than eth0?
How about 20 years of tradition?
Where is eth0? Why the change? How do I revert that change?
One possibility is to add net.ifnames=0 to kernel command line.
I'll try. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJG8OUACgkQtTMYHG2NR9VLOwCeIxYf03bDIAs2cFEjxn1RifFd 7TMAn1MYhrcJCpRI9HlsSa7mFBm/ieYx =J77v -----END PGP SIGNATURE-----
On Sat, Sep 28, 2013 at 05:08:21PM +0200, Carlos E. R. wrote:
On Saturday, 2013-09-28 at 18:34 +0400, Andrey Borzenkov wrote:
В Sat, 28 Sep 2013 16:17:23 +0200 (CEST) "Carlos E. R." <> пишет:
However, the name is abusrd: ens33.
What makes ens33 more absurd than eth0?
How about 20 years of tradition?
Sometimes tradition is wrong for modern things. Like systems where I can yank out any network device and add new ones while the machine runs, old-style Unix machines could not do that. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
From: Carlos E. R.
В Sat, 28 Sep 2013 16:17:23 +0200 (CEST) "Carlos E. R." <> пишет:
However, the name is abusrd: ens33.
What makes ens33 more absurd than eth0?
How about 20 years of tradition? -----Original Message----- How about: God knows how many addon-scripts expect network devices to be named ethXX -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-09-28 18:34 (GMT+0400) Andrey Borzenkov composed:
What makes ens33 more absurd than eth0?
Eth0 is easily recognizable by all familiar with traditional networking, without eidedic memory, and without requiring a lookup table. Maximum predictability here means every installation under the same roof uses the same name for the first (and only) *E*T*H*ernet port for it's reserved IP address.
One possibility is to add net.ifnames=0 to kernel command line.
When? On every boot? Only on boots on which zypper or yast will be installing updates? Only at initial installation? Does it need to be in /etc/sysconfig/bootloader too? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 28/09/13 23:29, Felix Miata escribió:
When? On every boot? Only on boots on which zypper or yast will be installing updates? Only at initial installation? Does it need to be in /etc/sysconfig/bootloader too?
To be permanent..yes. you need to add it to the bootloader parameters. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2013-09-28 23:35 (GMT-0300) Cristian Rodríguez composed:
Felix Miata composed:
[re: add net.ifnames=0 to kernel command line]
When? On every boot? Only on boots on which zypper or yast will be installing updates? Only at initial installation? Does it need to be in /etc/sysconfig/bootloader too?
To be permanent..yes. you need to add it to the bootloader parameters.
Good to know, but not an answer I wanted to hear. I'm giving a simpler approach a try. I've just welded a copy of 12.3's /etc/udev/rules.d/70-persistent-net.rules into one host's 13.1b1 / filesystem with chattr. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Felix Miata wrote:
On 2013-09-28 23:35 (GMT-0300) Cristian Rodríguez composed:
Felix Miata composed:
[re: add net.ifnames=0 to kernel command line]
When? On every boot? Only on boots on which zypper or yast will be installing updates? Only at initial installation? Does it need to be in /etc/sysconfig/bootloader too?
To be permanent..yes. you need to add it to the bootloader parameters.
Good to know, but not an answer I wanted to hear.
I'm giving a simpler approach a try. I've just welded a copy of 12.3's /etc/udev/rules.d/70-persistent-net.rules into one host's 13.1b1 / filesystem with chattr.
Apparently, having an empty file called : /etc/udev/rules.d/80-net-name-slot.rules will also work. I have also been told that giving the network interfaces names with YaST will work. I'm about to try that. -- Per Jessen, Zürich (16.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos, On Sat, Sep 28, 2013 at 04:17:23PM +0200, Carlos E. R. wrote:
On second boot, there was no network, but rcnetwork started it.
However, the name is abusrd: ens33. Where is eth0?
By default systemd now names interfaces using firmware/BIOS provided index numbers (e.g. eno1), but if that info is not available (possibly because you're inside vmplayer) it falls back to naming after firmware/BIOS provided PCI-E hotplug slot index numbers -- which is what you're seeing here.
Why the change?
It's in order to ensure *predictable* NIC names across reboots.
How do I revert that change?
You could disable the udev rule with something like: `ln -sv /dev/null /etc/udev/rules.d/80-net-name-slot.rules` Regards, -- Paul Thompson SUSE Consulting -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-09-28 at 15:53 +0100, Paul Thompson wrote:
Carlos,
On Sat, Sep 28, 2013 at 04:17:23PM +0200, Carlos E. R. wrote:
On second boot, there was no network, but rcnetwork started it.
However, the name is abusrd: ens33. Where is eth0?
By default systemd now names interfaces using firmware/BIOS provided index numbers (e.g. eno1), but if that info is not available (possibly because you're inside vmplayer) it falls back to naming after firmware/BIOS provided PCI-E hotplug slot index numbers -- which is what you're seeing here.
Why the change?
It's in order to ensure *predictable* NIC names across reboots.
My computers have been reliably using eth0 for decades. This computer has two nics, and eth0 has always been eth0, and eth1 has always been eth1. For instance, now a script that used eth0 would have to be edited for each computer.
How do I revert that change?
You could disable the udev rule with something like: `ln -sv /dev/null /etc/udev/rules.d/80-net-name-slot.rules`
I'll have a look. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJG8g0ACgkQtTMYHG2NR9U0hgCfVjltMkOLtfEo98beIu+b08d0 SGEAnjX9i6BhRe1AgSxREJ68D+FwI8PQ =N2XE -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 28/09/13 12:13, Carlos E. R. escribió:
It's in order to ensure *predictable* NIC names across reboots.
My computers have been reliably using eth0 for decades.
argumentum ad antiquitatem that is called.
For instance, now a script that used eth0 would have to be edited for each computer.
The script is well.. wrong..making asumptions about interface names. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 2013-09-28 20:12, Cristian Rodríguez wrote:
For instance, now a script that used eth0 would have to be edited for each computer.
The script is well.. wrong..making asumptions about interface names.
It is not an assumption, it is just... a static way of configuration. :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/28/2013 02:12 PM, Cristian Rodríguez pecked at the keyboard and wrote:
El 28/09/13 12:13, Carlos E. R. escribió:
It's in order to ensure *predictable* NIC names across reboots.
My computers have been reliably using eth0 for decades.
argumentum ad antiquitatem that is called.
For instance, now a script that used eth0 would have to be edited for each computer.
The script is well.. wrong..making asumptions about interface names.
But there was no guess work as the ethernet interface was always called... eth0 so the script was always right. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/28/2013 11:12 AM, Cristian Rodríguez wrote:
El 28/09/13 12:13, Carlos E. R. escribió:
It's in order to ensure *predictable* NIC names across reboots. My computers have been reliably using eth0 for decades. argumentum ad antiquitatem that is called.
For instance, now a script that used eth0 would have to be edited for each computer. The script is well.. wrong..making asumptions about interface names.
How would one make reference to the third Ethernet interface in a box that has five? You have to call it something, and changing the name without good reason sounds like something for-profit operating systems would do. Or, are you saying that we should never need to refer to a network interface by name? That referring to it by IP address should be enough? But what about interfaces without IP addresses, such as /dev/rst0? Wouldn't it be possible to make the "ethX" names predictable across reboots? Or am I missing something? Regards, Lew -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Saturday 2013-09-28 20:49, Lew Wolfgang wrote:
Or, are you saying that we should never need to refer to a network interface by name? That referring to it by IP address should be enough?
The point is that any name (network interfaces or device nodes) could already be a name that the user has statically assigned overruling any default system decisions.
But what about interfaces without IP addresses, such as /dev/rst0?
Since no single identifier works for all people in all cases, that is why there is the possibility to pick them out in multiple ways. Serial number, Make&Model, PCI/USB "path", ...
Wouldn't it be possible to make the "ethX" names predictable across reboots?
Yes, define some static user-endorsed rule like those the systems has so far (in openSUSE) created for us in 70-persistent-net.rules. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt wrote:
But what about interfaces without IP addresses, such as /dev/rst0? Since no single identifier works for all people in all cases, that is why there is the possibility to pick them out in multiple ways. Serial number, Make&Model, PCI/USB "path", ...
Well, eth has worked well for years, as it identifies a physical device, independent of protocol -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
El 28/09/13 15:49, Lew Wolfgang escribió:
How would one make reference to the third Ethernet interface in a box that has five? You have to call it something, and changing the name without good reason sounds like something for-profit operating systems would do.
Or, are you saying that we should never need to refer to a network interface by name?
No, I am not. what I'm trying to say is that there must be a simple way to determine the needed interface name dynamically.
Or am I missing something?
YEs, please read this http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... carrefully, particulary the "WHY?" section. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 09/28/2013 12:24 PM, Cristian Rodríguez wrote:
El 28/09/13 15:49, Lew Wolfgang escribió:
How would one make reference to the third Ethernet interface in a box that has five? You have to call it something, and changing the name without good reason sounds like something for-profit operating systems would do.
Or, are you saying that we should never need to refer to a network interface by name? No, I am not. what I'm trying to say is that there must be a simple way to determine the needed interface name dynamically.
Or am I missing something? YEs, please read this http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterface... carrefully, particulary the "WHY?" section.
Thanks, that does make sense. I still remember the SunOS 3.3 days where SCSI disks and tapes were named according to their SCSI bus addresses, which were hardware switch selectable. At some point after that the notion (from the Pea Sea world I think) that hardware addressing should be randomized at boot was introduced. Boy, did THAT ever suck! Regards, Lew -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-09-28 at 15:12 -0300, Cristian Rodríguez wrote:
El 28/09/13 12:13, Carlos E. R. escribió:
It's in order to ensure *predictable* NIC names across reboots.
My computers have been reliably using eth0 for decades.
argumentum ad antiquitatem that is called.
For instance, now a script that used eth0 would have to be edited for each computer.
The script is well.. wrong..making asumptions about interface names.
What about openSUSE documentation? The firewall script is full of references to eth0, eth1... and that's the only file I looked at yet. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJHh0EACgkQtTMYHG2NR9VzOACgjrTaC4Z/TZcllZ/4/L2eXel3 wLgAnj/1hxcLfJWxnU6wgTVn47rlcIQR =fsKq -----END PGP SIGNATURE-----
El 28/09/13 11:53, Paul Thompson escribió:
By default systemd now names interfaces using firmware/BIOS provided index numbers (e.g. eno1),
To be precise, it is udev that does that. -- "If debugging is the process of removing bugs, then programming must be the process of putting them in." - Edsger Dijkstra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
One cause is that /etc/udev/rules.d/70-persistent.net is missing as happend on this box. You can set them up appriately with the MAC addresses in the order you require. # cat /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="50:e5:49:c8:2e:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:f0:5b:65:5a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:2e:f1:36:99", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0" Regards Sid. On 28/09/13 15:17, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I installed 13.1 under vmplayer.
On second boot, there was no network, but rcnetwork started it.
However, the name is abusrd: ens33.
Where is eth0? Why the change? How do I revert that change?
- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux)
iEYEARECAAYFAlJG5PsACgkQtTMYHG2NR9WG7gCfS3H16eYR4dyzeMWGV6K3RID1 SgIAnR/zBAXAHnIS8gbSJlXgk9OikpLx =PudE -----END PGP SIGNATURE-----
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Sid Boyce wrote:
One cause is that /etc/udev/rules.d/70-persistent.net is missing as happend on this box. You can set them up appriately with the MAC addresses in the order you require. # cat /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="50:e5:49:c8:2e:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:f0:5b:65:5a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:2e:f1:36:99", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0"
Is it my imagination, or is it the purpose of all these changes to make administration more difficult? I have also been running Linux for several years and never had a problem with NIC ID, at least with up to 3 NICs. In my experience, the ID depends on the slot the NIC is plugged into. According to the above, changing a NIC will require editing a file, to ensure the same ID is used. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
James Knott wrote:
Is it my imagination, or is it the purpose of all these changes to make administration more difficult? I have also been running Linux for several years and never had a problem with NIC ID, at least with up to 3 NICs. In my experience, the ID depends on the slot the NIC is plugged into. According to the above, changing a NIC will require editing a file, to ensure the same ID is used.
Further on this. The computer with 3 NICs is my firewall. It has a built in NIC and I added 2 more NICs. As originally configured with the 3 NICs., the plug in NICs were eth 0 & 1 and the built in one eth2. I later removed eth1, because it was failing. But doing that did not cause the other NIC IDs to change. I now have eth0 and eth2, with no eth1 in the computer at all. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 28/09/13 22:04, James Knott wrote:
Sid Boyce wrote:
One cause is that /etc/udev/rules.d/70-persistent.net is missing as happend on this box. You can set them up appriately with the MAC addresses in the order you require. # cat /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="50:e5:49:c8:2e:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:f0:5b:65:5a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:2e:f1:36:99", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0" Is it my imagination, or is it the purpose of all these changes to make administration more difficult? I have also been running Linux for several years and never had a problem with NIC ID, at least with up to 3 NICs. In my experience, the ID depends on the slot the NIC is plugged into. According to the above, changing a NIC will require editing a file, to ensure the same ID is used. I agree. After doing an upgrades via zypper dup I noticed there was a change to ens65 or something like that but only on one of 3 boxes. The other 2 boxes still had /etc/udev/rules.d/70-persistent.net present. Regards Sid.
-- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Sid Boyce wrote:
On 28/09/13 22:04, James Knott wrote:
Sid Boyce wrote:
One cause is that /etc/udev/rules.d/70-persistent.net is missing as happend on this box. You can set them up appriately with the MAC addresses in the order you require. # cat /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="50:e5:49:c8:2e:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:f0:5b:65:5a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:2e:f1:36:99", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0" Is it my imagination, or is it the purpose of all these changes to make administration more difficult? I have also been running Linux for several years and never had a problem with NIC ID, at least with up to 3 NICs. In my experience, the ID depends on the slot the NIC is plugged into. According to the above, changing a NIC will require editing a file, to ensure the same ID is used.
I agree. After doing an upgrades via zypper dup I noticed there was a change to ens65 or something like that but only on one of 3 boxes. The other 2 boxes still had /etc/udev/rules.d/70-persistent.net present.
Yes, on an update you should definitely be able to retain the existing naming. I suggest you open a bugreport. -- Per Jessen, Zürich (16.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 29/09/13 09:44, Per Jessen wrote:
Sid Boyce wrote:
Sid Boyce wrote:
One cause is that /etc/udev/rules.d/70-persistent.net is missing as happend on this box. You can set them up appriately with the MAC addresses in the order you require. # cat /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="50:e5:49:c8:2e:8c", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1c:f0:5b:65:5a", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:2e:f1:36:99", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="wlan0" Is it my imagination, or is it the purpose of all these changes to make administration more difficult? I have also been running Linux for several years and never had a problem with NIC ID, at least with up to 3 NICs. In my experience, the ID depends on the slot the NIC is plugged into. According to the above, changing a NIC will require editing a file, to ensure the same ID is used. I agree. After doing an upgrades via zypper dup I noticed there was a change to ens65 or something like that but only on one of 3 boxes. The other 2 boxes still had /etc/udev/rules.d/70-persistent.net
On 28/09/13 22:04, James Knott wrote: present. Yes, on an update you should definitely be able to retain the existing naming. I suggest you open a bugreport.
I shall leave as is for now as I created /etc/udev/rules.d/70-persistent.net on the one box where it was missing, subsequent updates have not changed it. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Senior Staff Specialist, Cricket Coach Microsoft Windows Free Zone - Linux used for all Computing Tasks -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. wrote:
I installed 13.1 under vmplayer.
On second boot, there was no network, but rcnetwork started it.
However, the name is abusrd: ens33.
Agree.
Where is eth0? Why the change? How do I revert that change?
See https://bugzilla.novell.com/show_bug.cgi?id=820589 -- Per Jessen, Zürich (16.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-09-28 at 23:52 +0200, Per Jessen wrote:
Carlos E. R. wrote:
However, the name is abusrd: ens33.
Agree.
Where is eth0? Why the change? How do I revert that change?
Mmmm. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlJHih0ACgkQtTMYHG2NR9UN4QCffgOUN7Ijzt4d0kySDzCFMqJ8 71wAn04zTBYTXwOd4EE65+K6DwRGZDGu =D6mX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I installed 13.1 under vmplayer.
On second boot, there was no network, but rcnetwork started it.
However, the name is abusrd: ens33.
Where is eth0? Why the change? How do I revert that change?
Somwhat tangential to Carlos' question here, but any chance that anyone would want to take a look at https://bugzilla.novell.com/show_bug.cgi?id=842450 The networking naming isn't exactly consistent. Sometimes something is renamed, sometimes not. -- Per Jessen, Zürich (16.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (14)
-
Andrey Borzenkov -
Carlos E. R. -
Carlos E. R. -
Cristian Rodríguez -
Felix Miata -
Greg KH -
Hans Witvliet -
James Knott -
Jan Engelhardt -
Ken Schneider - openSUSE -
Lew Wolfgang -
Paul Thompson -
Per Jessen -
Sid Boyce