Re: eth0 and eth1 mixed

2005-04-06 Thread Stewart Smith
On Tue, 2005-04-05 at 14:10 -0500, David Stanaway wrote: > # install -m 755 /usr/share/doc/ifupdown/examples/get-mac-address.sh \ > /usr/local/bin An (arguably) better way would be (on 2.6 based systems) cat /sys/class/net/$ETH_DEVICE/address -- Stewart Smith ([EMAIL PROTECTED]) http://www.fl

Re: eth0 and eth1 mixed

2005-04-05 Thread David Stanaway
An alternative way to do this is with interface mapping with the ifupdown scripts. Try: # install -m 755 /usr/share/doc/ifupdown/examples/get-mac-address.sh \ /usr/local/bin add this to your /etc/network/interfaces (Substituting in your mac addresses, see /sbin/ifconfig -a | grep HW) auto e

Re: eth0 and eth1 mixed

2005-04-04 Thread Johannes Berg
On Sun, 2005-04-03 at 10:11 -0400, Tamas K Papp wrote: > Sometimes by powerbook boots believing that eth0 is > > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > eth1394: eth0: Could not allocate isochronous receive context for the > broadcast > channel > > which makes the network u

Re: eth0 and eth1 mixed

2005-04-03 Thread [ATR]Dj-Death
Le dimanche 03 avril 2005 Ã 16:17 +0200, Maximilian Gerlach a Ãcrit : > Try blacklisting eth1394. > Greets, > Maxi > I personnaly prefer this : (in /etc/modutils/something) alias eth0 sungem alias eth1 eth1394 -- Lionel Landwerlin / Dj-Death [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [

Re: eth0 and eth1 mixed

2005-04-03 Thread GONG Jie
On Sunday 03 April 2005 22:11, Tamas K Papp wrote: > Sometimes by powerbook boots believing that eth0 is > > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > eth1394: eth0: Could not allocate isochronous receive context for the > broadcast channel > > which makes the network unreachabl

Re: eth0 and eth1 mixed

2005-04-03 Thread Elimar Riesebieter
On Sun, 03 Apr 2005 the mental interface of Tamas K Papp told: > Sometimes by powerbook boots believing that eth0 is > > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > eth1394: eth0: Could not allocate isochronous receive context for the > broadcast > channel > > which makes the

Re: eth0 and eth1 mixed

2005-04-03 Thread Maximilian Gerlach
Try blacklisting eth1394. Greets, Maxi Am Sonntag, den 03.04.2005, 10:11 -0400 schrieb Tamas K Papp: > Sometimes by powerbook boots believing that eth0 is > > eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) > eth1394: eth0: Could not allocate isochronous receive context for the > bro

eth0 and eth1 mixed

2005-04-03 Thread Tamas K Papp
Sometimes by powerbook boots believing that eth0 is eth1394: eth0: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0) eth1394: eth0: Could not allocate isochronous receive context for the broadcast channel which makes the network unreachable. The sungem ethernet port becomes eth1. I googled for the s