Hi, By dying I mean the machine completely locks up and is unresponsive to pings or new SSH connections.
There version I believe is the latest on Gitlab; I don’t know why he hasn’t been installing the version from the Debian repositories. I am unfortunately unable to check the system logs currently as I can’t access the system. Many Thanks, Dean > On 25 Mar 2020, at 19:24, Daniel Lenski <dlen...@gmail.com> wrote: > > On Wed, Mar 25, 2020 at 6:35 AM Chester, Dean <d.cheste...@warwick.ac.uk> > wrote: >> >> Hi, >> >> I have a user who uses OpenConnect to connect to a VPN tunnel from within a >> network. The end point he is tunnelling to is a juniper network. The user is >> a sudoer. >> >> The user has been installing OpenConnect on Debian 10 from source; this has >> now killed the box which we don’t have physical access to currently due to >> ongoing global issues. >> > > What does “dying” mean? System completely hangs? What version of > openconnect are you building and running, exactly? (`openconnect > --version`) > >> When he was running ./configure —prefix=<SOME_PATH> the machine died. Does >> this script do anything trying to enumerate a new interface? > > No. OpenConnect does, of course, try to create new tunnel interfaces, > unless you tell it to use an existing tunnel interface with `-i` (see > https://www.infradead.org/openconnect/nonroot.html). > > OpenConnect *does not* create new interfaces as part of the > configuration/compliation process… and even if it tried, it would fail > unless running as root. > >> >> This is a new box we configured a few months ago for this specific reason. >> After he’s done with his tunnel we seem to be unable to access the machine >> again via SSH. >> >> What might be killing the connection and causing us to press the reset >> button on the machine? > > What do the system logs tell you? > > Dan _______________________________________________ openconnect-devel mailing list firstname.lastname@example.org http://lists.infradead.org/mailman/listinfo/openconnect-devel