On Fri, 25 Jul 2003, Tom Ball wrote: > Is there a way to assign a specific module to eth devices in the ip link > table? I'd like to know the answer to this one as well.. Who actually does the assignment of the names 'eth0' 'eth1' etc.. aliases in modules.conf don't appear to help here. The first loaded driver is automatically assigned eth0. > On my laptop, something is calling "ip link" or its equivalent > when the busses are scanned for my wireless card (pcmcia) and docking > station ethernet (PCI). The problem is that when I boot docked the PCI > buss is scanned first so the ethernet driver gets assigned eth0, while > when booted standalone the wireless gets eth0 because there's no PCI > buss. RedHat's network package requires device aliases in > /etc/modules.conf, so half the time networking fails due to mismatched > cards and devices. actually the redhat network stuff don't need the entry in modules.conf Perhaps the following might work for you.. 1. have the same wireless settings for eth0 and eth1 in redhat-config stuff (neat) 2. comment out the eth0,eth1 bindings in modules.conf 3. comment out HWADDR stuff in /etc/sysconfig/networking/devices/ifcfg* now the following configs should work: eth0 - wired eth1 - wireless eth0 - wireless eth1 - wired I use the same config settings for both a wired and wireless card (both pcmcia). And I do some extra tings to get multiple profile stuff working (for home and work wireless settings) Satish > > I've hacked this by rmmod'ing both drivers after buss scanning and > before pcmcia is loaded, so that ifup reloads them in the right order. > Is there a better way to enforce which card/driver gets assigned to > eth0? Perhaps a way to suppress a module from being loaded when its bus > is being scanned? Or a way for network drivers to not be installed in > the ip link table when loaded? > > Tom > > > > -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
