@viragomann Thank you for responding, I will proceed with duplicating the rules then.

so upon disabling and re enabling the WAN interface this is when i see the issue occur. the only action that can be taken it seems is to manually select the gateway removing it off the automatic option. restarting the gateway service nor reboot changes its behaviour. Running on 2.6.0-RELEASE (amd64) wonder if anyone else is getting the same issue?

@rcoleman-netgate Thank you very much

@jrhjr No problem here, also I don't unplug my WAN cable... Anyway, one other thing you can try is not failing back to WAN but to another VPN-Client. As far as I have understand you, it is not WAN failing but a VPN-Client. We, in this thread, do use Gateway Groups for VPN-Clients and it is working for us. And btw. not every redmine ticket/issue is affecting everyone.

@johnpoz Thank you kindly for your assistance, I will have to do some thinking and I will report back when I have resolved the issue.

@viragomann Thank you very much for the reply. It has helped me to learn a little more about myself and the community.

@viragomann Thanks for the reply. I'll the setting and give it a test.

@fatherprax no, that's not my problem. I don't use DHCPv6 either. I use RA. My WAN interface requests a 56 prefix instead of just 1 address. and my LAN interfaces are just set to 'track interface' and they get a bunch to give out to their devices. You can go to https://ifconfig.co/ or do a curl -6 https://ifconfig.co/ That should work on your machine, if it doesn't, then you don't have a valid ipv6

Can't figure it out. Since i believe what i need is called router-on-a-stick i made Port 1 to pfSense a trunk. But no matter what i try in the switch settings i cant open the Slate GUI (10.145.130.1) or the Player (10.145.130.2) on my Workstation. Port 1: pfSense Port 3: Slate Port 6: Workstation What is the correct setting: [image: 1668429342212-1.png] [image: 1668429347978-2.png] [image: 1668429356977-3.png] [image: 1668429363242-4.png]

[image: 1668230741737-d9d0f870-9f6d-4b88-bbb9-00dd82775ef9-image.png] Also i tried both WANGW and the failover and the same behavior. For browsing it won't use the primary IP assigned to WANGW