Thanks again, a co-worker pointed me to https://bugs.launchpad.net/ubuntu/+source/vpnc-scripts/+bug/1871184 Which looks like my issue, if I'm reading it right it's fixed in debian, but new in ubuntu. I guess it is in the queue to be fixed then. Let me know if I should do anything else for the Ubuntu bug. Mike On Mon, Apr 27, 2020 at 10:29 AM Daniel Lenski <dlenski@xxxxxxxxx> wrote: > > Not sure. The Debian maintainers are aware of the issue: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955016 > > … but it doesn't appear that a recent version has been imported into > the Ubuntu packaging system yet, for some reason; normally Ubuntu > tracks the upstream packages from Debian fairly closely: > https://changelogs.ubuntu.com/changelogs/pool/universe/v/vpnc-scripts/ > > It may be worth filing a bug at https://bugs.launchpad.net and linking > to the upstream Debian bug. > > Dan > > > On Mon, Apr 27, 2020 at 7:56 AM Mike Forsberg <bigmike.f@xxxxxxxxx> wrote: > > > > Thank you this worked great. Will share with the rest of the company. > > > > Any idea when this new script will be included in the version tagged > > for Ubuntu 20.04? > > > > On Sun, Apr 26, 2020 at 8:10 PM Daniel Lenski <dlenski@xxxxxxxxx> wrote: > > > > > > Your VPN is likely using split-excludes, which tell the client that > > > certain Internet-bound traffic should *not* be routed via the VPN, and > > > you're running into a bug in vpnc-script. The bug in handling of > > > split-excludes has existed for a long time, but wasn't obvious until > > > recent versions of iproute2 started giving this error: > > > > > > https://gitlab.com/openconnect/vpnc-scripts/-/merge_requests/5 > > > https://gitlab.com/openconnect/vpnc-scripts/-/merge_requests/6 > > > > > > Upgrade to the last to fix it: > > > > > > https://gitlab.com/openconnect/vpnc-scripts/blob/master/vpnc-script > > > > > > -Dan > > > > > > On Sun, Apr 26, 2020 at 5:30 PM Mike Forsberg <bigmike.f@xxxxxxxxx> wrote: > > > > > > > > First, thank you for the great project. I was very happy with the > > > > version on my old 18.04, but this weekend I upgraded to Ubuntu 20.04; > > > > while I'm able to connect, I do see errors??!?!?! > > > > > > > > I'm connecting with the command > > > > openconnect -b -q --juniper ${GATEWAY} --cafile=${CAFILE} > > > > --user=${USER} --authgroup='OATH Passcode' --passwd-on-stdin > > > > > > > > And see several messages like the following (they are much longer but > > > > appear to be the help text). > > > > > > > > Error: ipv4: Invalid values in header for route get request. > > > > Usage: ip route { list | flush } SELECTOR > > > > ip route save SELECTOR > > > > ip route restore > > > > ip route showdump > > > > ip route get [ ROUTE_GET_FLAGS ] ADDRESS > > > > > > > > Is there some modifications I need to make to use a newer ip route command? > > > > > > > > Again, this is a fresh 20.04 install. > > > > > > > > $ openconnect -V > > > > OpenConnect version v8.05-1 > > > > Using GnuTLS. Features present: TPMv2, PKCS#11, RSA software token, > > > > HOTP software token, TOTP software token, Yubikey OATH, System keys, > > > > DTLS, ESP > > > > Supported protocols: anyconnect (default), nc, gp, pulse > > > > > > > > I do have connection to my work's VPN but it might be slow?? > > > > > > > > Please let me know if you need any more information, > > > > > > > > Mike > > > > > > > > _______________________________________________ > > > > openconnect-devel mailing list > > > > openconnect-devel@xxxxxxxxxxxxxxxxxxx > > > > http://lists.infradead.org/mailman/listinfo/openconnect-devel _______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
