I am on the latest 1.9.0 on an ERL3.
It would appear static routes do not work correctly.
Case: We have a 2nd internal router that is used for VPN.
EdgeRouter: 192.168.2.2 with a /24 behind it.
The VPN router and subnet is 192.168.2.1 with the VPN subnet being 192.168.3.0/24
I add a static route in to the EdgeRouter...
Type: Gateway
Destination: 192.168.3.0/24
Next hop: 192.168.2.1
Distance: 1
So what we are seeing with this static route added (and of course our machine gateways are set to the EdgeRouter), is that ICMP traffic (pings/tracerts) appear to follow the route properly, but TCP/UDP traffic is NOT following this static route properly. I.E. I can't RDP over the site to site VPN.
Fact: This worked before we switch the router to a EdgeRouter (want something more robust than the Linksys that was in there, we are now regretting this decision).
Fact: Adding a static route to a windows machine FIXES this issue, which is proof positive that the EdgeMax is not properly routing the TCP/UDP traffic.
route -p ADD 192.168.3.0 MASK 255.255.255.0 192.168.2.1 METRIC 1
I have never seen a router before that couldn't properly handle internal static routes. This seems like a bit of a critical function of a router. I am pretty disappointed right now, annoyed I've spent 3 hours of otherwise billable time troubleshooting an issue caused by the EdgeRouter. I'm also annoyed as I'm going to have to now add static routes to all machines behind the EdgeRouter to get VPN traffic properly flowing again.
Please look in to the routing functionality of your router.