Hi all, I met a problem during my try to make a transparent wds bridge between 2 RB-500series on the first RB i have activated the dhcp and hotspot server on wds interface. the wds is bridged with the wlan 2 which is the backbone for the second routerboard the procedure is like described on wds transparent bridge, The problem is that working ok without the hotspot activated taking ip 10.5.50.x and its working right also the ping between wds 192.168.5.1 and 5.2 working perfect.Once i activated the hotspot doesnt ping the other side i have the login page, i can authenticate but there is no redirection to the web page and after while i have mikrotik proxy timeout . The bypass mac address also working fine.
Probably i something to do with the firewall any ideas?
rb-1
eth1 gateaway 192.168.2.1
wlan1: 10.5.50.1/24
wlan2 10.176.0.1/24 link to rb-2
wds 192.168.5.1
RB-2
wlan1 AP 10.5.52.1/24 (workind the wds perfect )
wlan2 link to rb-1 10.176.0.2/24
wds 192.168.5.2
Which interface has the hotspot assigned? The reason I ask is the wds bridge is supposed to be transparent between the two devices. Makes the two networks one virtual net. I think the hotspot should be on wlan2 maybe? Or maybe a “real” bridge between wlan1 and wlan2 on rb1.
The problem is that for example when the hotspot server is activated on wlan and iam tryng to bridge the both interfaces wlan1 (AP) and wds interface the hotspot and dhcp became inactive, so i activated the dhcp and hotspot in wds interface.
Without hotspot server working great
That is what the hotspot is supposed to do. If you put the hotspot on the wds bridge, it will break the connection. I think you might want to look into setting up a bridge between wlan1 and wlan2 on rb1, and putting the hotspot on that interface.
Thank you for replaying,
This is that I’ve done, but when the hotspot is activated its broke the connection, probably one solution is to find a way to allow the wds ip;s in this case 192.168.51-2, or to create separate hotspots server in each wlan interface but hens probably the roaming doesn’t work…