You are not logged in.
I want to live in a sane world where my network interface on my computer, the one that came with the computer is eth0. Now when I boot with my iPhone connected, eth0 regularly becomes the non-working ethernet that the iPhone provides.
x220:/var/log$ cat /etc/udev/rules.d/10-network.rules
SUBSYSTEM=="net", ATTR{address}=="f0:de:f1:a1:dd:f0", NAME="eth0"
x220:/var/log$ grep rename daemon.log | grep udevd
Jul 3 09:27:22 localhost [ 4.709767] udevd[150]: renamed network interface eth1 to rename4
Jul 3 09:27:22 localhost [ 33.811487] udevd[150]: renamed network interface rename4 to eth0
Jul 3 09:48:50 localhost [ 2.074912] udevd[131]: renamed network interface eth1 to rename4
x220:/var/log$ /sbin/ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436 metric 1
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 6 bytes 828 (828.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 828 (828.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
rename4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 metric 1
inet 192.168.2.144 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::f2de:f1ff:fea1:ddf0 prefixlen 64 scopeid 0x20<link>
ether f0:de:f1:a1:dd:f0 txqueuelen 1000 (Ethernet)
RX packets 249 bytes 51305 (50.1 KiB)
RX errors 0 dropped 1 overruns 0 frame 0
TX packets 253 bytes 43661 (42.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf2600000-f2620000
x220:/var/log$
I TRIED the udev rules. https://wiki.archlinux.org/index.php/Ud … ork_device
I don't want to call my interface "lan". That's madness.
Offline
One can see your udev rule and it looks like it does what it should at the beginning.
Have you tried to add another udev rule for your respective iphone MAC and map that to "eth1" explicitly (or "phoneth0" or whatever) also?
Please use code tags next time when posting long output.
Offline
...
I TRIED the udev rules. https://wiki.archlinux.org/index.php/Ud … ork_deviceI don't want to call my interface "lan". That's madness.
You tried it, did it work? If not, what happened?
As to the name, you can call it whatever you choose.
SUBSYSTEM=="net", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="foobar0"Would name your interface foobar0
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
I want to name my ethernet device eth0, not foobar0, lan0 or anything else for that matter.
Offline
My point is that you can name it almost anything you want.
What is the output of ip link ??
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Instead of using daemon.log, do dmesg |grep udevd so we can see only what happened on the latest boot. Filter out anything not related to the NICs as necessary; it shouldn't be too bad.
Also, use code tags!!!
Last edited by alphaniner (2012-07-05 16:03:15)
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
I want to name my ethernet device eth0, not foobar0, lan0 or anything else for that matter.
As ewaller said, you can name it anything you like, including eth0
SUBSYSTEM=="net", ATTR{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"Are you familiar with our Forum Rules, and How To Ask Questions The Smart Way?
BlueHackers // fscanary // resticctl
Offline
As ewaller said, you can name it anything you like, including eth0
As I read the OP's non-code-tagged output in the first post, that is exactly what has been setup already with an udev rule that seems to work for starters.
The problem seems to be it messes up when hendry plugs in that iphone.
Also that is seen in the ifconfig output, with "rename4" becoming the active interface later.
Or what do I miss?
@hendry: Try setting up a udev rule stipulating a name other than "eth0" for the device that you plug in.
Offline