Messages

1

23.1 Legacy Series / Re: Policy Based Routing Issues

« on: May 28, 2023, 02:32:46 am »

So it's always DNS, but I don't know what setting I'm missing that would allow it to work on the default gateway and not the WAN.

2

23.1 Legacy Series / Re: Policy Based Routing Issues

« on: May 27, 2023, 06:06:37 pm »

So I did some further testing and I can assign a VPN as the gateway on VLAN 120 or VLAN 69 and it gets an internet connection without any problem. But still can't assign the WAN. I attempted to make a WAN group with just the WAN in and it doesn't work either.

So there's something with the WAN I'm missing I think?

3

23.1 Legacy Series / Policy Based Routing Issues

« on: May 27, 2023, 03:15:18 pm »

I recently updated to 23.1.8 and started having an issue. The first issue was VPN gateways not getting IP addresses for the actual gateway, I resolved this by allowing them to pull routes and I thought all was well. But I discovered later one of my secondary LANs for my wife and guest stopped working IF the VPNs pull routes and I try to force those VLANs out of the WAN4 gateway.

I'm not using IPv6 inside of my network. VLAN 20 has always used the WAN4 gateway option vice default. VLAN 120 and 69 have used the default. When I try to force them out WAN4 they just stop routing traffic out. The firewall logs show the traffic passing out of the VLAN. I've attached screenshots of NAT and Firewall rules. Any ideas here I'm at a loss as I've tried everything that makes sense.

JLAN is VLAN69
LAN is VLAN20