Hi, sorry for reactivating an old topic. I would like to know if the status is still the same on this issue. It seems absurd to me that we would need to make things so much more complex to simply tell the firewall "if the gateway from the first VTI IPSec is down, use the second VTI IPSec". I am not sure if the implementation is too much of a hassle, but this feature would be greatly appreciated.

@DaHai8 It seems like an odd piece of hardware or at least how they've had it set up. Usually we set up a mesh as well and then roaming isn't a problem. We have I think one home user with an extender and IIRC that's the one where it sets up a different SSID then connects to the main SSID also, to relay the packets. But then one needs to switch between then. FWIW eero can be set up in "bridge mode" to function only as access points. It also can enable a guest network in bridge mode, if desired.

Its both fixed in 2.8.1 beta and 25.07-1 plus release (as expected)

Finally got the new fiber circuit installed. Everything works normally as expected now. It was some voodoo in the Comcast Coax Cable Modem that was blocking return traffic.

Traceroute from the outside world: vpsuser@test:~$ sudo traceroute -I a.b.c.164 traceroute to a.b.c.164 (a.b.c.164), 30 hops max, 60 byte packets 1 daniel.domesticagriculture.org.uk (103.144.176.193) 0.518 ms 0.470 ms 0.457 ms 2 wist.lyle.org (103.144.176.143) 0.479 ms * * 3 100.64.101.167 (100.64.101.167) 10.793 ms 10.781 ms * 4 * * * 5 * * * 6 * * * 7 * * * ... 100.64.101.167 is my router's WG client IP

@daltonch It is called policy based routing. https://docs.netgate.com/pfsense/en/latest/multiwan/policy-route.html

@ElGuapo Make a route using WAN2 to your endpoint-IP-address.

For the benefit of my future self… I’ve got the LTE interface to renew DHCP every 15 minutes. Not ideal, but should be enough to keep me online. Interface / DHCP client configuration / Advanced configuration / “Option modifiers” = “supersede dhcp-lease-time 1800” This requests the max lease time of 30 minutes, so renewal triggers in 1800/2 = 900s (15min)

@viragomann Thanks for the info! ill give that a go and see if I can get it working, knew it was probably something small I'm missing.

@stephenw10 / @marcosm any chance we can relocate this busy/lively thread to the regular Routing and Multi WAN section? It seems it isn't and probably never was specific to 25.07 RC anymore...

I've added an issue on redmine: https://redmine.pfsense.org/issues/16354

@greatbush while I have about 3 minutes here do you realize that windows machines by default will not allow pings and such from outside their own subnet to come in? Just trying to rule out any issues that you might have with Windows firewall on those machines..