You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a VPS that works behind a firewall, when it is enabled, it has a MTU of somewhere around 1400. The MTU on the VPN in the container is set to 1500.
The VPS has DDoS protection that will enable my edge firewall when under attack. When my VPS edge firewall is enabled manually, I lose all my VPN connections. I assume an automatic engagement of the firewall would also lose connections as it has the same settings.
In the documentation for the firewall, it states:
UDP fragmentation is blocked (DROP) by default. When enabling the Edge Network Firewall, if you are using a VPN, remember to configure your Maximum Transmission Unit (MTU) correctly. For example, with OpenVPN, you can check MTU test.
My guess is when this firewall is enabled , it sets the MTU lower and disallows fragmentation - which causes my VPN connection to fail.
It would be helpful to have an MTU option in the proton-privoxy config so I can set it to 1400 to test it.
Thanks for your hard work 👍
The text was updated successfully, but these errors were encountered:
I have a VPS that works behind a firewall, when it is enabled, it has a MTU of somewhere around 1400. The MTU on the VPN in the container is set to 1500.
The VPS has DDoS protection that will enable my edge firewall when under attack. When my VPS edge firewall is enabled manually, I lose all my VPN connections. I assume an automatic engagement of the firewall would also lose connections as it has the same settings.
In the documentation for the firewall, it states:
My guess is when this firewall is enabled , it sets the MTU lower and disallows fragmentation - which causes my VPN connection to fail.
It would be helpful to have an MTU option in the proton-privoxy config so I can set it to 1400 to test it.
Thanks for your hard work 👍
The text was updated successfully, but these errors were encountered: