I have a blunder. I am fairly new to Mikrotik, but have successfully deployed before. I use the product as just an AP-bridge normally. Internet comes into the board, and is re-dispersed via the WLAN. I use tranzeos as the client antennas. Works great.
But this new setup i can’t seem to get to work. Rather than the internet coming into the Mikrotik via the ethernet cable, i am trying to share it route it from on of the client side.
Basically i have a RB133 on top of a silo with an Omni attached. I have two clients, client A and client B. The internet exists at Client A site. And i want to be able to access internet at Client B side. The antennas both link to the Mikrotik just fine, i can even get to the router at Client A side from Client B side. However internet traffic will not pass from B to A. I initially felt that i had an issue with my IP addressing, but being able to log into the router from client B side tells me that it is correct.
Because i am new, i am not sure what steps to take to figure this one out.
put eth1 and wlan1 onto the same bridge group at a,b and the silo unit
then try setting the ap to ‘ap bridge’, the clients to ‘wds slave’. Also be sure to set wds to ‘dynamic’ and in the drop down box below that pick the bridge you created.
you will also need to create a route at the ap. basically a route that tells all traffic were to look for the gateway, the ip of b should be the route if that is internet side
I had a similar first time issue. I was able to ping all the way across but not surf. the above got me straightened out. Lots of ways to do it though. If this is too vague let me know and I’ll get more concise. I am using Router OS 4.6 but the gui should be pretty much the same.
under ip go to routes. (It might not be under ip in the winbox menu depending on what version of ROS you are using)
Once you are in routes define the ip address and netmask etc. In Mikrotik you can just put in 192.168.1.1/24 for a class c for example rather than filling in the fields for netmask and broadcast. do this on the internet side radio.
the second (far)radio will need something like 192.168.1.2/24 and a second route that directs all internet traffic to your gateway. (0.0.0.0/0 for all destinations and gateway of 192.168.1.1/24)