[driverloader] Switch back and forth between interfaces?

[Linuxant support (Jonathan)]

Hi,

when you try to bring up the eth1 interface while the eth0 interface is 
down and the module for that interface is removed from the kernel, it is 
possible that the DriverLoader interface will be assigned to eth0 
instead of eth1. To fix this problem, you can force DriverLoader to 
always use the eth1 interface with the following command in a root shell:

---
dldrconfig --netdevname=eth1
---

If it's not the problem, you could try to take a look at your 
'/var/log/messages' file for clues why bringing up the interface failed.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com


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.
> 
> Keith
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader