You are not logged in.
- Topics: Active | Unanswered
#1 2012-08-02 13:47:59
- alphaniner
- Member
- From: Ancapistan
- Registered: 2010-07-12
- Posts: 2,810
Udev network naming rules
I updated yesterday, and afterward nothing seemed amiss. This morning one of my eths was unable to get a dhcp lease. Eventually I realized it was because the names got mixed up; eth0 (the one I was trying to activate) and eth2 got swapped. Apparently 10-network.rules is being ignored.
I seem to recall that another network rules file (70-persistent-net.rules [?]) was mentioned recently. I used that back in my Ubu days and for a while in Arch, but eventually transitioned to 10-network.rules. Also, I don't see 70-..., 10-..., or any other network related rules files in /usr/lib/udev/rules.d.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
#2 2012-08-02 14:09:36
- jjacky
- Member
- Registered: 2011-11-09
- Posts: 347
- Website
Re: Udev network naming rules
Ignored, or did the rename failed? I (and others) have had something similar I think, see https://bbs.archlinux.org/viewtopic.php?id=145979
I think you might have to use other names than "kernel ones" (ethX), e.g. lan0 or something. Looking about this I also found that it might be possible to use nameif (from net-tools) to rename network interfaces, but I didn't actually get to test if it worked well or not, simply because I just blacklisted the driver for my other interface (eth1), since I don't actually use it.
Offline
#3 2012-08-02 14:31:24
- brebs
- Member
- Registered: 2007-04-03
- Posts: 3,742
Re: Udev network naming rules
Look in /etc/udev/rules.d/
Offline
#4 2012-08-02 14:33:18
- alphaniner
- Member
- From: Ancapistan
- Registered: 2010-07-12
- Posts: 2,810
Re: Udev network naming rules
@jjacky
I didn't see anything during boot, but output of dmesg contains:
[ 28.920102] systemd-udevd[241]: renamed network interface eth2 to eth3ACPI Warning: 0x0000000000000400-0x000000000000041f SystemIO conflicts with Region \SMRG 1 (20120320/utaddress-251)
[ 28.996255] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driverInterestingly, I also have a NIC using the sky2 driver.
OT: Is 'arch' the hostname of the machine from which the log excerpts (post #3 of that thread) were pulled? I'm curious because all of my logs just say 'localhost'.
@brebs
Yes, that's where my 10-network.rules file is located. There's nothing else there.
Last edited by alphaniner (2012-08-02 14:34:10)
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline