I have three SXT’s Like this:
1( -------)2
---------)3
Unit 1: Level 4 license (as AP)
Unit 2: Level 3 license (as Station)
Unit 3: Level 3 license (as Station)
They are very close together and should be within the 25 degree range-distances are about 100meters or less.
I have configured a 192.168.1.x subnet between the wlan interfaces and they all talk to each other great.
I can route between the ether1 interfaces just fine but here is my problem: I can only get one SXT station to route to clients behind the ether1 interface.
What am I missing here? 
How are the ethernet ports set for each client (unit2 and unit3) as far as ip/subnets?
add: The ethernet port is normally 192.168.88.1/24 on those devices. You will need to change one of them to a different subnet if you want to route to devices on the client localnets.
Here are the IP settings:
Unit 1: (ether1) 10.104.1.1/24 (wlan)192.168.88.104/24
Unit 2: (ether1) 10.54.1.1/24 (wlan)192.168.88.54/24
Unit 3: (ether1) 10.53.1.1/24 (wlan)192.168.88.53/24
I guess I was lazy and just used the default 192.168.88.0/24 subnets as a starting point to get the group talking to each other. Is this a special subnet or something?
Also I can ping all these IPs, its just that, for example, if I attach a hub to Unit 3 and try and ping 10.53.1.20 from Unit 1 I get nothing but if I do the same thing to Unit 2 and ping 10.54.1.20 then it works and that client is able to route through the system.
BTW - thanks for taking a look at this.
Have you routed all the subnets? It should be like this in the Unit 1 router:
/ip route
add dst-address=10.54.1.0/24 gateway=192.168.88.54
add dst-address=10.53.1.0/24 gateway=192.168.88.53
Insure all the 192.168.88.1/24 assignments are removed from the ether1 interface. No masquerades in the Unit2 and Unit3 routers.
Yep, those routes exist.
# DST-ADDRESS PREF-SRC GATEWAY DISTANCE
0 A S 0.0.0.0/0 10.104.1.2 1
1 S 10.53.1.0/24 192.168.88.53 1
2 A S 10.54.1.0/24 192.168.88.54 1
3 ADC 10.104.1.0/24 10.104.1.1 ether1 0
I am in the process of setting up a test rig and see if I can duplicate the issue.
If I can I will post some configs.
Well I got it working. I have no idea why it wasn’t working in the first place. One thing that makes this much easier is enabling RIP routing so I don’t accidentally mistype a route here or there.
One thing that caught me while testing this, the default config on the SXT’s has a masquerade rule that I needed to delete.
No onto fix a hotspot problem…
Thanks for the help. 