Quote from: tiermutter on November 25, 2023, 10:53:37 pmQuote from: novel on November 25, 2023, 10:45:19 pmYes , It working, but I disabel wan_dhcp to work. It is not correct way...How to fix it?For me, this is not the proper way. Maybe just a matter of mind, I don't know, never tried / tested this...Connection to VPN is now still established... but what will happen after connection loss / reboot? Without WAN GW OPNsense WG client will not be able to connect... will it?Changing priority instead of disabling WAN GW would be better, but -as said maybe a matter of mind- not the righteous way to go...Normally gateway must automatically when enable or disable the vpn, but in my case not happen. So I have to change to 253 the vpn gateway?
Quote from: novel on November 25, 2023, 10:45:19 pmYes , It working, but I disabel wan_dhcp to work. It is not correct way...How to fix it?For me, this is not the proper way. Maybe just a matter of mind, I don't know, never tried / tested this...Connection to VPN is now still established... but what will happen after connection loss / reboot? Without WAN GW OPNsense WG client will not be able to connect... will it?Changing priority instead of disabling WAN GW would be better, but -as said maybe a matter of mind- not the righteous way to go...
Yes , It working, but I disabel wan_dhcp to work. It is not correct way...How to fix it?
I don't understand.
Rule on LAN, destination port 443, gateway WAN_DHCP.
... placed before your existing "default allow" with gateway set to your VPN.Why do you want that rule? Sure you only want non-443 traffic to go through VPN?May I ask what your purpose is?
Ok, but... You initial mission was to route everything via VPN due to limitations of your country... Now all https will go through WAN, with only a little part going through VPN...?!Would ne better to put those "some sites" into an alias and only route them via WAN...
First create an alias where you put in all sites you want ro reach via WAN.Then go to last created rule where WAN GW is set and put the alias as destination.
Lower value for priority is correct, yes.But you also need to mark WAN DHCP as upstream GW.Monitor IP for your VPN GW is a google DNS IP. OPNsense / dpinger will ping trhis IP periodically to determine whether the gateway is up or not. I prefer public IPs for this case since adding VPN endpoint IP here does not mean that connection to WAN over VPN is working. It is just diagnostics, but this IP will also ALWAYS be routed over VPN gateway, regardless of other configurations.Unsure about your last question... what do you mean?