Question : TTL expired in transit

I've set up a static route on my DD-WRT router:

Destination LAN:  192.168.3.0
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.25

Which is pointing to a NanoStation 2 wireless receiver which is set to router mode and set with WAN IP 192.168.1.25, and LAN IP as 192.168.3.1.  

What's weird here is when I ping 192.168.3.0 I get TTL expired in transit.
When I tracert I get a loop:
1    <1 ms    <1 ms    <1 ms  GCMM.gcmm.net [192.168.1.1]
2     2 ms     2 ms     2 ms  192.168.1.22
3     3 ms     2 ms     2 ms  GCMM.gcmm.net [192.168.1.1]
4     5 ms     4 ms     5 ms  192.168.1.22
5     5 ms     5 ms     4 ms  GCMM.gcmm.net [192.168.1.1]
6     7 ms     6 ms     7 ms  192.168.1.22
7     8 ms     6 ms     7 ms  GCMM.gcmm.net [192.168.1.1]
8    11 ms     8 ms    10 ms  192.168.1.22

Any insights?
     

Answer : TTL expired in transit

Okay, I see your problem. These NanoStations are hybrid devices that operate between layer 2 and layer 3. The way they're basically setup is to define the "default gateway" so that they know where to send traffic. The problem with a "default gateway" is that defines where to send ALL traffic. So the 1.22 device does exactly that... sends all traffic to 1.1 device. The WRT54G, however, has a route to the 3.0 network that says to send it to the 1.110 device. But when NanoStation2 gets the packet, it sends the packet to it's default gateway (1.1) who promptly sends it back.

So there are a couple things.

1) The next hops of any routes should be routers. Not the NanoStations. So on the WRT54G, the next hop for the 3.0 network should be 1.110
2) The only way to move traffic away from the default gateway (1.1) is to create a route on the NanoStations that use the 1.110 device as the next hop. If you can't figure out how to do that, if it can't be done, or if they can't be put into true bridging mode, it won't work.
Random Solutions  
 
programming4us programming4us