Re: [gentoo-user] del.uged want to start on net.eth1, only eth0 is there

[Lars Madson <rwx700@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2177 bytes --]

hm there's only one line in my /etc/udev/rules.d/70-persistent-net.rules:

# This file was automatically generated by the /lib64/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1c:c0:5a:81:dc",
KERNEL=="eth*", NAME="eth0"


2011/9/4 Dale <rdalek1967@gmail.com>

> Lars Madson wrote:
>
>> Hi,
>>
>> After upgrading world, I might have gone a bit fast on the last conf files
>> that I update with etc-update.
>> Now that I restart deluged, the init script brings up eth1 but I only have
>> eth0 correctly setup.
>> It should use eth0. In rc-update list I see net.eth1, no net.eth0, if it
>> can help.
>>
>> My question is when this net.eth1 is called so that I could fix this wrong
>> routing?
>>
>> thx
>> Laurent
>>
>
> If I understand this correctly, it sounds like udev has created a new nic
> for some reason.  Your file should be here and look something like this:
>
> root@fireball / # cat /etc/udev/rules.d/70-**persistent-net.rules
> # This file was automatically generated by the /lib64/udev/write_net_rules
> # program, run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single
> # line, and change only the value of the NAME= key.
>
> # PCI device 0x10ec:0x8168 (r8169)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="1c:6f:65:4c:**91:c7", ATTR{dev_id}=="0x0",
> ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
> root@fireball / #
>
> If you only have one nic but have two lines there, I would just delete the
> whole file and reboot.  When you do and udev comes back up, it will create a
> new file and it resets its naming and such which should get you back to
> net.eth0 again.
>
> I think you can kill udev and restart it if you don't want to reboot for
> some reason.
>
> Again, this is if I understand the problem correctly.  If this makes sense,
> I may on track.  If not, I may be missing something and you may want to wait
> on someone else to chime in.
>
> Dale
>
> :-)  :-)
>
>

[-- Attachment #2: Type: text/html, Size: 3056 bytes --]