[opensuse] rename4 network interface??
This morning when I powered on my oS 12.3 laptop, for some reason, I've got a new network interface called "rename4". My regular eth0, ham0, and lo interfaces are there still, but my "sticky" IP address is assigned to this new "rename4" adapter, so it apparently has the MAC address of the physical NIC assigned to it. Has anyone seen this before? It's very odd... chrismyers:/home/cmyers # ifconfig eth0 Link encap:Ethernet HWaddr D2:E1:40:80:0D:3B UP BROADCAST MULTICAST MTU:1500 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:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) ham0 Link encap:Ethernet HWaddr D6:75:33:46:10:A4 inet addr:25.27.111.106 Bcast:25.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING MULTICAST MTU:1200 Metric:1 RX packets:4068 errors:0 dropped:0 overruns:0 frame:0 TX packets:3600 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:2820059 (2.6 Mb) TX bytes:684863 (668.8 Kb) 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:317 errors:0 dropped:0 overruns:0 frame:0 TX packets:317 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:48010 (46.8 Kb) TX bytes:48010 (46.8 Kb) rename4 Link encap:Ethernet HWaddr 3C:97:0E:A4:F5:E9 inet addr:172.20.9.87 Bcast:172.20.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:34591 errors:0 dropped:0 overruns:0 frame:0 TX packets:22820 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:29515929 (28.1 Mb) TX bytes:7014888 (6.6 Mb) Interrupt:20 Memory:f5300000-f5320000 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/16/2014 09:52 AM, Christopher Myers wrote:
This morning when I powered on my oS 12.3 laptop, for some reason, I've got a new network interface called "rename4". My regular eth0, ham0, and lo interfaces are there still, but my "sticky" IP address is assigned to this new "rename4" adapter, so it apparently has the MAC address of the physical NIC assigned to it.
Has anyone seen this before? It's very odd...
I haven't seen that particular issue, but you can assign device names to a specific MAC in Yast Network Settings. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott 05/16/14 9:00 AM >>> On 05/16/2014 09:52 AM, Christopher Myers wrote: This morning when I powered on my oS 12.3 laptop, for some reason, I've got a new network interface called "rename4". My regular eth0, ham0, and lo interfaces are there still, but my "sticky" IP address is assigned to this new "rename4" adapter, so it apparently has the MAC address of the physical NIC assigned to it.
Has anyone seen this before? It's very odd...
I haven't seen that particular issue, but you can assign device names to a specific MAC in Yast Network Settings. - I might have to do that; I've just never seen this happen before on my laptop in the year and a half I've had it now, so it's really odd to me that it would start doing something like that now. I know the newer versions of oS have moved to a consistent naming scheme (rather than the old like eth0 style,) but wasn't sure if this had maybe gotten back-ported to 12.3 now? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/16/2014 10:11 AM, Christopher Myers wrote:
I haven't seen that particular issue, but you can assign device names to a specific MAC in Yast Network Settings.
- I might have to do that; I've just never seen this happen before on my laptop in the year and a half I've had it now, so it's really odd to me that it would start doing something like that now. I know the newer versions of oS have moved to a consistent naming scheme (rather than the old like eth0 style,) but wasn't sure if this had maybe gotten back-ported to 12.3 now?
I'm running 13.1. I set my NIC names to the good ol' ethx ones, instead of the ones that get assigned. BTW, I haven't yet received my message that you replied to. You really should wait for messages to appear before you reply to them. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott 05/16/14 9:38 AM >>> On 05/16/2014 10:11 AM, Christopher Myers wrote: I haven't seen that particular issue, but you can assign device names to a specific MAC in Yast Network Settings.
- I might have to do that; I've just never seen this happen before on my laptop in the year and a half I've had it now, so it's really odd to me that it would start doing something like that now. I know the newer versions of oS have moved to a consistent naming scheme (rather than the old like eth0 style,) but wasn't sure if this had maybe gotten back-ported to 12.3 now?
I'm running 13.1. I set my NIC names to the good ol' ethx ones, instead of the ones that get assigned. - Makes sense; in my case with my laptop, I don't necessarily care what they're named, as long as they keep the same name. Otherwise stuff that depends on those names (in this case, VirtualBox (so that my windoze VM can have its sticky IP)) gets a bit fussy :P BTW, I haven't yet received my message that you replied to. You really should wait for messages to appear before you reply to them. ;-) - I'll try to be better about that. I just got so excited to reply to your message that I couldn't make myself wait for you to send it! :D -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 05/16/2014 10:50 AM, Christopher Myers wrote:
BTW, I haven't yet received my message that you replied to. You really should wait for messages to appear before you reply to them. ;-)
- I'll try to be better about that. I just got so excited to reply to your message that I couldn't make myself wait for you to send it! :D
That message finally turned up, more than 2.5 hours after I sent it. I've noticed messages from this list are often delayed. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott 05/16/14 11:35 AM >>> On 05/16/2014 10:50 AM, Christopher Myers wrote: BTW, I haven't yet received my message that you replied to. You really should wait for messages to appear before you reply to them. ;-)
- I'll try to be better about that. I just got so excited to reply to your message that I couldn't make myself wait for you to send it! :D
That message finally turned up, more than 2.5 hours after I sent it. I've noticed messages from this list are often delayed. - I've noticed that sometimes, where I'll get the replies to an email before I get the original question :P 2.5 hours is a pretty good gap though; ooc, is the listserv software for the list clustered or something like that possibly? Like where one node could be more backed up than another one? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
El 16/05/14 09:52, Christopher Myers escribió:
Has anyone seen this before?
Yes, you just discovered the reason why in later incarnations interfaces are automatically renamed as enp3s0, wlp3s0 ..etc.. this is because the old method has a number of problems, race conditions and oddities such as yours. -- Cristian "I don't know the key to success, but the key to failure is trying to please everybody." -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Christopher Myers -
Cristian Rodríguez -
James Knott