Suddenly, a new connection error

[Dave Brosius]

I figured it out, i had to add

--disable-ipv6

to options, i guess something on my phone hotspot changed, in some way.

On Sun, Jan 21, 2024 at 12:02 PM Dave Brosius <mebigfatguy at gmail.com> wrote:
>
> Sorry some more details
>
> Am using v8.05-1
>
> and it turns out the VPN DOES work, however i still get that
>
> RTNETLINK answers: Invalid argument
>
> the vpn slice does not, so perhaps i'll ask in that project.
>
> Also, it used to be the case when ctrl-c was hit on openconnect, it
> would remove itself. This no longer seems to be the case and i have to
> close the terminal in which it was run. Not a problem for me, just
> maybe another clue to the puzzle.
>
> thanks, again.
> dave
>
> On Sat, Jan 20, 2024 at 7:41 PM Dave Brosius <mebigfatguy at gmail.com> wrote:
> >
> > Hi folks, i've been using openconnect with vpn-slice for many years
> > now as a user, and haven't had any troubles with it. Thanks!
> >
> > However today, when i try to connect, i get
> >
> > Connected as 10.69.12.166 + 2606:b400:600:c063::11c/64, using SSL,
> > with DTLS in progress
> > Established DTLS connection (using GnuTLS). Ciphersuite
> > (DTLS1.2)-(ECDHE-RSA)-(AES-256-GCM).
> > Detected MTU of 1182 bytes (was 1280)
> > RTNETLINK answers: Invalid argument
> > Error: ipv4: Invalid values in header for route get request.
> > Usage: ip route { list | flush } SELECTOR
> >        ip route save SELECTOR
> >        ........
> >        ........
> >
> > So I tried openconnect without vpn-slice and the problem still remains
> >
> > The only thing on my end that changed was my phone (which i'm
> > hotspoting thru) got an upgrade.
> >
> > Anyone have any suggestions on what i can do to fix or diagnose this?
> >
> > thanks
> > dave