I also forgot to update you. But after numerous (NetworkManager), this problem disappeared on Stretch.
So please feel free to close this bug report, as this problem is not an issue anymore. On Sun, May 29, 2016 at 7:20 PM, Mike Miller <[email protected]> wrote: > On Sun, Oct 18, 2015 at 05:06:21 +0200, Adnan Hodzic wrote: > > Hello, > > > > I've upgraded my whole system to Stretch now, and I can confirm that I > > still have problem which I initially submitted in this bug report. > > > > Please let me know if I can provide you with any additional information > > which could help you resolve it. > > NetworkManager debug logs would be helpful (your earlier logs do not > have debug log level enabled), and ensure you are running the latest NM > 1.2.2. > > As David said earlier, the problem may turn out to be that > NetworkManager just doesn't work well when you configure things behind > its back. I would not be surprised if you are able to debug this and > determine that OpenConnect is behaving correctly, writing the expected > resolv.conf, and NetworkManager is noticing a state change and deciding > to "refresh" resolv.conf with its current internal state of what your > DNS should be, which does not include the Juniper tunnel that you just > brought up. > > Apologies for not seeing this earlier, > > -- > mike >
