On Tue, Apr 28, 2020 at 1:22 PM Daniel Lenski <dlenski@xxxxxxxxx> wrote: > > On Tue, Apr 28, 2020 at 10:24 AM John Hendy <jw.hendy@xxxxxxxxx> wrote: > > > > On Mon, Apr 27, 2020 at 7:45 PM Daniel Lenski <dlenski@xxxxxxxxx> wrote: > > > It appears more likely to me that *something other than OpenConnect* > > > is overwriting your /etc/resolv.conf… possibly NetworkManager, > > > possibly dhcpcd… not 100% sure. > > > > Wow, it appears this is exactly what's going on. After resolv.conf > > gets overwritten, if I restore it to the state when I first connect to > > VPN, I still have the connection! > > > > I use wicd for network management. I don't have networkmanager > > installed. I can pursue this in a separate endeavor now that we've > > ruled out openconnect. That said, if you have tips on where I might > > look to figure out why something is hijacking resolv.conf when > > something else is still controlling it, that would be appreciated! > > Seems that wicd invoking dhcpcd is the likely culprit. Perhaps this is relevant? > https://www.linuxquestions.org/questions/slackware-14/how-to-prevent-wicd-overwriting-etc-resolv-conf-4175488551/ Thanks for the help, and apologies for not accurately diagnosing this! I wanted to circle back with the resolution. In looking into wicd, I discovered it's discontinued due to being python2 based (and I suppose they are not migrating to py3). I switched to netctl and just maintained a VPN connection with openconnect for perhaps 3hrs continuously with no problems. It looks like the dhcpcd process was indeed the culprit. With netctl, /etc/resolv.conf remained unchanged the whole time. Thanks again! John _______________________________________________ openconnect-devel mailing list openconnect-devel@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/openconnect-devel
