Sometimes I can do this, sometimes I can’t. Last time I could I downgraded form 8.5.0 to 8.4.1 MAX BR1 HW3
I have wifi wan connected to a thermostat on 10.10.10.10 I set outbound policy source any destination 10.10.10.10 protocol any enforced wifi wan.
This is rather infuriating. I got it working on 8.4.1 then about an hour later I can no longer ping 10.10.10.10 from LAN or from anywhere besides from the peplink admin gui or cli
@MartinLangmaid can you offer any advice here?
try the priority rule with the single WAN in the list.
i assume the wifi wan is healthy right? green in dashboard?
WiFi wan is green. I set health check to ping 10.10.10.10 what is the priority rule you’re talking about?
I just tried 8.5 beta and again it worked for a while then stopped working. However it wasn’t advertising 10.10.10.0/24 to fusionhub. I explicitly created the router in OSPF and then it failed.
I do need my other WANs up for internet, not currently on site
Seems to be working shortly after updating firmware just pushed 8.5.0 build 5169 again. I had to put 10.10.10.0/24 in OSPF so fusionhub could see it, even though that shouldn’t be required. This was at Oct 6 17:28 UTC will update when it stops working
Around 19:00 UTC just noticed it stopped working. I made no changes
Can confirm I can still ping 10.10.10.10 on wan 3 but not on lan made no changes
Don’t use an enforced outbound policy rule use priority rule instead, make sure to tick terminate sessions on device recovery.
It won’t as it’s a wan connection, by default OSPF only advertises LAN subnets over SpeedFusion. You can add manually select which LANs / WANs get advertised using the Network advertising section in Advanced > OSPF eg:
Don’t add it to ‘Static Route Advertising’ I suspect that is causing you the issue.
When it doesn’t work and you look at Status > Speedfusion VPN on the Fusionhub does it show the 10.10.10.0/24 network there under information column as a remote subnet?
