On Fri, Aug 7, 2015 at 13:53:49 +0100, David Woodhouse wrote: > On Fri, 2015-08-07 at 08:27 -0400, Mike Miller wrote: >> >> Thanks for the debugging guys, reassigned to NM-openconnect for now. > > Nah, that makes it my fault too! Pass the buck a bit further! > > Seriously, NM-openconnect doesn't really do much with the IP > configuration at all. You can use dbus-monitor to watch what > nm-openconnect-service-openconnect-helper hands back to NM, and I bet > it *will* include the MTU. We haven't really touched that part for > ages. > > I blame NM.
Fair enough. Matt already said that reverting to NM 1.0.2 was enough to restore his connection, but that was while running openconnect standalone. Matt, can you verify that going back to NM 1.0.2 and connecting to the VPN via NM now sets the proper MTU on tun0 and your connection works again? -- mike -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
