I’m trying to use a RB133c for a special project that involves using the router in 12vDC vehicle platform.
I would like to configure the RB133c to associate with whatever open wireless access point happens to be available (possibly creating multiple virtual radios for multiple open access points?) with maybe a script to check internet access at large (and if that access fails, move along to the next available open wireless access point).
Anyone ever tried anything like this?
yes, i am doing this now with a rb532. i stumbled across connect-list, it’s your best friend. disable / untick the ssid in the main wireless config, and then it will automatically connect to any non secure wireless. you have to script the dhcp client however - it won’t renew when a new wireless is used. i have mine setup that within 5 seconds it will hop to whatever one is open : ) if you want scripts let me know.
We used “if not connected then release”. Is yours more elegant? Rarely we’ll get a reconnect before the script runs. Looked at comparing SSIDs but some are the same with different networks…
:global newmac [/int wireless registration get [/int wireless registration find] mac-address ]
:log info ( "Old MAC: " . $oldmac )
:log info ( "New MAC: " . $newmac )
:if ($newmac != $oldmac) do={
:log info "script: remote radio mac changed, processing..."
:global oldmac [/int wireless registration get [/int wireless registration find] mac-address ]
#/int l2tp-client disable l2tp-PortableIP
/ip dhcp-client release wlan-station
:delay 1
/ip dhcp-client renew wlan-station
:log info "script: should have new ip by now."
#/int l2tp-client enable l2tp-PortableIP
} else={
:log info "No change in radio MAC"
}
Went with that one too but ran into a Tropos mesh that had all the same mac but not the same network - go figure. BTW, release implies renew (but renew doesn’t release).
Thanks for the script [not using it yet, but I’m sure it will come in handy].
I’m running into odd problems with the RB133c
I dropped the SSID out (left it unchecked) of the interface configuration for wlan1
added wlan1 to the connect list with “none” at the security profile
setup dhcp-client on wlan1 (gets an IP address and DNS server like a champ with the above now done)
created a wire2wireless bridge that includes both ether1 and wlan1
on the RB133c itself, I can ping out just fine, hostnames resolve, the internet is reachable, etc.
the computer connected to ether1 gets and IP address/default gateway/dns server just fine, but I can’t ping anything besides the RB133c’s wlan1 dhcp issued IP address (can’t even ping the default gateway DHCP hands the ether1 connected computer).
I know I’m probably looking over something blindingly obvious, but it escapes me at the moment…
is your upstream allowing more than 1 ip ? if you bridge wlan and lan you effectively are putting everyone directly on the ISP side, of which most want more money for more IPs.
‘setup dhcp-client on wlan1 (gets an IP address and DNS server like a champ with the above now done)’
also, shouldn’t that dhcp-client go on the bridge interface now (if thats really how you want it setup) ?
why not use masq ?
Sam
why not use masq ?
Want to keep things as simple as possible (the ether1 connected device side simple; not too worried about the RB133c config being simple). Eliminating NAT and keeping things at layer 2 puts me one step (layer) closer to whatever I am opportunistically obtaining my connectivity.
is your upstream allowing more than 1 ip ?
most want more money for more IPs.
not a (my) problem… the bulk of opportunistic wireless will happen through open access points that are already doing the NAT for me.
BTW, I’m testing on a “known good” open access point.
also, shouldn’t that dhcp-client go on the bridge interface now (if thats really how you want it setup) ?
I tried that… same result (fine from the RB133c, nolo contendere from the ether1 connected device that receives an IP address just fine via DHCP).
Not quite sure how to debug this one… I guess it’s time to start capturing packets on various interfaces and compare the results.
this is exactly what I need but where do i put the above code to do it? I can’t seem to get scripts to run, never done one before. My DHCP is not renewing.
What’s the wireless mode of the client?
You know that you need to use the station-pseudobridge mode (only available in the 3.0 ROS) to be able to successfully bridge a wireless station interface?