I recently changed over to a RB433 and from an older 2.8.15 OS. Nominally all is now working fine on this HOTSPOT.. But I notice some unexpected phenomena. First my hardware setup:
RB433---Cisco AP342----Cisco 342asBridge---WET54g------Client Computer.
...........Main AP.........Remote Bridge.....ClientRadio.....Client
MainAP = used as center of STAR configuration.
Remote Bridge = (typ of 4 bridges in a STAR configuration around the MainAP)
1) I notice that to insure MAC auto login all the time from a client computer into the HOTSPOT, I have to put BOTH the MAC address of the client computer AND the MAC of the WET54g radio into the user list. On the old setup, I only had to put in the IP of the client computer. Why are BOTH the MAC of the radio AND the MAC of the client computer both required in the user list? I note that MUCH of the time, automatic login works with only the MAC of the client computer in the user list, but NOT all the time.
2) I notice that in the hotspot LOG, that two of my "Cisco AP343 Bridges" are being logged as "trying to log in to the hotsopt". IP=10.5.50.226 and 227 are two of my bridges.) I never saw any indication of that before. See attached LOG (second) image. What can be causing this?
3) I Notice also that IP=10.5.50.226 and 227 are shown in the HOSTS list (below) but my other two bridges are NOT shown there. Why are the bridges shown in the hosts list?
4) I notice in the first image below of the Hotspot HOST page, that the IP addresses in the first column are shown to be transferred to an address in the second column: IE, 10.5.50.3 to 10.5.50.5.
What does this mean?
I will appreciate any information you can help me with.
Thanks!
"Strange" behaviour on MT ver 3.14 on RB433
You do not have the required permissions to view the files attached to this post.
Re: "Strange" behaviour on MT ver 3.14 on RB433
Greetings!
1) The hotspot hosts list shows that the IPs in the left column are being masqueraded as the IPs in the right column. This is normally because they are not getting the IP assignment from your hotspot, or the IP asignment expired. Not a problem.
2) The access points in question probably have some setup that requires a connection to the internet (NTP,DNS,etc). If the other AP stations don't request anything for the idle-timeout period (5min default), they will drop from the host list. Still not a problem.
When the APs try to access the internet, they are stopped by the hotspot. To allow access for your APs,
/ip hotspot ip-binding add address=10.5.50.226 type=bypassed
/ip hotspot ip-binding add address=10.5.50.227 type=bypassed
This could be a problem if the requested info is necessary, like dns or ntp.
This could also be a problem allowing the APs access if some clients on the AP are being masqueraded as the AP. That would give them free/unlimited access.
1) The hotspot hosts list shows that the IPs in the left column are being masqueraded as the IPs in the right column. This is normally because they are not getting the IP assignment from your hotspot, or the IP asignment expired. Not a problem.
2) The access points in question probably have some setup that requires a connection to the internet (NTP,DNS,etc). If the other AP stations don't request anything for the idle-timeout period (5min default), they will drop from the host list. Still not a problem.
When the APs try to access the internet, they are stopped by the hotspot. To allow access for your APs,
/ip hotspot ip-binding add address=10.5.50.226 type=bypassed
/ip hotspot ip-binding add address=10.5.50.227 type=bypassed
This could be a problem if the requested info is necessary, like dns or ntp.
This could also be a problem allowing the APs access if some clients on the AP are being masqueraded as the AP. That would give them free/unlimited access.