routing issues

RouterOS General
1

Here is my scenario. 2 towers… one had a MT router and was serving both itself and the remote tower for authentication, ip’s etc. On the remote tower I just replaced 4 radios and a switch with a RB with 4 radios in it. Instead of backhualing with 2.4 I’m now using the 5 Ghz. It’s working great, except for this. Before when both towers were served by the one MT, I had set a range of internal static IPs to be used on all my client’s radios (10.61.32.xxx) so I could monitor them. On the new router on the remote tower I have one of these addresses assigned to the 5 GHz radio as 10.61.32.22/24. However, I can no longer ping the radios being served from this tower from either the old router or the new. I can ping the .22 address from anywhere in the network and I’ve tried assigning addresses in the same range to the other interfaces and can ping them as well. I just can’t reach the client radios on the other side of my new mt. Any suggestions on how I should set up the routing to allow these addresses to be reachable again from either router? here is a simpple diagram in case you are confused.

client radio (10.61.32.xxx/24)–> MT(2.4 AP)10.61.32.24/24–>MT(5GHz station)10.61.32.22/24–>MT(5GHz AP)10.61.32.33/24bridged to ethernet–>switch—>core MT(10.61.32.1/24)

Cameron

2

Cameron,

client radio (10.61.32.xxx/24)–> MT(2.4 AP)10.61.32.24/24–>MT(5GHz station)10.61.32.22/24–>MT(5GHz AP)10.61.32.33/24bridged to ethernet–>switch—>core MT(10.61.32.1/24)

All this stuff must be bridged to make it work. That’s a lot of bridges.

I’d route your MT(5GHz) link, using say, 10.10.15.1 /30 on the AP side, and 10.10.15.2 /30 on the station side. Give your core MT another IP range (perhaps a public), say 10.62.32.1 /30 Setup your MT (2.4 AP) to be 10.61.32.1 /24, and do all your filtering, bandwidth limiting (if you do it on the router) there. Route the 10.61.32.1 /24 down to the core MT, and do your NAT at that point.

Simple…