Make a static DNS name like hotspot.local and map it to 10.1.0.1 and make sure clients can resolve that. Set the name and address of the hotspot in all hotspot profiles to that name and address.
Sorry, I was reading this on a phone right after getting up and apparently got fairly confused. Ignore all that, and just read this post.
The idea is to have an IP address that ALL Hotspots respond to.
First make an IP address that’s always up - either another physical interface, or a loopback interface (empty bridge). Then map your Hotspot name to that IP address. Then use that IP address and name for all three Hotspots (maybe adjust that final command below as it edits ALL Hotspot profiles, you may want to change the three relevant ones one by one manually).
Now all users on all Hotspots can do status-y things and interact with the Hotspot servlets by going to ‘hotspot.local’ or 172.31.255.255.
I do this with Hotspots stacked on VLAN interfaces, and use the IP address/name of the physical interface for all VLAN Hotspot instances. Works a treat.
You’re trying to reach a device behind eth1 with its proper IP address of 10.0.3.0/24 from a device behind eth0 with its proper IP address of 10.0.0.0/24?
That doesn’t require a bridge, that’s just routing. Both are directly connected networks, so the router will route between them.
If that isn’t working then the most likely causes are, in order:
host firewalls on the hosts. Traffic is being routed just fine, but the hosts are dropping it. Windows Vista and 7 introduced the concept of zones where most traffic is only permitted from the local network. Check host firewalls
hosts are misconfigured and aren’t using the router as the default gateway for return traffic. Check host routing tables, and that you can access the Internet
the router firewall has been configured to drop the traffic - by default with factory settings it would permit it.
I think that the 3th is the correct one. But i check inside firewall of RB1100 and the only rules are about hot-spot. Normally traffic thought lan’s is permitted and generally i had some rules to block them.
Also , i don’t ping from RB1100 hosts on lans. Only arp-ping work.
Do you have address pools configured on the Hotspot profiles, or the Hotspot user profiles? If so you’re poison ARPing the network. Change the address pools to ‘none’, and try again.
lan1 10.0.0.1/20
lan2 10.0.3.1/24
lan3 10.5.50.1/24
lan4 loop-back for hotspot 172.0.0.1/32
arp is enable on all
and tree PPPoE server ( one for lan )
internet → 192.2.0.32/24
inside firewall , only tree rules : srcnat with masquerate for all lan and PPPoE
The strange is that : from lan1 ping gw lan3 (10.5.50.1 ) , no ping from lan1 to gw lan2 ( 10.0.3.1) , ping from lan2 to gw lan1(10.0.0.1) and gw lan3(10.5.50.1) !!!