Open mebigfatguy opened 8 months ago
(I get the RTNETLINK answers: Invalid argument error whether vpn-slice is in the picture or not)
Yeah, it's just that vpn-slice
checks failures much more carefully than the default vpnc-script
, which will simply ignore such errors.
Detected MTU of 1182 bytes (was 1280)
Aaaah, that's the problem. IPv6 requires an MTU of at least 1280 bytes.
Seems like iproute(8) will return this error for any IPv6-related actions you attempt to perform on an adapter that has an MTU of <1280 bytes. In order to resolve this without sloppily ignoring errors, we're going to have to detect (and warn) when MTU is too low for IPv6, and then filter out all subsequent manipulations related to IPv6.
Detected MTU of 1182 bytes (was 1280)
Aaaah, that's the problem. IPv6 requires an MTU of at least 1280 bytes.
@mebigfatguy, please test cd40123.
If OpenConnect provides IPv6 configuration and a too-small MTU, vpn-slice
will intentionally abort and will instruct you to add --disable-ipv6
to the command-line:
MTU of 789 is too small for IPv6 (minimum 1280). Invoke OpenConnect with --disable-ipv6 to configure for IPv4 only
HI folks,
Looking to see if bright folks can help me, I've been using openconnect/vpn-slice for years as a simple user for years w/o issue [thanks!], but today, after a phone update (which i hotspot thru), openconnect and/or vpn-slice aren't working correctly.
openconnect seems to work correctly to the vpn if run without vpn-slice, however i now get this error when connecting
(I get the
RTNETLINK answers: Invalid argument
error whether vpn-slice is in the picture or not)vpn-slice -V
returns `vpn-slice 0.15``sudo vpn-slice --self-test
reports successAny suggestions or help to diagnose/fix this issue would be appreciated.
thanks, dave