I've been having a play with my WRT54GL/OpenWrt.
Currently it's set up with the house wireless network (WPA). I wanted to
experiment with adding a publically accessible net, firewalled off from the
rest of the house and limited to a fraction of the available external
bandwidth. Just for the fun of it.
The recipe for doing this on these boxes is to create an extra VLAN that's not
connected to any port and bridge it to the wireless device. You then set up a
new wireless ESSID etc.
I found some warning that Windows can get confused by a single AP with two
ESSID, but once I had it all working the house Windows box saw both networks
and connected to one or the other without a hitch.
Sad to say, my laptop, with Debian Sid/b43/NetworkManager failed. Network
Manager would only show one of the nets, and attempts to connect to either
the visible one or the other (by entering the ESSID by hand) failed. I had to
disable the new public network and go back to a single wireless network to
get the laptop connected again.
Anybody have any clues as to where the problem is likely to lie?
NetworkManager is probably my favourite - a manual scan with 'iwlist wlan0
scanning' shows both ESSID - but I guess it could be wpa_supplicant or even
the b43 driver.
--
Jim Hague - jim.hague@??? Never trust a computer you can't lift.
