Your message dated Wed, 20 Jan 2016 15:54:57 +0000 with message-id <e1alv61-0006uy...@franck.debian.org> and subject line Bug#809195: fixed in network-manager 1.0.10-2 has caused the Debian Bug report #809195, regarding network-manager: NM does not honor "push route" any more 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 ow...@bugs.debian.org immediately.) -- 809195: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809195 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: network-manager Version: 1.0.6-1 Severity: normal Dear Maintainer, I have just upgraded network-manager from 1.0.6 to 1.0.10 just to determine that my OpenVPN connection stopped working. Downgrading to 1.0.6 fixes the connection again. In my configuration, the central OpenVPN server pushes some route to the client with the push "route 192.168.x.x 255.255.x.x" directive. Everything has been set up properly so whenever I make a ip route on my nm-1.0.6 client I see the appropriate route. However, this has changed with 1.0.10: The appropriate route is no longer listed when doing a call to "ip route". If this behaviour change is intended, I could not find documentation on how to manually revert to the previous behaviour. If this change was not done by intention, it is a regression we should trace and fix. I am filing this bug report with network-manager (not network-manager-openvpn) because downgrading network-manager-openvpn alone did not have an effect. However, downgrading network-manager (without downgrading network-manager-openvpn) already had the desired effect. My current (working) package combination is: hi network-manager 1.0.6-1 ii network-manager-gnome 1.0.10-1 hi network-manager-openvpn 1.0.6-3 Best regards, Thomas -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'oldoldstable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser 3.113+nmu3 ii dbus 1.10.6-1 ii init-system-helpers 1.24 ii isc-dhcp-client 4.3.3-5 ii libbluetooth3 5.36-1 ii libc6 2.21-6 ii libdbus-1-3 1.10.6-1 ii libdbus-glib-1-2 0.102-1 ii libglib2.0-0 2.46.2-3 ii libgnutls-deb0-28 3.3.19-1 ii libgudev-1.0-0 230-2 ii libmm-glib0 1.4.12-1 ii libndp0 1.4-2 ii libnewt0.52 0.52.18-1+b1 ii libnl-3-200 3.2.26-1 ii libnl-genl-3-200 3.2.26-1 ii libnl-route-3-200 3.2.26-1 ii libnm0 1.0.10-1 ii libpam-systemd 228-2+b1 ii libpolkit-agent-1-0 0.105-14 ii libpolkit-gobject-1-0 0.105-14 ii libreadline6 6.3-8+b4 ii libsoup2.4-1 2.52.1-1 ii libsystemd0 228-2+b1 ii libteamdctl0 1.18-1 ii libuuid1 2.27.1-1 ii lsb-base 9.20150917 ii policykit-1 0.105-14 ii udev 228-2+b1 ii wpasupplicant 2.3-2.3 Versions of packages network-manager recommends: ii crda 3.13-1+b1 ii dnsmasq-base 2.75-1 ii iptables 1.4.21-2+b1 ii iputils-arping 3:20121221-5+b2 ii modemmanager 1.4.12-1 ii ppp 2.4.7-1+1 Versions of packages network-manager suggests: ii avahi-autoipd 0.6.32~rc+dfsg-1 pn libteam-utils <none> -- no debconf information
--- End Message ---
--- Begin Message ---Source: network-manager Source-Version: 1.0.10-2 We believe that the bug you reported is fixed in the latest version of network-manager, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 809...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl <bi...@debian.org> (supplier of updated network-manager package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Wed, 20 Jan 2016 16:16:13 +0100 Source: network-manager Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev network-manager-dbg gir1.2-networkmanager-1.0 Architecture: source Version: 1.0.10-2 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team <pkg-utopia-maintain...@lists.alioth.debian.org> Changed-By: Michael Biebl <bi...@debian.org> Description: gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager libnm-dev - GObject-based client library for NetworkManager (development file libnm-glib-dev - network management framework (GLib interface) libnm-glib-vpn-dev - network management framework (GLib interface) libnm-glib-vpn1 - network management framework (GLib VPN shared library) libnm-glib4 - network management framework (GLib shared library) libnm-util-dev - network management framework (development files) libnm-util2 - network management framework (shared library) libnm0 - GObject-based client library for NetworkManager network-manager - network management framework (daemon and userspace tools) network-manager-dbg - network management framework (debugging symbols) network-manager-dev - network management framework (development files) Closes: 783525 809195 Changes: network-manager (1.0.10-2) unstable; urgency=medium . * Fix failure to configure routes due to wrong device-route for IPv4 peer-addresses. Patch cherry-picked from upstream Git. (Closes: #809195) * Switch from user-mode PPPoE client back to kernel-mode PPPoE. We switched to rp-pppoe some time ago to workaround a bug in detecting disconnects which has seen been fixed in the kernel and could be worked around fairly simply with the right configuration. In addition, the kernel mode PPPoE implementation is faster and provides more features. (Closes: #783525) Checksums-Sha1: da5dc79ed9c7255b38768b4d41e79dc711f35fac 3548 network-manager_1.0.10-2.dsc 4f387a7bbd26bdad4aef91e2d0f04f2a38de0906 48096 network-manager_1.0.10-2.debian.tar.xz Checksums-Sha256: 03e3959e8448431574a623a9b8744fcf16de2bec49195995d14b4e04b021142c 3548 network-manager_1.0.10-2.dsc 2a8c8989493891cd4e3ead2578a3a4a3f513bb45827fdf5c5fa4eb0fd4cb5301 48096 network-manager_1.0.10-2.debian.tar.xz Files: 5e23ceb9091eeeb4893c49487b89a750 3548 net optional network-manager_1.0.10-2.dsc 6499787b80268fb4444f496f3effa413 48096 net optional network-manager_1.0.10-2.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWn6bnAAoJEGrh3w1gjyLcoewP/RxyGNFatLcSQ08KZVhY97pp 6s9oGtA7fF0E5b9uETde5Z5uCU5LWTBwZ+NieC29FuWN8K7ZNkXrsb1qGuVlDWv/ TpG1pFWfbGgfUVU3h12BMuSRzqxwuZxcVnD4QKBgiAImkmXJjmpFEbD/kIWgi8pr IeQk4UupVPjH8rdyq40hFXT0107+qunOWzusj5N0k0x2mAHD6qILNgrCMqeYdINK a/HbriqBKLQCkIXkBAbXpioeZQNOXQsOnh0M0/aLBcpXjx7/3eYO/O5du5UZoVto vdkrE69pSBRY0r6m2jpgP9MkuAgQUfEqlFUbvLYx0ga9y2snD3K7/ewoL3eVUsB+ AmLf03rF6wfk6fScKsxXqFeKrq8BOPfJNEQRcFa4WPEYFuuxCrcWp+cRUEg/lspg Gp0F4np9CxxeSCeYWTNvKuBTTY66Tbo74RK+TwE7EPNPUAft5T7q8dfzriTvCV3B srAF7/lzD+rYJwXyyM4yp148xzTrf3hp4RuiX3rvF5RlQjH1cxQ46Cwf3LxL8ZgY aP9MTN7xvWUGHqNNkyJxHMGVVp41P8WL+euD2hGG2nyfCMoruqmDzsiLnxxUrPhE UkxZTjt65xLfD8iLuWrqheDukxy/17Rz6fntJhn/+lzTPnp2uuNQHXc46U7kDsEZ blAQbpvg44j30U21tHVc =+mqt -----END PGP SIGNATURE-----
--- End Message ---
