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