Re: Eth*'s and they corresponding hardwares
On Tue, 4 May 2004 04:49:39 -0300 UnKnown <[EMAIL PROTECTED]> wrote: : Hi ppl, got an intresting problem here, the other day I compile : kernel 2.4.25 for the main router it has 5 ethernet cards 3 : realtek 1 tulip and 1 ne2000 everithing whent fine untill the boot : proces was over and I try to conect to the network. For some : reason what in the previous kernel was one eth in the new kernel : is another, aparently the kernels load the eths in a diferent way. : : The old one load them in this order : : eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 : eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 : eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 : eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 : eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D : : While the new one load in this order : : eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 : eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D : eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 : eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 : eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 : : So some of the ethernets get mix up and the net doesnt work : properly. I could reconfig, the route iptables and other stuff to : work arround. But I was wondering if there is a way to bind a : sertein ethernet "hardware" to an specific eth device. : : If anyone has a clue with it I'll apreciate any direction, I'm : over the kernel doc but as I'm not really expert on it is taking : me no ware. So any clue would be well came. Although I haven't had to deal with it using later kernels, I resolved this problem some years ago by resetting the i/o base address on each nic. ie 0x310 0x320 0x330 etc. I then added an 'ether' command for each at boot time. ie ether = 5, 0x310, 12, 0x3c509, eth0 - where these correspond to the desired irq, base i/o address, transciever type, address conflict flag and interface. I know networking has been upgraded since, and I'm not sure if this would still work, and on tulip cards, but I'd be interested to know. Something else to try, hope it helps, bill
Re: Eth*'s and they corresponding hardwares
On Tue, 4 May 2004 04:49:39 -0300 UnKnown <[EMAIL PROTECTED]> wrote: : Hi ppl, got an intresting problem here, the other day I compile : kernel 2.4.25 for the main router it has 5 ethernet cards 3 : realtek 1 tulip and 1 ne2000 everithing whent fine untill the boot : proces was over and I try to conect to the network. For some : reason what in the previous kernel was one eth in the new kernel : is another, aparently the kernels load the eths in a diferent way. : : The old one load them in this order : : eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 : eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 : eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 : eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 : eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D : : While the new one load in this order : : eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 : eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D : eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 : eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 : eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 : : So some of the ethernets get mix up and the net doesnt work : properly. I could reconfig, the route iptables and other stuff to : work arround. But I was wondering if there is a way to bind a : sertein ethernet "hardware" to an specific eth device. : : If anyone has a clue with it I'll apreciate any direction, I'm : over the kernel doc but as I'm not really expert on it is taking : me no ware. So any clue would be well came. Although I haven't had to deal with it using later kernels, I resolved this problem some years ago by resetting the i/o base address on each nic. ie 0x310 0x320 0x330 etc. I then added an 'ether' command for each at boot time. ie ether = 5, 0x310, 12, 0x3c509, eth0 - where these correspond to the desired irq, base i/o address, transciever type, address conflict flag and interface. I know networking has been upgraded since, and I'm not sure if this would still work, and on tulip cards, but I'd be interested to know. Something else to try, hope it helps, bill -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
Thxs a lot ppl thats was exatly what i was looking for, I'm trying it this week end. If u dont have word from me then I'll have to read things more carefully but it will sertenlly work out. Thx to u all. Posibles solutions, some ramdom order. -Switch cables. -Use modules, and load them in the proper way, (not suitable for me but) -PCMCIA/WIRELESS support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Orinoco Settings" NICKNAME="laptop01" ESSID="home_AP" MODE="Managed" RATE="auto" ;; -nameif (man 8 nameif) this sound cool just to have a net call servers, dnz, newbys, really rocks :) -hard code your mac addresses in the config file /etc/network/interfaces #man interfaces defines how auto eth0 iface eth0 inet static hwaddr 00:20:18:10:72:76 address 199.105.37.102 netmask 255.255.255.0 broadcast 199.105.37.255 gateway 199.105.37.1 -Steve Haavik point me to te following links/man pages This was discussed here a couple months back. http://lists.debian.org/debian-isp/2004/01/msg00292.html And a quick search on Google turned this up. http://www.xenotime.net/linux/doc/network-interface-names.txt interfaces(5) Debian bug #101728." /usr/share/doc/ifupdown/examples/network-interfaces.gz. with some words detailing what would i have to go trough - Last but defenitly not least Robert Tasarz give some, for what i see, personal exps. in the topic. I'll read this with care and try to go for it if I get to the cleaver solution, ill post it. Cya and thx to u all, rak On Tue, May 04, 2004 at 04:49:39AM -0300, UnKnown wrote: > Hi ppl, got an intresting problem here, the other day I compile kernel > 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip > and 1 ne2000 everithing whent fine untill the boot proces was over and > I try to conect to the network. For some reason what in the previous kernel > was one eth in the new kernel is another, aparently the kernels load the > eths in a diferent way. > > The old one load them in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > > While the new one load in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > > So some of the ethernets get mix up and the net doesnt work properly. > I could reconfig, the route iptables and other stuff to work arround. > But I was wondering if there is a way to bind a sertein ethernet "hardware" > to an specific eth device. > > If anyone has a clue with it I'll apreciate any direction, I'm over the > kernel doc but as I'm not really expert on it is taking me no ware. So any > clue would be well came. > > Cheers, > rak > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Eth*'s and they corresponding hardwares
Thxs a lot ppl thats was exatly what i was looking for, I'm trying it this week end. If u dont have word from me then I'll have to read things more carefully but it will sertenlly work out. Thx to u all. Posibles solutions, some ramdom order. -Switch cables. -Use modules, and load them in the proper way, (not suitable for me but) -PCMCIA/WIRELESS support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Orinoco Settings" NICKNAME="laptop01" ESSID="home_AP" MODE="Managed" RATE="auto" ;; -nameif (man 8 nameif) this sound cool just to have a net call servers, dnz, newbys, really rocks :) -hard code your mac addresses in the config file /etc/network/interfaces #man interfaces defines how auto eth0 iface eth0 inet static hwaddr 00:20:18:10:72:76 address 199.105.37.102 netmask 255.255.255.0 broadcast 199.105.37.255 gateway 199.105.37.1 -Steve Haavik point me to te following links/man pages This was discussed here a couple months back. http://lists.debian.org/debian-isp/2004/01/msg00292.html And a quick search on Google turned this up. http://www.xenotime.net/linux/doc/network-interface-names.txt interfaces(5) Debian bug #101728." /usr/share/doc/ifupdown/examples/network-interfaces.gz. with some words detailing what would i have to go trough - Last but defenitly not least Robert Tasarz give some, for what i see, personal exps. in the topic. I'll read this with care and try to go for it if I get to the cleaver solution, ill post it. Cya and thx to u all, rak On Tue, May 04, 2004 at 04:49:39AM -0300, UnKnown wrote: > Hi ppl, got an intresting problem here, the other day I compile kernel > 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip > and 1 ne2000 everithing whent fine untill the boot proces was over and > I try to conect to the network. For some reason what in the previous kernel > was one eth in the new kernel is another, aparently the kernels load the > eths in a diferent way. > > The old one load them in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > > While the new one load in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > > So some of the ethernets get mix up and the net doesnt work properly. > I could reconfig, the route iptables and other stuff to work arround. > But I was wondering if there is a way to bind a sertein ethernet "hardware" > to an specific eth device. > > If anyone has a clue with it I'll apreciate any direction, I'm over the > kernel doc but as I'm not really expert on it is taking me no ware. So any > clue would be well came. > > Cheers, > rak > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
Hi, Pierre Fagrell wrote: > UnKnown wrote: > >Hi ppl, got an intresting problem here, the other day I compile kernel > >2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip > >and 1 ne2000 everithing whent fine untill the boot proces was over and > >I try to conect to the network. For some reason what in the previous kernel > >was one eth in the new kernel is another, aparently the kernels load the > >eths in a diferent way. > > [snip] > One easy and quick fix though, would be to just swap the ethernet cables > around. First - forcing mac address not always works. At least some time ago it didn't work with my realtek 8139 card. Second - even if it works - you have different mac, but still the same interface name connected with card. So, if you don't want to touch your ip/fw config files, you need to switch cables anyway. And that's not always easy or even possible (mixed copper/fiber links). Third - if you are lucky enough and using Sid or Sarge - install ifrename package. Still, problem is because ifrename isn't resolving temporary name conflicts, so simple swapping names of two interfaces isn't possible with standard config. One of solutions is to have two config files (one for temporary interface names) and starting ifrename two times. Here's example config files: /etc/iftab.temp: eth_0 mac 00:20:18:10:72:76 eth_1 mac 00:48:54:66:C3:B2 eth_2 mac 00:48:54:67:CC:88 eth_3 mac 00:48:54:66:C9:75 eth_4 mac 00:80:AD:3C:24:2D /etc/iftab: eth0 mac 00:20:18:10:72:76 eth1 mac 00:48:54:66:C3:B2 eth2 mac 00:48:54:67:CC:88 eth3 mac 00:48:54:66:C9:75 eth4 mac 00:80:AD:3C:24:2D Now make some init.d script with: ifrename -f /etc/iftabl.temp ifrename And run it before ifupdown. It works with 2.6.5 kernel and I think should work with 2.4.x as well. Regards Robert Tasarz
Re: Eth*'s and they corresponding hardwares
You could just hard code your mac addresses in the config file. /etc/network/interfaces #man interfaces defines how auto eth0 iface eth0 inet static hwaddr 00:20:18:10:72:76 address 199.105.37.102 netmask 255.255.255.0 broadcast 199.105.37.255 gateway 199.105.37.1 iface eth1 inet static hwaddr 00:20:18:10:72:75 address 199.105.37.100 netmask 255.255.255.0 broadcast 199.105.37.255 gateway 199.105.37.1 > On 04/05/04 04:49 -0300, UnKnown wrote: > Hi ppl, got an intresting problem here, the other day I compile kernel > 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip > and 1 ne2000 everithing whent fine untill the boot proces was over and > I try to conect to the network. For some reason what in the previous kernel > was one eth in the new kernel is another, aparently the kernels load the > eths in a diferent way. > > The old one load them in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > > While the new one load in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > > So some of the ethernets get mix up and the net doesnt work properly. > I could reconfig, the route iptables and other stuff to work arround. > But I was wondering if there is a way to bind a sertein ethernet "hardware" > to an specific eth device. > > If anyone has a clue with it I'll apreciate any direction, I'm over the > kernel doc but as I'm not really expert on it is taking me no ware. So any > clue would be well came. > > Cheers, > rak > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- -- Ted Knab Chester, Maryland 21619 USA -- Conquest is easy. Control is not. -- Kirk, "Mirror, Mirror", stardate unknown
Re: Eth*'s and they corresponding hardwares
Hi, Pierre Fagrell wrote: > UnKnown wrote: > >Hi ppl, got an intresting problem here, the other day I compile kernel > >2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip > >and 1 ne2000 everithing whent fine untill the boot proces was over and > >I try to conect to the network. For some reason what in the previous kernel > >was one eth in the new kernel is another, aparently the kernels load the > >eths in a diferent way. > > [snip] > One easy and quick fix though, would be to just swap the ethernet cables > around. First - forcing mac address not always works. At least some time ago it didn't work with my realtek 8139 card. Second - even if it works - you have different mac, but still the same interface name connected with card. So, if you don't want to touch your ip/fw config files, you need to switch cables anyway. And that's not always easy or even possible (mixed copper/fiber links). Third - if you are lucky enough and using Sid or Sarge - install ifrename package. Still, problem is because ifrename isn't resolving temporary name conflicts, so simple swapping names of two interfaces isn't possible with standard config. One of solutions is to have two config files (one for temporary interface names) and starting ifrename two times. Here's example config files: /etc/iftab.temp: eth_0 mac 00:20:18:10:72:76 eth_1 mac 00:48:54:66:C3:B2 eth_2 mac 00:48:54:67:CC:88 eth_3 mac 00:48:54:66:C9:75 eth_4 mac 00:80:AD:3C:24:2D /etc/iftab: eth0 mac 00:20:18:10:72:76 eth1 mac 00:48:54:66:C3:B2 eth2 mac 00:48:54:67:CC:88 eth3 mac 00:48:54:66:C9:75 eth4 mac 00:80:AD:3C:24:2D Now make some init.d script with: ifrename -f /etc/iftabl.temp ifrename And run it before ifupdown. It works with 2.6.5 kernel and I think should work with 2.4.x as well. Regards Robert Tasarz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
This was discussed here a couple months back. http://lists.debian.org/debian-isp/2004/01/msg00292.html And a quick search on Google turned this up. http://www.xenotime.net/linux/doc/network-interface-names.txt The manpages for interfaces(5) has a note at the end stating "The ifup and ifdown programs work with so-called "physical" interface names. These names are assigned to hardware by the kernel. Unfortunately it can happen that the kernel assigns different physical interface names to the same hardware at different times; for example, what was called "eth0" last time you booted is now called "eth1" and viceversa. This creates a problem if you want to configure the interfaces appropriately. A way to deal with this problem is to use mapping scripts that choose logical interface names according to the properties of the interface hardware. See the get-mac-address.sh script in the examples directory for an example of such a mapping script. See also Debian bug #101728." So, depending on your setup, you might not have to do a real lot. Just look at the examples in /usr/share/doc/ifupdown/examples/network-interfaces.gz.
Re: Eth*'s and they corresponding hardwares
You could just hard code your mac addresses in the config file. /etc/network/interfaces #man interfaces defines how auto eth0 iface eth0 inet static hwaddr 00:20:18:10:72:76 address 199.105.37.102 netmask 255.255.255.0 broadcast 199.105.37.255 gateway 199.105.37.1 iface eth1 inet static hwaddr 00:20:18:10:72:75 address 199.105.37.100 netmask 255.255.255.0 broadcast 199.105.37.255 gateway 199.105.37.1 > On 04/05/04 04:49 -0300, UnKnown wrote: > Hi ppl, got an intresting problem here, the other day I compile kernel > 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip > and 1 ne2000 everithing whent fine untill the boot proces was over and > I try to conect to the network. For some reason what in the previous kernel > was one eth in the new kernel is another, aparently the kernels load the > eths in a diferent way. > > The old one load them in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > > While the new one load in this order > > eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 > eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D > eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 > eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 > eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 > > So some of the ethernets get mix up and the net doesnt work properly. > I could reconfig, the route iptables and other stuff to work arround. > But I was wondering if there is a way to bind a sertein ethernet "hardware" > to an specific eth device. > > If anyone has a clue with it I'll apreciate any direction, I'm over the > kernel doc but as I'm not really expert on it is taking me no ware. So any > clue would be well came. > > Cheers, > rak > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- -- Ted Knab Chester, Maryland 21619 USA -- Conquest is easy. Control is not. -- Kirk, "Mirror, Mirror", stardate unknown -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
This was discussed here a couple months back. http://lists.debian.org/debian-isp/2004/01/msg00292.html And a quick search on Google turned this up. http://www.xenotime.net/linux/doc/network-interface-names.txt The manpages for interfaces(5) has a note at the end stating "The ifup and ifdown programs work with so-called "physical" interface names. These names are assigned to hardware by the kernel. Unfortunately it can happen that the kernel assigns different physical interface names to the same hardware at different times; for example, what was called "eth0" last time you booted is now called "eth1" and viceversa. This creates a problem if you want to configure the interfaces appropriately. A way to deal with this problem is to use mapping scripts that choose logical interface names according to the properties of the interface hardware. See the get-mac-address.sh script in the examples directory for an example of such a mapping script. See also Debian bug #101728." So, depending on your setup, you might not have to do a real lot. Just look at the examples in /usr/share/doc/ifupdown/examples/network-interfaces.gz. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
UnKnown wrote: Hi ppl, got an intresting problem here, the other day I compile kernel 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip and 1 ne2000 everithing whent fine untill the boot proces was over and I try to conect to the network. For some reason what in the previous kernel was one eth in the new kernel is another, aparently the kernels load the eths in a diferent way. The old one load them in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D While the new one load in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 So some of the ethernets get mix up and the net doesnt work properly. I could reconfig, the route iptables and other stuff to work arround. But I was wondering if there is a way to bind a sertein ethernet "hardware" to an specific eth device. If anyone has a clue with it I'll apreciate any direction, I'm over the kernel doc but as I'm not really expert on it is taking me no ware. So any clue would be well came. Cheers, rak I don't know how to do that except with modules, but I suppose you compiled the drivers in the kernel? One easy and quick fix though, would be to just swap the ethernet cables around. Regards Pierre Fagrell
Re: Eth*'s and they corresponding hardwares
UnKnown wrote: Hi ppl, got an intresting problem here, the other day I compile kernel 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip and 1 ne2000 everithing whent fine untill the boot proces was over and I try to conect to the network. For some reason what in the previous kernel was one eth in the new kernel is another, aparently the kernels load the eths in a diferent way. The old one load them in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D While the new one load in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 So some of the ethernets get mix up and the net doesnt work properly. I could reconfig, the route iptables and other stuff to work arround. But I was wondering if there is a way to bind a sertein ethernet "hardware" to an specific eth device. If anyone has a clue with it I'll apreciate any direction, I'm over the kernel doc but as I'm not really expert on it is taking me no ware. So any clue would be well came. Cheers, rak I don't know how to do that except with modules, but I suppose you compiled the drivers in the kernel? One easy and quick fix though, would be to just swap the ethernet cables around. Regards Pierre Fagrell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
You have to use nameif (man 8 nameif). With nameif you can establish an association between the MAC address & the name of the interface. Btw, you could also use fancy names, sometimes is better to write "iptables -I INPUT -i dmz -p tcp --dport 80 -j ACCEPT" than "iptables -I INPUT -i eth2 -p tcp --dport 80 -j ACCEPT" Good luck! Mensaje citado por MB <[EMAIL PROTECTED]>: > How does that work when he/she has got 3 of the same model nic? > Somehow you should be able to reference each card (MAC) with a > specific setup. With pcmcia cards you can specify a config for each > MAC address. > > Much like my wireless setup: > > # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) > # Note : wvlan_cs driver only, and version 1.0.4+ for encryption > support > *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) > INFO="Orinoco Settings" > NICKNAME="laptop01" > ESSID="home_AP" > MODE="Managed" > RATE="auto" > ;; > > Mark > > > --- Robert Waldner <[EMAIL PROTECTED]> wrote: > > > > On Tue, 04 May 2004 04:49:39 -0300, UnKnown writes: > > >But I was wondering if there is a way to bind a sertein ethernet > > "hardware" > > >to an specific eth device. > > > > I just compile the drivers as modules and load them in the desired > > order. If you do it otherwise, you're always at the mercy of the > > BIOS > > anyway. > > > > cheers, > > &rw > > -- > > / Ing. Robert Waldner | Security Engineer | CoreTec IT-Security > ><[EMAIL PROTECTED]> | T +43 1 503 72 73 | F +43 1 503 72 73 x99 / > > > > > > > > > ATTACHMENT part 2 application/pgp-signature > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] >
Re: Eth*'s and they corresponding hardwares
You have to use nameif (man 8 nameif). With nameif you can establish an association between the MAC address & the name of the interface. Btw, you could also use fancy names, sometimes is better to write "iptables -I INPUT -i dmz -p tcp --dport 80 -j ACCEPT" than "iptables -I INPUT -i eth2 -p tcp --dport 80 -j ACCEPT" Good luck! Mensaje citado por MB <[EMAIL PROTECTED]>: > How does that work when he/she has got 3 of the same model nic? > Somehow you should be able to reference each card (MAC) with a > specific setup. With pcmcia cards you can specify a config for each > MAC address. > > Much like my wireless setup: > > # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) > # Note : wvlan_cs driver only, and version 1.0.4+ for encryption > support > *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) > INFO="Orinoco Settings" > NICKNAME="laptop01" > ESSID="home_AP" > MODE="Managed" > RATE="auto" > ;; > > Mark > > > --- Robert Waldner <[EMAIL PROTECTED]> wrote: > > > > On Tue, 04 May 2004 04:49:39 -0300, UnKnown writes: > > >But I was wondering if there is a way to bind a sertein ethernet > > "hardware" > > >to an specific eth device. > > > > I just compile the drivers as modules and load them in the desired > > order. If you do it otherwise, you're always at the mercy of the > > BIOS > > anyway. > > > > cheers, > > &rw > > -- > > / Ing. Robert Waldner | Security Engineer | CoreTec IT-Security > ><[EMAIL PROTECTED]> | T +43 1 503 72 73 | F +43 1 503 72 73 x99 / > > > > > > > > > ATTACHMENT part 2 application/pgp-signature > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
How does that work when he/she has got 3 of the same model nic? Somehow you should be able to reference each card (MAC) with a specific setup. With pcmcia cards you can specify a config for each MAC address. Much like my wireless setup: # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Orinoco Settings" NICKNAME="laptop01" ESSID="home_AP" MODE="Managed" RATE="auto" ;; Mark --- Robert Waldner <[EMAIL PROTECTED]> wrote: > > On Tue, 04 May 2004 04:49:39 -0300, UnKnown writes: > >But I was wondering if there is a way to bind a sertein ethernet > "hardware" > >to an specific eth device. > > I just compile the drivers as modules and load them in the desired > order. If you do it otherwise, you're always at the mercy of the > BIOS > anyway. > > cheers, > &rw > -- > / Ing. Robert Waldner | Security Engineer | CoreTec IT-Security \ > \ <[EMAIL PROTECTED]> | T +43 1 503 72 73 | F +43 1 503 72 73 x99 / > > > > ATTACHMENT part 2 application/pgp-signature
Re: Eth*'s and they corresponding hardwares
How does that work when he/she has got 3 of the same model nic? Somehow you should be able to reference each card (MAC) with a specific setup. With pcmcia cards you can specify a config for each MAC address. Much like my wireless setup: # Lucent Wavelan IEEE (+ Orinoco, RoamAbout and ELSA) # Note : wvlan_cs driver only, and version 1.0.4+ for encryption support *,*,*,00:60:1D:*|*,*,*,00:02:2D:*) INFO="Orinoco Settings" NICKNAME="laptop01" ESSID="home_AP" MODE="Managed" RATE="auto" ;; Mark --- Robert Waldner <[EMAIL PROTECTED]> wrote: > > On Tue, 04 May 2004 04:49:39 -0300, UnKnown writes: > >But I was wondering if there is a way to bind a sertein ethernet > "hardware" > >to an specific eth device. > > I just compile the drivers as modules and load them in the desired > order. If you do it otherwise, you're always at the mercy of the > BIOS > anyway. > > cheers, > &rw > -- > / Ing. Robert Waldner | Security Engineer | CoreTec IT-Security \ > \ <[EMAIL PROTECTED]> | T +43 1 503 72 73 | F +43 1 503 72 73 x99 / > > > > ATTACHMENT part 2 application/pgp-signature -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Eth*'s and they corresponding hardwares
On Tue, 04 May 2004 04:49:39 -0300, UnKnown writes: >But I was wondering if there is a way to bind a sertein ethernet "hardware" >to an specific eth device. I just compile the drivers as modules and load them in the desired order. If you do it otherwise, you're always at the mercy of the BIOS anyway. cheers, &rw -- / Ing. Robert Waldner | Security Engineer | CoreTec IT-Security \ \ <[EMAIL PROTECTED]> | T +43 1 503 72 73 | F +43 1 503 72 73 x99 / pgpHlnLW4iIzd.pgp Description: PGP signature
Eth*'s and they corresponding hardwares
Hi ppl, got an intresting problem here, the other day I compile kernel 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip and 1 ne2000 everithing whent fine untill the boot proces was over and I try to conect to the network. For some reason what in the previous kernel was one eth in the new kernel is another, aparently the kernels load the eths in a diferent way. The old one load them in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D While the new one load in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 So some of the ethernets get mix up and the net doesnt work properly. I could reconfig, the route iptables and other stuff to work arround. But I was wondering if there is a way to bind a sertein ethernet "hardware" to an specific eth device. If anyone has a clue with it I'll apreciate any direction, I'm over the kernel doc but as I'm not really expert on it is taking me no ware. So any clue would be well came. Cheers, rak
Re: Eth*'s and they corresponding hardwares
On Tue, 04 May 2004 04:49:39 -0300, UnKnown writes: >But I was wondering if there is a way to bind a sertein ethernet "hardware" >to an specific eth device. I just compile the drivers as modules and load them in the desired order. If you do it otherwise, you're always at the mercy of the BIOS anyway. cheers, &rw -- / Ing. Robert Waldner | Security Engineer | CoreTec IT-Security \ \ <[EMAIL PROTECTED]> | T +43 1 503 72 73 | F +43 1 503 72 73 x99 / pgp0.pgp Description: PGP signature
Eth*'s and they corresponding hardwares
Hi ppl, got an intresting problem here, the other day I compile kernel 2.4.25 for the main router it has 5 ethernet cards 3 realtek 1 tulip and 1 ne2000 everithing whent fine untill the boot proces was over and I try to conect to the network. For some reason what in the previous kernel was one eth in the new kernel is another, aparently the kernels load the eths in a diferent way. The old one load them in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth2 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth3 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 eth4 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D While the new one load in this order eth0 Link encap:Ethernet HWaddr 00:20:18:10:72:76 eth1 Link encap:Ethernet HWaddr 00:80:AD:3C:24:2D eth2 Link encap:Ethernet HWaddr 00:48:54:66:C3:B2 eth3 Link encap:Ethernet HWaddr 00:48:54:67:CC:88 eth4 Link encap:Ethernet HWaddr 00:48:54:66:C9:75 So some of the ethernets get mix up and the net doesnt work properly. I could reconfig, the route iptables and other stuff to work arround. But I was wondering if there is a way to bind a sertein ethernet "hardware" to an specific eth device. If anyone has a clue with it I'll apreciate any direction, I'm over the kernel doc but as I'm not really expert on it is taking me no ware. So any clue would be well came. Cheers, rak -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
