Andy Willis wrote:

I am not saying this is the best method but it seems to work.  I have the vpc mac driver with tcpip on lan0.  My wired card is configured to use it.  I then have tcpip on lan7 set to my wireless card. I am using dhcp for both the wireless and the wired lans but as you can't have both set to dhcp in the tcpip settings I have not enabled lan7.   I then have the wlan widget set to put my wireless set to dhcp on lan0.  This has allowed me to use the wireless without having to reconfigure anything.  The only thing I do have to do is switch the lan to something other than lan0 and then back to lan0 (in the widget) in order for it to grab it.
Andy

So I assume that lan0 is your TCP/IP interface for the wireless lan card ? If not, I get a bit confused... You should not set the WLAN widget to lan0 to let it issue a DHCP request for the cabled interface...

You should also not set the WLAN monitor to lan7 to prevent DHCP configuration, instead you should modify a given connection profile to not use DHCP.

The reason for both cases is that forthcoming versions of the driver and the WLAN monitor will determine automatically the IP interface associated to the WLAN driver, and then you will not longer be able to select another IP interface. As a result, any IP interface selected and not being the correct IP interface for yourWLAN device, while any of your connection profile is configured to use DHCP or manual configuration, is a _misconfigurarion_. You can currently do so, but it is kind of a misuse. The WLAN monitor is to configure the IP interface of the WLAN device _only_.

Just wanted to make that point clear, as this will definitely change in the future.

BTW, in the forthcoming version of WLAN monitor there will also be a notice in the installatio section that once the WLAN monitor is used for IP configuration of the WLAN device, this should not anylonger be done in the TCP/IP configuration settings notebook as well.

bye, Christian