Closed Massimo-B closed 1 year ago
VPNC is only exposing the set MTU as environment variable (https://github.com/streambinder/vpnc/blob/master/src/vpnc.c#L351-L366). That value is not handled in any way, but only exposed: it should be picked up by vpnc-scripts (the one originally linked to this repo is https://git.infradead.org/users/dwmw2/vpnc-scripts.git) during interface creation. If it does not work, you should talk to them :)
Forwarded to https://gitlab.com/openconnect/vpnc-scripts/-/issues/61 I'm using vpnc via networkmanager-vpnc, it is still an issue of vpnc-scripts?
I'm using vpnc via networkmanager-vpnc, it is still an issue of vpnc-scripts?
It's an issue of whatever wrapper is that you're using: if networkmanager-vpnc is, then that's the one to blame, imho :)
I see. But anyway, for debugging I used vpnc from command line and it was failing, so the vpnc-scripts bug report is well placed.
It's working now...
Changing the MTU either by
--ifmtu 1180
of byInterface MTU 1180
in the config does not have any effect. The created tun0 interface always has MTU 1500.Trying that for nested VPN, a nested vpnc fails with the default MTU of 1500. Trying to manually set in the background
ip link set dev tun0 mtu 1180
doesn't seem to solve it.