On Fri, 7 Aug 2015 19:13:15 -0400 Mike Miller <mtmil...@debian.org> wrote: > Control: reassign -1 network-manager 1.0.4-1 > Control: retitle -1 network-manager: sets VPN tunnel MTU incorrectly > > On Fri, Aug 07, 2015 at 22:31:44 +0300, Matti Koskimies wrote: > > On Fri, 2015-08-07 at 09:19 -0400, Mike Miller wrote: > > > On Fri, Aug 7, 2015 at 13:53:49 +0100, David Woodhouse wrote: > > > > 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? > > > > > > I can verify that going back to NM 1.0.2 and connecting to VPN via NM > > sets the proper MTU on vpn0 and my connection works. > > Ok, thanks, regression seems to be squarely on NM, reassigning again.
I've done some limited testing with the latest version 1.0.6-1 from unstable. So far, the issue seems to be resolved. -- JP
