im having an issue when setting up a hotspot on a bridged interface.
bridge1 = eth + wlan
for some reason and i’ve tested this if i set the hotspot interface to bridge1, i lose connectivity on winbox and the hotspot system doesnt work but the wireless with its default routes work fine.
is the hotspot creating a set of firewall rules that block for some reason ?
edit:
upon ping the device, where it worked before i get a ping prohibited.
yes i have, im not sure if the firewall rules/NAT rules are causing a problem.
once the bridge and hotspot and pools and interface bridge has been done.
i’m unable to ping it from a device on the same network as the bridge interface.
i get the following from my linuxbox:
From 10.4.10.106 icmp_seq=1 Destination Net Prohibited
From 10.4.10.106 icmp_seq=2 Destination Net Prohibited
From 10.4.10.106 icmp_seq=3 Destination Net Prohibited
since my linux box is on the same network it doesn’t suggest its a routing issue but more likely a firewall of some sort:
i have the default hotspot firewall/nat rules in place from using the hotspot setup option which works perfectly fine if i dont use a bridge interface.
it seems it creates all the firewall rules for the hotspot feature during which you specify the interface which i did “bridge1”
something in the firewall rules prevents any kind of connectivity to it over LAN, but if i try from my phone wirelessly it shows ( i think still testing that theory )
i understand the functionality of the hotspot i’ve managed to get it to work perfectly with radius even & so far everything is great,
i just have an issue trying to run Hotspot feature on top of a bridge.
it appears that the bridge works fine without the hotspot feature setup on it.
if i apply the hotspot feauture select the bridge, i lose connectivity to the LAN side of the bridge, the troubleshooting i’ve done , i’ve isolated the problem to possibly the default firewall rules that are generated by the hotspot setup configuration wizard.
i disable all the firewall rules & hotspot … then im able to connect now problems.
Did you try opening the browser? Since you put the hotspot on a bridge, it works on all directions. It means you have to log into the captive portal until you can access your router and other things.
the config is correct, its a firewall behavior by looks of things… I’m sure its blocking connectivity
here is a ping of my mikrotik, before and after the hotspot was enabled using the wizard.
Before Hotspot Setup with Wizard
64 bytes from 10.4.10.106: icmp_seq=417 ttl=64 time=0.247 ms
64 bytes from 10.4.10.106: icmp_seq=418 ttl=64 time=0.227 ms
64 bytes from 10.4.10.106: icmp_seq=419 ttl=64 time=0.243 ms
64 bytes from 10.4.10.106: icmp_seq=420 ttl=64 time=0.207 ms
64 bytes from 10.4.10.106: icmp_seq=421 ttl=64 time=0.209 ms
64 bytes from 10.4.10.106: icmp_seq=422 ttl=64 time=8.54 ms
64 bytes from 10.4.10.106: icmp_seq=423 ttl=64 time=0.431 ms
After Hotspot Wizard was used
From 10.4.10.106 icmp_seq=424 Destination Net Prohibited
From 10.4.10.106 icmp_seq=425 Destination Net Prohibited
From 10.4.10.106 icmp_seq=426 Destination Net Prohibited
From 10.4.10.106 icmp_seq=427 Destination Net Prohibited
From 10.4.10.106 icmp_seq=428 Destination Net Prohibited
From 10.4.10.106 icmp_seq=429 Destination Net Prohibited
From 10.4.10.106 icmp_seq=430 Destination Net Prohibited
From 10.4.10.106 icmp_seq=431 Destination Net Prohibited
I attempted to connect to wifi and it works but hotspot doesnt come up, clearly something not right specifically to do with the hotspot setup
by default hotspot block the icmp protocol, if you want to ping the hotspot interface then you need to add the walled garden accept entry that allows the protocol=icmp
Also after you have logged in the hotspot you should be able to ping the router.
Also reconsider you network structure as currently if you enable the hotspot on the bridge then the default gateway should also be logged into the hotspot as the hotspot is working on all the bridged ports.
I would suggest to move the Hotspot to the default gateway router and leave the wifi bridged routers act only as wireless bridge.
Go to “walled garden IP list”
Klik on the blue cross
Do what you see in printscreen (by server stand hotspot you must set to bridge from hotspot)
This will make you can ping to the hotspot.
To login with winbox you will first need to log in to the hotspot
Once the default hotspot firewall rules were setup then i couldn’t “manage” the mikrotik.
I’ve literally tried everything i dont think this is impossible but more a firewall behavior with the “default hotspot rules” wether it be in the Firewall Filter or Firewall NAT rules.
I have exactly the same problem with Groove A-52Hpn.
If i use the “wlan1” interface since the hotspot setup, the hotspot function doesn’t work (but the wifi connection is ok, i have well internet with the wifi).
If i use the “bridge-local” interface :
If i have already connected with wifi before hotspot setup, the login page of the hotspot setup is well displayed.
If i make a new wifi connection, impossible to obtain an IP from access point DHCP server.
Impossible to connect with winbox after hotspot setup and this from ethernet or wifi access (http and Telnet)
Have you solved this problem ?
What is the correct configuration .