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

:-) :-)

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="" 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



:-) *:-)

Lars Madson wrote:


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"







Must be something else then.* My new nickname is stumped.* lol* At
least we know what it is not tho.*



Dale



:-)* :-)*

On Sun, Sep 4, 2011 at 6:27 AM, Lars Madson <rwx700@gmail.com> 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

Check /etc/init.d to ensure you have links for both eth0 and eth1.
Then check both /etc/conf.d/net &
/etc/udev/rules.d/70-persistent-net.rules to ensure you have both
interfaces set up as you want them, double checking each interface's
MAC address using ifconfig against any values listed in
70-persistent-net.rules, if any.

HTH,
Mark

On 09/04/2011 06:27 AM, 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?

If you are using only one ethernet adapter then you should remove
/etc/init.d/net.eth1.

If eth1 seems to exist somewhere but it really shouldn't exist, then
you should delete /etc/udev/rules.d/70-persistent-net.rules and reboot.
That should get rid of eth1.

If you really have two ethernet adapters then my answer is probably wrong.

Yes I have only one ethernet adapter, eth0.My /etc/init.d/net.eth1 is a symlink to net.loI can remove it.But shouldn't it be a /etc/init.d/net.eth0 ?
my udev rule seems alright.

thxLaurent

2011/9/4 walt <w41ter@gmail.com>

On 09/04/2011 06:27 AM, 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?



If you are using only one ethernet adapter then you should remove

/etc/init.d/net.eth1.



If eth1 seems to exist somewhere but it really shouldn't exist, then

you should delete /etc/udev/rules.d/70-persistent-net.rules and reboot.

That should get rid of eth1.



If you really have two ethernet adapters then my answer is probably wrong.

On Mon, 2011-09-05 at 17:14 +0200, Lars Madson wrote:
> Yes I have only one ethernet adapter, eth0.
> My /etc/init.d/net.eth1 is a symlink to net.lo
> I can remove it.
> But shouldn't it be a /etc/init.d/net.eth0 ?

Yes, net.eth0 should also be a symlink to net.lo. If you don't have
that symlink then you should create it.

SOLVED.I deleted the /etc/init.d/net.eth1 and created a symlink for /etc/init.d/net.eth0 to net.lo, without reboot.
Thank you!Laurent


2011/9/5 walt <w41ter@gmail.com>

On Mon, 2011-09-05 at 17:14 +0200, Lars Madson wrote:

> Yes I have only one ethernet adapter, eth0.

> My /etc/init.d/net.eth1 is a symlink to net.lo

> I can remove it.

> But shouldn't it be a /etc/init.d/net.eth0 ?



Yes, net.eth0 should also be a symlink to net.lo. *If you don't have

that symlink then you should create it.

Lars Madson wrote:

SOLVED.
I deleted the /etc/init.d/net.eth1 and created a symlink for
/etc/init.d/net.eth0 to net.lo, without reboot.


Thank you!
Laurent


Have you restarted your network? Just deleting the file isn't going to
stop/start anything. It will still be running the old way until you
restart the services or reboot.


Dale

:-) :-)