In <20100210084608.gu14...@think.homelan>, Andrei Popescu wrote:
>On Tue,09.Feb.10, 23:06:08, Stan Hoeppner wrote:
>> I don't know anything about these scripts. When do they run?
Udev is a daemon, started fairly early in the boot process. It communicates
with the kernel. It evaluates the rules
On Wed, Feb 10, 2010 at 10:46:08AM +0200, Andrei Popescu wrote:
> On Tue,09.Feb.10, 23:06:08, Stan Hoeppner wrote:
> > Andrei Popescu put forth on 2/9/2010 3:37 AM:
> > > On Mon,08.Feb.10, 16:33:39, Stan Hoeppner wrote:
[snip]
> > I don't know anything about these scripts. When do they run? And
cially since the OP mentioned the interface
> > names were ok and consistent.
>
> The mere existence of this Debian doc (and others) suggests that this UDEV
> eth0/eth1/etc naming problem is fairly common. Common enough for people to
> take
> the time to write a lengthy help do
que (or at least no reports here on d-u) I
> doubt it's good advice to tell someone having troubles with networking
> to edit udev rules, especially since the OP mentioned the interface
> names were ok and consistent.
The mere existence of this Debian doc (and others) suggest
On Mon,08.Feb.10, 20:07:36, Frank Miles wrote:
> I won't belabor this.
>
> Putting in a different NIC fixed things. No fuss, though interesting that it
> (presumably udev) wanted to call it eth2. I can live with that.
Of course it did, eth0 and eth1 were already taken ;)
Regards,
Andrei
--
Of
On Mon,08.Feb.10, 16:33:39, Stan Hoeppner wrote:
> So, are you saying it didn't happen? Couldn't have happened? Shouldn't have
> happened? I'm imagining things? Are you kidding?
No, I'm saying that under normal circumstances it should work.
> It broke. I fixed it by manually editing the p
I won't belabor this.
Putting in a different NIC fixed things. No fuss, though interesting that it
(presumably udev) wanted to call it eth2. I can live with that.
Thanks again, everyone!
-Frank
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsu
Andrei Popescu put forth on 2/8/2010 2:29 PM:
> On Mon,08.Feb.10, 01:15:43, Stan Hoeppner wrote:
>
>>> Perhaps the kernel brings eth1 into existence by first establishing it as
>>> eth0, then renaming it to eth1; then bringing the "real" eth0 into
>>> existence.
>>
>> The above can happen when yo
On Mon,08.Feb.10, 01:15:43, Stan Hoeppner wrote:
> > Perhaps the kernel brings eth1 into existence by first establishing it as
> > eth0, then renaming it to eth1; then bringing the "real" eth0 into
> > existence.
>
> The above can happen when you add NICs to the system. I hate UDEV for this,
>
Frank Miles put forth on 2/8/2010 10:32 AM:
> Thanks so much to Stan, Tom H, and Cameleon!
>
> It seems that the consensus is that it's a NIC problem. In case
> it wasn't previously clear, the RealTek 8169 is part of the Gigabyte
> motherboard.
>
> I thought that I'd escaped non-free-firmware he
Thanks so much to Stan, Tom H, and Cameleon!
It seems that the consensus is that it's a NIC problem. In case
it wasn't previously clear, the RealTek 8169 is part of the Gigabyte
motherboard.
I thought that I'd escaped non-free-firmware hell by getting a MB
with the graphics based on an Intel ch
Hi Frank, sorry you're going through such pains here. Did the same myself not
long ago.
Frank Miles put forth on 2/7/2010 12:41 PM:
> Feb 7 04:51:22 puffin kernel: [6.156559] r8169 Gigabit Ethernet
> driver 2.3LK-NAPI loaded
> Feb 7 04:51:22 puffin kernel: [6.156573] r8169 :02:00.0
... ok, started...
[snip]
I fail to see what it's doing, but I cannot see any reference to "eth1",
it's like only one interace is being recognized :-?
What is the output of "dmesg | grep eth"?
[6.317161] eth1: RTL8168d/8111d at 0xc9c4e000,xx:xx:xx:xx:xx:xx, XID 083000c0 IRQ 32
>> [ 6.317161] eth1: RTL8168d/8111d at 0xc9c4e000,xx:xx:xx:xx:xx:xx,
>> XID 083000c0 IRQ 32
>> [ 6.384830] eth1: unable to apply firmware patch
>> [ 7.190453] udev: renamed network interface eth1 to eth0
>> [ 7.229390] udev: renamed network interface eth0_rename to eth1
>> [
On Sun, 07 Feb 2010 13:36:13 -0800, Frank Miles wrote:
> [snip]
>
>>I fail to see what it's doing, but I cannot see any reference to "eth1",
>>it's like only one interace is being recognized :-?
>>
>>What is the output of "dmesg | grep eth"?
>
> [6.317161] eth1: RTL8168d/8111d at 0xc9000
> I made a minor effort earlier to suppress the IPv6 modules, but [a] didn't
> succeed
Add
ipv6.disable=1
to the grub kernel/linux line to disable ipv6 (without recompiling the kernel)
but it cannot be the problem.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject
On Sun, 07 Feb 2010 13:36:13 -0800, Frank Miles wrote:
> [snip]
>
>>I fail to see what it's doing, but I cannot see any reference to "eth1",
>>it's like only one interace is being recognized :-?
>>
>>What is the output of "dmesg | grep eth"?
>
> [6.317161] eth1: RTL8168d/8111d at 0xc9000
> That file includes:
> # PCI device 0x10ec:0x8168 (r8169)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0", ATTR{type}=="1",
> KERNEL=="eth*", NAME="eth0"
> # PCI device 0x10b7:0x9050 (3c59x)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="
[snip]
I fail to see what it's doing, but I cannot see any reference to "eth1",
it's like only one interace is being recognized :-?
What is the output of "dmesg | grep eth"?
[6.317161] eth1: RTL8168d/8111d at 0xc9c4e000, xx:xx:xx:xx:xx:xx,
XID 083000c0 IRQ 32
[6.384830] eth1
On Sun, 07 Feb 2010 10:41:46 -0800, Frank Miles wrote:
> Thanks, Camaleon (sorry - don't know how to generate the proper
> characters).
Still "us-ascii"? ;-) No problem.
> That file includes:
>
> # PCI device 0x10ec:0x8168 (r8169)
> SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
> ATTR{addres
Thanks, Camaleon (sorry - don't know how to generate the proper characters).
That file includes:
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="xx:xx:xx:xx:xx:xx", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device
On Sun, 07 Feb 2010 07:07:03 -0800, Frank Miles wrote:
(...)
> There is one troubling line in the logs from boot:
> udev: renamed network interface eth0 to eth1
> Doing an "ifdown eth1" does not fix the eth0 problem.
Mmm... check your "/etc/udev/rules.d/70-persistent-net.rules", there
sho
I am in the final throes of getting a new system running (Debian/squeeze).
For the past 2 weeks it's had just eth0, and the network has worked fine.
Now I want this system to have two network interfaces - the original eth0,
and eth1 to a DSL modem, just like its precessor system.
The strange th
Another user of a Realtec 8139 ethenet card noticed that his
card was "not working".
Others reported it was related to a eth1394 device conflict.
I report a similar occurence.
i have a ibook g4 running sid with kernel linux-image 2.6.17-2
uname -a
Linux debian 2.6.17-2-powerpc #1 Thu Aug 31 1
On Mon, 27 Feb 2006 20:36:35 +0100
Svante Signell <[EMAIL PROTECTED]> wrote:
> The solution given below has been working for some time now, until udev
> 0.085-1 from Feb 19 was installed. Then the behaviour is wrong again,
> eth0 is associated to the 8139too driver and eth1 is associated to the
>
> Florian Kulzer wrote:
>
> > Svante Signell wrote:
> >
> > The solution given below has been working for some time now, until
> > udev
> > 0.085-1 from Feb 19 was installed. Then the behaviour is wrong
> > again,
> > eth0 is associated to the 8139too driver and eth1 is as
Svante Signell wrote:
The solution given below has been working for some time now, until udev
0.085-1 from Feb 19 was installed. Then the behaviour is wrong again,
eth0 is associated to the 8139too driver and eth1 is associated to the
3c59x driver. What has changed in the udev functionality? The
The solution given below has been working for some time now, until udev
0.085-1 from Feb 19 was installed. Then the behaviour is wrong again,
eth0 is associated to the 8139too driver and eth1 is associated to the
3c59x driver. What has changed in the udev functionality? The
file /etc/udev/static-ni
On Monday, 30.01.2006 at 14:13 +0100, Torquil Macdonald Sørensen wrote:
> >I also had the same problem. It seems to me that udev cannot assign a
> >name to a network device if that name is already taken by another
> >device. Therefore these udev rules only "work" if the assignment
> >happened to b
Florian Kulzer wrote:
Torquil Macdonald Sørensen wrote:
Greetings!
I am having some problems controlling the assignement order of eth0,
eth1 and so on with udev. There was another thread about this earlier:
http://lists.debian.org/debian-user/2006/01/msg00075.html
I created a /etc/udev
Torquil Macdonald Sørensen wrote:
Greetings!
I am having some problems controlling the assignement order of eth0,
eth1 and so on with udev. There was another thread about this earlier:
http://lists.debian.org/debian-user/2006/01/msg00075.html
I created a /etc/udev/local.rules as adviced, with
Greetings!
I am having some problems controlling the assignement order of eth0,
eth1 and so on with udev. There was another thread about this earlier:
http://lists.debian.org/debian-user/2006/01/msg00075.html
I created a /etc/udev/local.rules as adviced, with a symlink to this
file in /etc
o care which card is designated eth0
> and which is designated eth1 then you could copy the script
> get-mac-address.sh from /usr/share/doc/ifupdown/examples
> into /etc/network and map the configuration to the mac address of each
> card with some text in /etc/network/interfaces like:
&
Stefhen Hovland wrote:
>i think ifrename will do what you are asking, you can specify that
>eth0 always be bound to x, and eth1 always bound to y, etc..
>
>
>http://packages.debian.org/unstable/net/ifrename
>
>stefhen
>
>On 12/29/05, Svante Signell <[EMAIL PROTECTED]> wrote:
>
>
>>With the new w
own/examples
into /etc/network and map the configuration to the mac address of each
card with some text in /etc/network/interfaces like:
auto eth0 eth1
mapping eth0 eth1
script /etc/network/get-mac-address.sh
map 00:00:00:00:00:00 wireless
map 11:11:11:11:11:11 ethernet
:
mapping, e.g.
auto eth0 eth1
mapping eth*
script /usr/local/sbin/map-scheme
and in the map-scheme script,
mac=$(/sbin/ifconfig "$1" | \
sed -n '/^.*HWaddr \([:[:xdigit:]]*\).*/{s//\1/;y/abcdef/ABCDEF/;p;q;}')
which contains the MAC address. The advantage is that one can
Svante Signell wrote:
With the new way of device creation and module loading (udev, discover
etc) my ethernet modules (3c59x,8139too) are loaded in different order
with kernels 2.6.12 and 2.6.14. For 2.6.14 3c59x is loaded first
corresponding to eth0 and then 8139too corresponding to eth1. With
k
i think ifrename will do what you are asking, you can specify that
eth0 always be bound to x, and eth1 always bound to y, etc..
http://packages.debian.org/unstable/net/ifrename
stefhen
On 12/29/05, Svante Signell <[EMAIL PROTECTED]> wrote:
> With the new way of device creation and module loadin
With the new way of device creation and module loading (udev, discover
etc) my ethernet modules (3c59x,8139too) are loaded in different order
with kernels 2.6.12 and 2.6.14. For 2.6.14 3c59x is loaded first
corresponding to eth0 and then 8139too corresponding to eth1. With
kernel 2.6.12 they are lo
On Friday, 24.06.2005 at 23:30 +1200, Chris Bannister wrote:
> > > Try setting Plug-n-Play to NO/OFF/FALSE in bios
> > >
> > There are around 3 method to do so (learned while googling for the
> > problem, maybe somewhere metioned them on this list too, not sure).
> > I chose an easier one. I just
On Thu, Jun 23, 2005 at 12:51:06PM -0400, H. S. wrote:
> Apparently, _Chris Bannister_, on 23/06/05 12:30,typed:
> > Hi,
> >
> > Try setting Plug-n-Play to NO/OFF/FALSE in bios
> >
> > HTH
> >
>
> There are around 3 method to do so (learned while googling for the
> problem, maybe somewhere meti
Apparently, _Chris Bannister_, on 23/06/05 12:30,typed:
> Hi,
>
> Try setting Plug-n-Play to NO/OFF/FALSE in bios
>
> HTH
>
There are around 3 method to do so (learned while googling for the
problem, maybe somewhere metioned them on this list too, not sure). I
chose an easier one. I just mentio
Hi,
Try setting Plug-n-Play to NO/OFF/FALSE in bios
HTH
--
Chris.
==
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Shaddy just rejoiced over my response (see ``purity -p
> nerd|grep ^100'') ;-), and felt an irresistible compulsion to rephrase
> it. Besides, s/he has other problems like replying both to me and the
> list, and [1]TOFU, besides being rude.
>
> [1] http://www.vranx.de/mail/tofu.html
>
I since
On Thu, Feb 12, 2004 at 08:23:22PM -0800, Nano Nano wrote:
> On Fri, Feb 13, 2004 at 11:46:58AM +0800, Shaddy.Baddah wrote:
> > Finally! Thank you Jan. Some of the suggestions are pretty convenient, like
> > dmesg, which should give you the vendor details, but that would break down
> > if they are
On Fri, Feb 13, 2004 at 11:46:58AM +0800, Shaddy.Baddah wrote:
> Finally! Thank you Jan. Some of the suggestions are pretty convenient, like
> dmesg, which should give you the vendor details, but that would break down
> if they are the same vendor. And considering this is the absolute correct
> way
al Message-
From: Jan Minar [mailto:[EMAIL PROTECTED]
Sent: Friday, February 13, 2004 10:42 AM
To: Debian Users List
Subject: Re: eth0/eth1 which one?
On Thu, Feb 12, 2004 at 10:40:11AM -0800, Lars Jensen wrote:
> I have two network cards on my machine How do I tell which one is eth0
>
On Thu, Feb 12, 2004 at 10:40:11AM -0800, Lars Jensen wrote:
> I have two network cards on my machine How do I tell which one is eth0
> and which one is eth1 ?
Quite a bunch of interesting replies :-) Here is mine:
Each and every ethernet card has its own unique MAC number, this number
usually i
On Thu, 12 Feb 2004 13:02:42 -0800
Paul Johnson <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Thu, Feb 12, 2004 at 10:40:11AM -0800, Lars Jensen wrote:
> > I have two network cards on my machine How do I tell which one is eth0
> > and which one is eth1 ?
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, Feb 12, 2004 at 10:40:11AM -0800, Lars Jensen wrote:
> I have two network cards on my machine How do I tell which one is eth0
> and which one is eth1 ?
If you have DHCP on your segment, then you can plug one in and see
which iface gets the IP.
On Thu, Feb 12, 2004 at 10:40:11AM -0800, Lars Jensen wrote:
> I have two network cards on my machine How do I tell which one is eth0
> and which one is eth1 ?
If the cards use different modules, `dmesg' should give you some
information on which card is is served by which driver.
But if the cards
On 02/12/2004 04:40 PM, Lars Jensen wrote:
I have two network cards on my machine How do I tell which one is eth0
and which one is eth1 ?
dmesg can give you a hint:
$ dmesg | grep 'eth[01]'
--
Hamilton Coutinho | Feanor - license issues are
[EMAIL PROTECTED] | important. If we do
Lars Jensen wrote:
> I have two network cards on my machine How do I tell which one is eth0
> and which one is eth1 ?
Unplug one and run ifconfig -a. The one with "no carrier" is the one you
unplugged.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Con
On Thu, Feb 12, 2004 at 10:40:11AM -0800, Lars Jensen wrote:
> I have two network cards on my machine How do I tell which one is eth0
> and which one is eth1 ?
>
> Thanks,
> Lars.
ping something and look at the link lights
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsub
I have two network cards on my machine How do I tell which one is eth0
and which one is eth1 ?
Thanks,
Lars.
--
Lars Jensen, Truckee Meadows Community College, Reno NV 89512-3999.
Tel: 775.673.7113 E-mail: [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsu
Doug MacFarlane wrote:
On Wed, 05 Nov 2003 01:15:18 -0900, Ken Irving wrote:
On Wed, Nov 05, 2003 at 09:52:42AM +0100, Andreas Bohnert wrote:
Hi,
I don't know how to setup my firewall for my new xdsl connection. I
saw some posting concerning adsl, so maybe there are some
people,
On Wed, 05 Nov 2003 01:15:18 -0900, Ken Irving wrote:
> On Wed, Nov 05, 2003 at 09:52:42AM +0100, Andreas Bohnert wrote:
>> Hi,
>>I don't know how to setup my firewall for my new xdsl connection. I
>> saw some posting concerning adsl, so maybe there are some
>> people, who know how t
On Wed, 05 Nov 2003 01:15:18 -0900, Ken Irving wrote:
> On Wed, Nov 05, 2003 at 09:52:42AM +0100, Andreas Bohnert wrote:
>> Hi,
>>I don't know how to setup my firewall for my new xdsl connection. I
>> saw some posting concerning adsl, so maybe there are some
>> people, who know how to
On Wed, Nov 05, 2003 at 09:52:42AM +0100, Andreas Bohnert wrote:
> Hi,
>I don't know how to setup my firewall for my new xdsl connection. I
> saw some posting concerning adsl, so maybe there are some
> people, who know how to handle this.
I'm not sure what you're talking about, with
Hi,
I don't know how to setup my firewall for my new xdsl connection. I
saw some posting concerning adsl, so maybe there are some
people, who know how to handle this.
here is my situation:
eth0 is connect to my private network (192.168.0.1).
my eth1 gets an lokal ip from my
On Mon, Jun 10, 2002 at 03:41:29AM -0400, Anthony DeRobertis wrote:
> On Sun, 2002-06-09 at 09:46, AE Roy wrote:
>
> > I'm looking for a way in which I can turn my eth0 into eth1. I've been
> > thru all the files in /etc/network but I didn't find what I'm looking for.
>
> I've never used it, but
On Sun, 2002-06-09 at 09:46, AE Roy wrote:
> I'm looking for a way in which I can turn my eth0 into eth1. I've been
> thru all the files in /etc/network but I didn't find what I'm looking for.
I've never used it, but according to the manpage, nameif can do this.
see man 8 nameif.
signature.asc
AE Roy wrote:
> I'm looking for a way in which I can turn my eth0 into eth1.
> I was imagening something along the lines of eth0=eth1.
If you're using kernel 2.4 and package iproute2, you could do it like
this: ip link set eth0 name eth1
--
[EMAIL PROTECTED]
--
To UNSUB
On Sun, Jun 09, 2002 at 04:51:10PM +0200, Tobias Jahn wrote:
> I have not tested this, but try the following kernel parameter at boot time
> (i.e. in your lilo/grub configuration or by hand):
>
> ether=0,0,eth1
>
> (The format is ether=irq,addr,name where 0 indicates autoprobe for irq and
> addr.
Hello Roy,
On Sun, Jun 09, 2002 at 06:46:48AM -0700, AE Roy wrote:
> I'm looking for a way in which I can turn my eth0 into eth1. I've been
> thru all the files in /etc/network but I didn't find what I'm looking for.
I have not tested this, but try the following kernel parameter at boot time
(i.e
d the outer-netorwk.
I'm looking for a way in which I can turn my eth0 into eth1. I've been
thru all the files in /etc/network but I didn't find what I'm looking for.
I was imagening something along the lines of eth0=eth1.
Anyone know anything about this?
Roy
--
To UNS
On Thu, Nov 22, 2001 at 11:25:43PM -0500, Sean Morgan wrote:
> Also, I can't for the life of me see why a cable company would lock on to
> a MAC address.
RCN in the northeast US does exactly this.
Personally I was happy (when I was in charge of such things) to
instruct the modem to recognise one
On Thu, Nov 22, 2001 at 11:25:43PM -0500, Sean Morgan wrote:
> On Wed, 21 Nov 2001 10:44:19 -0500
>
> Also, I can't for the life of me see why a cable company would lock on to
> a MAC address. Roadrunner doesn't do this, and it would be really
> incompetent for a cable company to authenticate on
Sean Morgan <[EMAIL PROTECTED]> writes:
> Also, I can't for the life of me see why a cable company would lock on to
> a MAC address. Roadrunner doesn't do this, and it would be really
Roadrunner in Eastern Mass. does do this. They're so kind as to even
put the mac address as the hostname, like
en quite a saga - I have lost my (limited) hacking instinct.
> | > | Having failed to get ipmasq to work on 2.2.19 (possibly something
to
> | > | do with eth0 eth1 being reversed i.e. eth0 on LAN side), I am now
on
> | > | the 2.4.14 precompiled and hoping for better things.
&g
ipmasq to work on 2.2.19 (possibly something to
| > | do with eth0 eth1 being reversed i.e. eth0 on LAN side), I am now on
| > | the 2.4.14 precompiled and hoping for better things.
| >
| > You can specify the address for each card on the kernel command line,
| only if you compile the dr
According to Kelley, Tim (CBS-New Orleans) on Wed, Nov 21, 2001 at 09:26:16AM
-0500:
> dhcpcd can pass whatever Mac address you want to a dhcp server ...
just what I wanted to hear (but was afraid to ask).
I was wondering about that and tried it once and failed - now will
try again. Though the
dhcpcd can pass whatever Mac address you want to a dhcp server ...
> -Original Message-
> From: Eric Smith [SMTP:[EMAIL PROTECTED]
> Sent: Wednesday, November 21, 2001 1:14 AM
> To: Debian User
> Subject: eth0 <-> eth1
>
> According to dman on Tue, Nov 2
According to dman on Tue, Nov 20, 2001 at 08:14:49PM -0500:
> On Tue, Nov 20, 2001 at 07:10:19PM +0100, Eric Smith wrote:
> | Its been quite a saga - I have lost my (limited) hacking instinct.
> | Having failed to get ipmasq to work on 2.2.19 (possibly something to
> | do with eth
According to Daniel Serodio on Tue, Nov 20, 2001 at 07:20:01PM -0200:
> If your NIC's are different, try creating a file in /etc/modutils (eg,
> 'nic') with eg:
>
> alias eth0 ne2k-pci
> alias eth1 fealnx
>
> Run 'update-modules'. Then 'apt-get install ipmasq'. That's how I do it
> (a
75 matches
Mail list logo
