Upstream bug report has been created:
https://bugzilla.gnome.org/show_bug.cgi?id=754781
On Sun, 30 Aug 2015 20:31:25 -0500 Scott Coil
wrote:
> Seems like this commit introduced the regression:
>
> http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=9b79e6c732ffb2fb105647c1465070d36a6cc180
>
>
> I'm including a reversion patch for the relevant piece, though, it is
On Tue, 01 Sep 2015 14:24:25 -0400 "LeJacq, Jean Pierre" "LeJacq, Jean
"LeJacq, Jean Pierre" wrote:
> On Fri, 7 Aug 2015 19:13:15 -0400 Mike Miller wrote:
> > Control: reassign -1 network-manager 1.0.4-1
> > Control: retitle -1 network-manager: sets VPN tunnel MTU incorrectly
> >
> > On Fri, Au
On Fri, 7 Aug 2015 19:13:15 -0400 Mike Miller 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:
>
Seems like this commit introduced the regression:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=9b79e6c732ffb2fb105647c1465070d36a6cc180
I'm including a reversion patch for the relevant piece, though, it is
likely not a clean patch for upstream.
diff --git a/src/nm-ip4-co
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:
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
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 re
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
Control: reassign -1 network-manager-openconnect 1.0.2-1
Control: retitle -1 network-manager-openconnect: sets tunnel MTU incorrectly
On Fri, Aug 7, 2015 at 08:28:04 +0100, David Woodhouse wrote:
> That's a NetworkManager or NM-openconnect bug. We *do* pass that MTU
> value back to NM and expect i
On Fri, 2015-08-07 at 09:10 +0300, Matti Koskimies wrote:
> The MTU value of the tun0 device created when using openconnect on
> the command line was 1200. It was 1500 for the vpn0 device created
> using network-manager-openconnect. So I reduced the mtu value to 1200
> and voilà, everything work
On Thu, 2015-08-06 at 12:29 +0100, David Woodhouse wrote:
> On Thu, 2015-08-06 at 14:18 +0300, Matti Koskimies wrote:
> >
> > Pinging doesn't work, but I don't expect it to in our network.
>
>
> Oh? Your network is infested by idiot admins who like to block ICMP?
> That's almost certainly relev
On Thu, 2015-08-06 at 14:18 +0300, Matti Koskimies wrote:
>
> Pinging doesn't work, but I don't expect it to in our network.
Oh? Your network is infested by idiot admins who like to block ICMP?
That's almost certainly relevant.
> Instead,
> I used netcat for "port pinging" the ssh port:
>
> $
On Wed, 2015-08-05 at 14:34 +0100, David Woodhouse wrote:
> On Wed, 2015-08-05 at 16:19 +0300, Matti Koskimies wrote:
> > Connecting using the GUI still doesn't work, although I get a lot
> > further now. Connecting and authentication works, and everything
> > looks OK in NM. The routing table loo
On Wed, 2015-08-05 at 16:19 +0300, Matti Koskimies wrote:
> Connecting using the GUI still doesn't work, although I get a lot
> further now. Connecting and authentication works, and everything looks
> OK in NM. The routing table looks similar to the one I get using my
> workaround. But there's no n
On Tue, 2015-08-04 at 11:57 +0100, David Woodhouse wrote:
> On Tue, 2015-08-04 at 08:45 +0300, Matti Koskimies wrote:
> > I'm using only command line for both openconnect and network
> > -manager. So don't even have network-manager-openconnect installed.
> > I'm using self written systemd files to
On Tue, 2015-08-04 at 08:45 +0300, Matti Koskimies wrote:
> I'm using only command line for both openconnect and network-manager.
> So don't even have network-manager-openconnect installed. I'm using
> self written systemd files to connect and disconnect the VPN. The
> command I use for starting is
On Mon, 2015-08-03 at 09:36 -0400, Mike Miller wrote:
> On Mon, Aug 03, 2015 at 10:42:25 +0300, Matti Koskimies wrote:
> > Versions:
> > network-manager 1.0.4-1
> > openconnect: 7.06-2
> >
> > I did a little research and found out that the routing table was
> > different with different NM versions
On Mon, Aug 03, 2015 at 10:42:25 +0300, Matti Koskimies wrote:
> Versions:
> network-manager 1.0.4-1
> openconnect: 7.06-2
>
> I did a little research and found out that the routing table was
> different with different NM versions installed after starting
> openconnect. So I found a workaround:
>
On Sat, 2015-08-01 at 11:52 -0400, Mike Miller wrote:
> Control: tags -1 + moreinfo
>
> On Fri, Jul 31, 2015 at 16:59:00 +0300, Matti Koskimies wrote:
> > Debian sid updated network-manager from 1.0.2 to 1.0.4 and after
> > that
> > openconnect didn't work. I downgraded network-manager to 1.0.2 a
Control: tags -1 + moreinfo
On Fri, Jul 31, 2015 at 16:59:00 +0300, Matti Koskimies wrote:
> Debian sid updated network-manager from 1.0.2 to 1.0.4 and after that
> openconnect didn't work. I downgraded network-manager to 1.0.2 and openconnect
> works again.
Works for me. Can you define "didn't w
Package: openconnect
Version: 7.06-2
Severity: important
Dear Maintainer,
Debian sid updated network-manager from 1.0.2 to 1.0.4 and after that
openconnect didn't work. I downgraded network-manager to 1.0.2 and openconnect
works again.
-- System Information:
Debian Release: stretch/sid
APT
22 matches
Mail list logo
