Well, I guess I am a bit thick headed. I have been working on setting up a nstreme2 backhaul, lets say tower1 and tower2. I finally have the radios associated but I cannot pass data, ping or tracert to the laptops from either side. Test layout is like this.
laptop 64.xxx.xxx.xxx (represents core router at our ds3) ether1 >
(tower1) ether1 64.xxx.xxx.xxx, wlan1 10.0.4.1/30 (tx), wlan2 10.0.4.5/30 (rx) >
(tower2) wlan1 10.0.4.2/30 (rx), wlan2 10.0.4.6/30 (tx), ether1 10.0.4.17/28 >
(laptop) ether1 10.0.4.18/28 (represents rest of the network).
I then tried setting up routing much the same way as I would using just ap and clients like I have on other backhauls. Didn’t work.
Default route on tower1 is 64.xxx.xxx.xxx thru ether1. I tried setting default route on tower2 to 10.0.4.5 (the rx on tower one) and got an invalid route. Also any routing on tower1 that refers to ip addresses after tower2 show invalid. Anything direct connect in the routing table works. From the laptop 64.xxx.xxx.xxx I can ping all the way to 10.0.4.6 (tower2 tx). I cannot ping 10.0.4.17 or the laptop off of tower2 and traceroute stops at the tower1 ether1 address.
So, any help would be appreciated. I am just not getting the routing with nstreme2 and cannot pass data onward through the network.
tk
EDIT: A mistake. I had 10.0.4.6 on tower1 also by mistake. So after correcting that address to 10.0.4.5 I cannot ping to tower2 after all. I can ping anything on the tower my laptop is connected to. I cannot ping across the link. If I break the nstreme2 and set the link up as ap and client it does work. So I know the radios etc are good.
Sure could use some help.
tk