So played w/ this some and realized w/ the Lost_Duckling mode making it a AP instead of a bridge I can then connect to my normal wlan and get into the web-config. I should then be able to setup the hotel wireless as a new profile and change wlan1 back to a station save and try to connect correct?
Making it a AP is great! I had not tested it. I tested without adding a dhcp-server either, but even if you can't connect to it, it allows connection in the virtual AP to manage it. I love it.
Curious how youd get around a sign in captive portal that you get redirected to automatically? Hotel wireless is open with a captive portal as soon as you connect so not sure how to get around that on the Tik?
First, you need to give captive portals lower priority in the connect list, so that they don't hijack well known authenticated connections. I had lots of problems with it when I had buses passing nearby offering free wifi and my mAP was roaming from the wifi I was connected to them every so and so...
Second, I have managed to log into the portal using the laptop or cellular through the router, but it is sometimes tricky. I need to test it more. Sometimes the captive portals will require some dhcp options, sometimes APs can ban the router if it emits some strange traffic...
One of the problems if you open the mAP to roaming via connect-list is that you might get a dhcp-lease of 24 hours from a given wifi... and then you switch off, go to a different place and switch it on in the same day, and nothing works, plus the router is looking desperately for the wrong gateway, which can get you banned as some APs will have some blacklisting going on. I have a script that will check a series of conditions and release the lease, something like this:
Note that wan-bridge is a bridge with external interfaces: wireless in station mode, sta1, sometimes ether1 if plugged to upstream, might be pwrline-out1...)
# ensure that registration/dhcp lease are current...
{
:if (([:len [/interface bridge host f where mac-address=[/ip arp get [find where address=[/ip dhcp-client get \
[f where interface="wan-bridge"] gateway ]] mac-address ]]]=0) or \
([/interface bridge host get [f where mac-address=[/ip arp get [f address=[/ip dhcp-client get \
[f where interface="wan-bridge" ] gateway ]] mac-address ]] age ]>5s)) \
do={
/log info "releasing dhcp lease on network change"
/ip dhcp-client release [find where interface="wan-bridge"]
/ipv6 dhcp-client release [find where interface="wan-bridge"]
}
}
The idea is: if the gatweay mac address is not in the ARP table or it is there, but has more than 5 seconds of age -> release the dhcp leases (the router will take care of trying to get a new one). If is a way to get layer 2 knowledge (where 802.11 lives) up to a Layer 3 protocol (DHCP)... but can fail if both routers have, say 192.168.1.1 as gateway and it answers. It is acceptable but it needs more work. I have found no scriptable event that serves the purpose.