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've only seen this once, on an Ubuntu host using wg-quick and Network Manager. The connection worked but they were unable to use SSH because of timeouts. The issue was resolved by editing the wg config to specify the MTU:
I don't think we can really do anything here since we don't want to lower the MTU for users that don't have issues. But maybe we can document this in a FAQ and add an option flag to set the MTU when the config is generated?
The text was updated successfully, but these errors were encountered:
I've only seen this once, on an Ubuntu host using
wg-quick
and Network Manager. The connection worked but they were unable to use SSH because of timeouts. The issue was resolved by editing the wg config to specify the MTU:Seems to be the same as this issue: https://askubuntu.com/questions/1229456/ssh-fails-with-connection-timed-out-in-vpn-and-hangs-here-expecting-ssh2-msg
Relevant info:
https://lists.zx2c4.com/pipermail/wireguard/2017-December/002201.html
https://www.ovpn.com/en/faq/client/explanation-mtu
https://fasterdata.es.net/network-tuning/mtu-issues/debugging-mtu-problems/
Possible solution:
I don't think we can really do anything here since we don't want to lower the MTU for users that don't have issues. But maybe we can document this in a FAQ and add an option flag to set the MTU when the config is generated?
The text was updated successfully, but these errors were encountered: