Hello,

I just recently noticed that there is a column in the host section of the hotspot called Bridge Port. We are in a situation where we will have the network completely VLANed off, and would like to see what VLAN a guest is currently on. This greatly helps us with locating a guest as well as troubleshooting a network.

I am however unable to get this to display anything other than "unknown". We always put our hotspots on a bridge, and then assign ports or VLANs to that bridge as the need requires.

Does anyone know how to get this to display this information properly for us? I have tried a test out here in the office where I added two VLANs to a bridge with the Mikrotik connected to a managed switch with two clients on different VLANs, I have also tried assigning multiple physical interfaces to the bridge, and in both cases it only displayed "unknown" for the hosts.

Any assistance with this would be greatly appreciated. Thanks.

huh... according to the manual http://wiki.mikrotik.com/wiki/Hotspot#ip_hotspot_host :

bridge-port (read-only; name) : /interface bridge port client connected to, value is unknown when HotSpot is not configured on the bridge

what version do you use?

We've been using 4.5. I tried it also in 4.6 and got the same results. I upgraded to 5.0 beta here on my test box and it worked, and when I downgraded to 4.5 again to work on some other things, for some reason it started working like it should of.

Right now we're working on a way around it because it has the same information in /interface bridge hosts, just not as nicely formatted . So I think we're going to try and use that for now.

Did you figure out why your ports were showing up as unknown under hotspot hosts? Mine are showing up as unknown on my bridged hotspot w. 4.1, upgraded to 4.9 to find same results.

Not knowing what vlan hotspot users are on doesnt bother me, but may indicate an incorrect setup by chance? Cant figure out how upgrading to beta than downgrading back would fix it.

regards,

jason

No we never really figured it out. It appears on some boxes sometimes, and others we get nothing. You can get basically the same information if you go to /interface bridge hosts. That is what we are using for now for this information, it's just not presented as nicely as it would be directly from the hotspot.

same on my 4.5, bridge-port hotspot topology with vrrp, so many unknown bridged port

now revert back to old version (2.9.51)

I have the same issue on 5 of 7 routerboard 1000's running 4.13. Two of which work just fine. The ip hotspot host bridge-port column is properly populated, the other 5, just show unknown. This is critical for proper functionality on the Dude.

I use this column to quickly triangulate offending users on my network. I'm providing Mikrotik-based wireless solution at 7 of our high school campuses here in Tempe, Arizona, USA.

Any light brought onto this issue would be greatly helpful or appreciated.

Ian

Hi,

I wanted to bump this thread as im having the same issue. I just moved my HS from 2.9.51 (where clicking on a host in ip->hotspot->hosts would show the correct bridge port which in my case are EoIP tunnels).

Now on v5.5 everything works great (better Hotspot performance under heavy load too!) but when i click on any host the "Bridge Port" shows "unknown"

This is a very useful feature for me like the other poster above, it allows me to track down the source/location of any issues, or users.

in this thread there was a soltuion to this same problem (changing the mac addresses of the EoIP tunnels on both sides, however that did not work for me)

http://forum.mikrotik.com/viewtopic.php?f=3&t=31126


anyone have a solution or idea? mikrotik?
tks

was just working with mindtool on this one again today - still a problem using 5.5 even. Is anyone at MT looking into this?

setting should fix your problem.

Thanks that fixed the issue for me!

Thats what Sam (changeip) and I figured out. Pretty cool.

Something else that Sam and I also noticed is that when we use L2TP tunnels in the place of EoIP tunnels mainly for improved efficiency and lower CPU overhead than EoIPs... We would use L2TP tunnels with MRRU's set at 1600 and a profile attaching specific L2TP tunnels to a bridge in the same manner as the EoIPs as described...

Now, the unknown thing is back but only with the L2TP tunnels... could this be a limitation of something or a bug? This is while EoIPs are working correctly under the Bridge Port column in ip-hotspot-hosts table.

The interface-bridge-host table shows the L2TP tunnels mapped to the right tunnel... but not in ip-hotspot-hosts Bridge Port column. This is true when interface-bridge-settings use-ip-firewall=yes.

Thanks,
Ian

mindtool

Now, the unknown thing is back but only with the L2TP tunnels... could this be a limitation of something or a bug? This is while EoIPs are working correctly under the Bridge Port column in ip-hotspot-hosts table.

Thank you very much for the report.
We have similar report about unknown port for dynamic L2TP tunnel on HotSpot server. We are working on the issue.

Awesome. Thanks Sergejs.

Ian