[driverloader] HowTo: multiple interface and APs?

[Linuxant Support (Jonathan)]

Hi,

you can force DriverLoader to use a specific wireless interface by using the 
'dldrconfig --netdevname' command in a root shell. For example, you want that 
DriverLoader uses 'eth1' as wireless interface, you can use the following 
command in a root shell :

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

You could put this in a script to do want do you want. For example, you 
configure both 'eth1' and 'eth2' with the 'redhat-config-network' tool and 
you use the following 2 scripts to select which interface to use :

Script : dldrupeth1
---
#!/bin/sh

dldrstop
dldrconfig --netdevname=eth1
ifup eth1
---

Script : dldrupeth2
---
#!/bin/sh

dldrstop
dldrconfig --netdevname=eth2
ifup eth2
---

However, it is possible that there is something even more simple to do in your 
situation. Simply set the ESSID of both of your access point at the same 
value and use a single wireless interface (for example eth1) for 
DriverLoader. In the case where both access point are accessible at the same 
time, i.e. the coverage of both access point overlap at this position, the 
Windows driver should select the access point that have a better signal with 
your wireless card.

Regards,


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


Le 22 Juin 2004 23:35, Fred Welland a écrit :
> -New to driverloader
> -Using linux for a while
> -Toshiba tecra 8100 + Netgear WG511 + DLink AP and SMC AP
> -RH 9 (pretty vanilla)
>
> I installed DriverLoader via RPM and fed it my Windows driver for the
> WG511.  The works fine and connects to my D-Link AP fine.
>
> Added another AP to my network (to fix a dead spot).  Now I want to do
> this:
>
> eth0 - be my normal wired PCMCIA card
> eth1 - be WG511/DriverLoader pointing to one AP (ssid & channel)
> eth2 - be WG511/DriverLoader pointing to the other AP (ssid & channel)
>
> Generally I use the redhat-* tools to tinker with stuff and I use the
> DriverLoader web configurator to do stuff to wg511.  I can't figure out how
> to get DriverLoader to use any interface ID other than eth0.
>
> Could someone give me a nudge or two in the correct direction on how to set
> this up?  How can I make driverloader 'bind' to eth1 and/olr eth2?
>
> Ultimately, I'd like to use 'redhat-network-config' to just
> activate/de-activate interface depending on where I am.
>
> Thanks for you help,
>
>
>
>
>
>
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader