From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1R0E7f-0000Bj-2o for garchives@archives.gentoo.org; Sun, 04 Sep 2011 14:56:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 43DCD21C347; Sun, 4 Sep 2011 14:56:21 +0000 (UTC) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by pigeon.gentoo.org (Postfix) with ESMTP id 2754521C102 for ; Sun, 4 Sep 2011 14:55:24 +0000 (UTC) Received: by qyk34 with SMTP id 34so2688794qyk.19 for ; Sun, 04 Sep 2011 07:55:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yRQATEEqVjEg3yBWS0zDK6vysn8bAC98DgIMQymxcpw=; b=sFbsypXNIBIeku9CWdFAAcLyr3VkIuGrVLKqg+0Tdx1bjCoRo7K6pj7us+3SXLP/HU X/RP1orW32utxdqhT4c2WwEXitFW6svC7UMKhuqn9/sml3Tuoo6idPFFRt5XyG8Kca2X WqtE3NCuE/GKX2owpePH7+0CdATXLlT4iTK/s= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.229.42.138 with SMTP id s10mr2286066qce.176.1315148124648; Sun, 04 Sep 2011 07:55:24 -0700 (PDT) Received: by 10.229.80.85 with HTTP; Sun, 4 Sep 2011 07:55:24 -0700 (PDT) In-Reply-To: <4E63874B.4010805@gmail.com> References: <4E63874B.4010805@gmail.com> Date: Sun, 4 Sep 2011 16:55:24 +0200 Message-ID: Subject: Re: [gentoo-user] del.uged want to start on net.eth1, only eth0 is there From: Lars Madson To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=00163683242ccbf52e04ac1ec8f4 X-Archives-Salt: X-Archives-Hash: 1fb69a8401c21deb57fbcc4cd3ef92cf --00163683242ccbf52e04ac1ec8f4 Content-Type: text/plain; charset=ISO-8859-1 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 > 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 > > :-) :-) > > --00163683242ccbf52e04ac1ec8f4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
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=3D=3D"net", DRIVERS=3D=3D"?*", ATTR{address}= =3D=3D"00:1c:c0:5a:81:dc", KERNEL=3D=3D"eth*", NAME=3D&= quot;eth0"
2011/9/4 Dale <rdalek1967@gmai= l.com>
Lars Mads= on 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 ca= n 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 f= or some reason. =A0Your 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<= br> # 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=3D key.

# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=3D=3D"net", ACTION=3D=3D"add", DRIVERS=3D=3D&= quot;?*", ATTR{address}=3D=3D"1c:6f:65:4c:91:c7", ATT= R{dev_id}=3D=3D"0x0", ATTR{type}=3D=3D"1", KERNEL=3D=3D= "eth*", NAME=3D"eth0"
root@fireball / #

If you only have one nic but have two lines there, I would just delete the = whole file and reboot. =A0When you do and udev comes back up, it will creat= e 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 fo= r some reason.

Again, this is if I understand the problem correctly. =A0If this makes sens= e, I may on track. =A0If not, I may be missing something and you may want t= o wait on someone else to chime in.

Dale

:-) =A0:-)


--00163683242ccbf52e04ac1ec8f4--