[driverloader] Switch back and forth between interfaces?

Jonathan Baron baron at psych.upenn.edu
Wed Aug 25 09:50:11 EDT 2004

On 08/25/04 08:30, burgeke at HQ.VerizonWireless.com wrote:
>Quick question which I just stumbled onto and recalled wondering about in
>the past.
>Take this scenario:
>Laptop boots with eth1 enabled which grabs IP from DHCP - this device is
>driverloader (2100b card), eth0 is set to not start on boot. Box comes up
>and all is well, I can get out to the net no problem. I fire up Fedora's
>(FC2 BTW) network applet and deactivate eth1 (driverloader) and activate
>eth0 (local onboard nic). Now, I can work with eth0 no problem as well and
>get out to the network. Now, deactivate eth0 and attempt to reactivate eth1,
>and eth1 can not get an IP from the DHCP server nor associate with the
>access point. Happens every time... Not sure why but this has followed me
>from FC1 to FC2 when using the driverloader software.
>Note that all is fine if I use ipw2100 but I prefer to use driverloader
>since for whatever reason javahmo (tivo soft) won't work with the ipw2100
>driver (java barfs with network errors for some reason).
>Anyway, hope I made some sense and others could maybe shed light.

I had a similar problem, and I ended up configuring the network
card as eth2, and driverloader as eth1 (I think - if you want
details I'll get them later - you can send me email off the
list).  Then I could use the network and driverloader and go back
and forth from one to the other with no problem.  The trick for
me was to make sure that the definitions in /etc/modprobe.conf,
/etc/sysconfig/hwconf, and /etc/sysconfif/network-scripts all
agreed with each other about which device was which, and which
was associated with which driver.  (The drivers were in
modprob.conf.)  I had to do a lot of this by hand rather than
relying on system-config-network.

Jonathan Baron, Professor of Psychology, University of Pennsylvania
Home page: http://www.sas.upenn.edu/~baron

More information about the driverloader mailing list