Your message dated Thu, 3 Mar 2016 17:00:31 -0800
with message-id <[email protected]>
and subject line fixed 709890 in network-manager-applet/0.9.8.2-1
has caused the Debian Bug report #709890,
regarding network-manager-openconnect: Static IPv6 VPN route needs a next-hop
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
709890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709890
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager-openconnect
Version: 0.9.8.0-1
Severity: minor

My university offers IPv6 over AnyConnect/OpenConnect, but currently does
not signal split tunneling only for their prefix. Since I usually have 
direct native IPv6 I often only want to route their prefix over the tunnel,
not the default route.

It almost works with the following configuration

[ipv6]
method=auto
route1=2001:4ca0::/32,ac:2701:0:0:5b01::,0
ignore-auto-dns=true
never-default=true

The problem is "ac:2701:0:0:5b01::", the next-hop above. The GUI forces me
to fill that field, even if it is technically unnecessary on point2point
links like the VPN tunnel. If I leave it empty, it gets filled with random
junk as seen above. Which then leads to

May 26 14:46:24 schleppi NetworkManager[14998]: <error> [1369572384.496049] 
[nm-system.c:689] nm_system_apply_ip6_config(): (vpn0): failed to set IPv6 
route: Object not found

and the route not being set.

The workaround is easy enough for me, since I always connect to the same
VPN concentrator I use an arbitrary high address from the VPN pool as
next-hop, which is directly-connected on vpn0. Not pretty though, since I
should be using the cluster address and might end up on one of six VPN
concentrators with different pools.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable'), (800, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager-openconnect depends on:
ii  adduser           3.113+nmu3
ii  libc6             2.17-3
ii  libdbus-1-3       1.6.10-1
ii  libdbus-glib-1-2  0.100.2-1
ii  libglib2.0-0      2.36.1-2build1
ii  libnm-glib-vpn1   0.9.8.0-5
ii  libnm-glib4       0.9.8.0-5
ii  libnm-util2       0.9.8.0-5
ii  network-manager   0.9.8.0-5
ii  openconnect       4.99-2

Versions of packages network-manager-openconnect recommends:
ii  network-manager-openconnect-gnome  0.9.8.0-1

network-manager-openconnect suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
fixed 709890 network-manager-applet/0.9.8.2-1
thanks

Closing dormant bug, I believe this was fixed in upstream 0.9.8.2.

-- 
mike

--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to