-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New issue with openconnect/vpn-slice due to env change? #148
Comments
Yeah, it's just that
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. |
IPv6 requires a minimum MTU of 1280. If MTU is <1280, it appears that any-and-all IPv6-related configuration, including setting addresses and routes, will immediately fail on Linux, where iproute(8) gives very cryptic errors like: RTNETLINK answers: Invalid argument error This will prevent vpn-slice from completing a working setup even for IPv4. Rather than overlooking this problem or silently ignoring IPv6 configuration issues, we should *fail* when IPv6 configuration is requested but the MTU is too small, and request that the user add `--disable-ipv6` to the OpenConnect command line, which should prevent OpenConnect from requesting or providing any IPv6 configuration to vpn-slice. Ping #148.
IPv6 requires a minimum MTU of 1280. If MTU is <1280, it appears that any-and-all IPv6-related configuration, including setting addresses and routes, will immediately fail on Linux, where iproute(8) gives very cryptic errors like: RTNETLINK answers: Invalid argument error This will prevent vpn-slice from completing a working setup even for IPv4. Rather than overlooking this problem or silently ignoring IPv6 configuration issues, we should *fail* when IPv6 configuration is requested but the MTU is too small, and request that the user add `--disable-ipv6` to the OpenConnect command line, which should prevent OpenConnect from requesting or providing any IPv6 configuration to vpn-slice. Ping #148.
IPv6 requires a minimum MTU of 1280. If MTU is <1280, it appears that any-and-all IPv6-related configuration, including setting addresses and routes, will immediately fail on Linux, where iproute(8) gives very cryptic errors like: RTNETLINK answers: Invalid argument error This will prevent vpn-slice from completing a working setup even for IPv4. Rather than overlooking this problem or silently ignoring IPv6 configuration issues, we should *fail* when IPv6 configuration is requested but the MTU is too small, and request that the user add `--disable-ipv6` to the OpenConnect command line, which should prevent OpenConnect from requesting or providing any IPv6 configuration to vpn-slice. Ping #148.
@mebigfatguy, please test cd40123. If OpenConnect provides IPv6 configuration and a too-small MTU,
|
IPv6 requires a minimum MTU of 1280. If MTU is <1280, it appears that any-and-all IPv6-related configuration, including setting addresses and routes, will immediately fail on Linux, where iproute(8) gives very cryptic errors like: RTNETLINK answers: Invalid argument error This will prevent vpn-slice from completing a working setup even for IPv4. Rather than overlooking this problem or silently ignoring IPv6 configuration issues, we should *fail* when IPv6 configuration is requested but the MTU is too small, and request that the user add `--disable-ipv6` to the OpenConnect command line, which should prevent OpenConnect from requesting or providing any IPv6 configuration to vpn-slice. Ping #148.
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
The text was updated successfully, but these errors were encountered: