I am testing a cloud setup at present and having an issue with using the Draytek as a gateway. I think the issue boils down to a static route that I have set up not working on the Draytek.

The set-up is as follows:

Temporary gateway to network 192.168.0.0/25 on network 192.168.1.1/24 = 192.168.1.160
Gateway is pfSense. Currently it is set up to route only so firewall issues are excluded.

Using a number of linux workstations on the 192.168.1.1/24 network, I am able to communicate with all devices on the 192.168.0.0/25 network. To do this, I created a static route on the workstation. Ideally, I want the Draytek to route, but it doesn't. Devices on the 192.168.0.0/25 network can communicate with the Linux workstations on the 192.168.1.1/24 network.

I have set up a static route on the Draytek. The routing status shows:

Code:

Codes: C - connected, S - static, R - RIP, * - default, ~ - private * 0.0.0.0/ 0.0.0.0 via *.*.*.*, WAN1 S~ 192.168.0.0/ 255.255.255.128 via 192.168.1.160, LAN1

I have removed some of the entries (they are not relevant and do not have possible routes that would be chosen. I replaced the WAN1 IP with *.*.*.*

It would appear that WAN1 is chosen in preference to the static route.

Trace routing on the router shows:

Code:

ip tracert 192.168.0.2 traceroute to 192.168.0.2, 30 hops max through WAN1 protocol ICMP 1 Request timed out. * 2 Request timed out. * Trace complete.

I have also tried setting up a load balance rule and adjusting the priority values.

Whatever I do, the Draytek attempts to route via WAN1. Why?

I was using older firmware and have also updated to the latest.

Thanks.

Have you tried using a policy route as well? Alternatively, do you have any policy routes already set up to push traffic over WAN1? If you do, try disabling those because depending on the firmware version, they can over-ride static routes configured on the router.

Thanks for the suggestion. I did have route policies in place and I disabled them. I also tried adding one for the new subnet with these disabled. Rebooted the router to make sure that the routing table was as it should be and still no joy.

I think that the router is simply choosing the default route, even though there is a static route in place. I have tried disabling all load balancing rules, and reached the point where my routing table is:

Code:

Codes: C - connected, S - static, R - RIP, * - default, ~ - private S~ 192.168.0.0/ 255.255.255.128 via 192.168.1.160, LAN1 C~ 192.168.1.0/ 255.255.255.0 is directly connected, LAN1

This was done by issuing the "ip route default off" command to the remote shell. The router still, having rebooted it, attempts to route to the 192.168.0.0 network via WAN1. I smell a bug!