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 debian-isp-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
Reply to: