Static Routes broken GT-BE98 Pro 3.0.0.6.102_34491

[historypsi]

Anyone else using static routes noticed this firmware broke them? I can get it up for all of 4 pings before it drops when I readd the route and apply after deleting the route, apply. On the initial apply I can ping the other side through the gateway for the network then all connectivity drops and when it comes back up after applying....nothing. 

The pings are during the time it's applying the route. After it says "Complete" it's back to not pinging. Rolling back to the previous firmware fixes it but all the other issues prior to the new update come back. It's a lose/lose situation.

[historypsi]

Yeah, you should be able to reach the WAN interface of the 2nd router. But the other side if the route is working should be pingable too. I'm currently on the beta release which has MLO in it and that is working for me as far as the static route so I think we can rule that out.

[Saltgrass]

It is late, so I may not be seeing the situation correctly, but I see the same thing in the beta as I see in the latest firmware release.

I still cannot ping the computer attached to the second router.  I will try tomorrow when I am not so sleepy.

[Saltgrass]

So far, no luck with either the 9 version beta or the 33830 version.  The route is showing in the routing table.  So, I must be doing something wrong or you have some setting I don't.

I cannot reset the port forwarding in this version of the firmware but the assigned number should work.

Let me know if you think of anything else regarding the setup for the static route.  Like, are you using a different number for the second router where the third set is different and what would happen if I changed the second router IP to a 192.168.50.128 so the third numbers agree with the first router.

[historypsi]

If you don't mind sharing. What is the network of computer 1 and computer 2? 192.168.50.x and 192.168.100.x? 

[Saltgrass]

Yes, .50 for router 1 and .100 for router 2.  

So, back to this route.

[historypsi]

Got ya, and the interface on the route is set to "LAN" I assume. On the 2nd router did you disable the firewall?

[historypsi]

Also, what if you run the command:

tracert 192.168.100.x  (the IP address of computer 2)

What do you get? Here's mine for example:

My computer went to the gt-be98 first and it said I don't have it so go to Ubnt (ubiquiti router) and then it continued on to the IP of my server because of that static route.

[Saltgrass]

Firewall is disabled on router 2.

I am not bypassing anything, just a simple two router configuration so..

C:\Windows\System32>tracert 192.168.100.1

Tracing route to 192.168.100.1 over a maximum of 30 hops

1 3 ms 3 ms 2 ms GT-BE98_Pro-BA00 [192.168.50.1]
2 5 ms 3 ms 3 ms 192.168.100.1

To the computer on Router 2

C:\Windows\System32>tracert 192.168.100.107

Tracing route to 192.168.100.107 over a maximum of 30 hops

1 5 ms 3 ms 3 ms GT-BE98_Pro-BA00 [192.168.50.1]
2 6 ms 3 ms 3 ms 192.168.50.223
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.

[historypsi]

Was asking about the firewall on the 2nd router because their link that I shared the other day said it had to be turned off. But....your static route is working on the GT-BE98. It's doing what it should by telling computer 1 to go to 192.168.50.223 to find computer 2. So the issue isn't with router 1 as to why you can't get to computer 2. Also you said you can ping 192.168.100.1 correct? If you upgrade your firmware, neither that ping or traceroute should work.

[Saltgrass]

Firewall is off and I can ping router 2, which I could do with the later firmware.  Are you ready for me to go back to the latest firmware and do the trace route with that newer firmware?