Control: tags -1 upstream Control: close -1 On Sat, 24 Dec 2022 19:36:39 +0100 "Francesco Poli (wintermute)" <[email protected]> wrote: > Package: openconnect > Version: 9.01-2 > Severity: normal > > Hello and thanks for maintaining this package in Debian! > > I tried it to connect to a Fortinet SSL VPN. > I used the following command: > > # openconnect --prot=fortinet -u $VPNUSER $VPNSERVER > > It worked, in the sense that I was able to connect to the VPN. > > However, when I decided to disconnect, I used [Ctrl+C] to end the > session: the session ended as expected (good!), but I was left with > a non-working network configuration (outside of the VPN). > In other words, openconnect failed to restore the network configuration > that was in place before its invocation! > Even pinging a remote host resulted in "Network unreachable" errors. > > I had to bring my Ethernet network interface down: > > # ifdown $INTERFACE > > and then up again: > > # ifup $INTERFACE > > in order to get back to a working network configuration (this resulted > in obtaining the network parameters back from the DHCP server and > everything was working fine again). > > At the end of the session, I expected openconnect to automatically > restore the network configuration as it had found it at the beginning of > the session. > Please note that another VPN client (package 'openfortivpn', which is > specific for Fortinet VPNs) transparently restores the previous network > configuration, when the user hits [Ctrl+C] to disconnect from the VPN... > > I acknowledge that this misbehavior by openconnect is not a big flaw, > but having to manually issue an ifdown/ifup command is anyway annoying. > > Please fix this issue and/or forward this bug report upstream, as > appropriate.
Please report this upstream -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
