touch-packages team mailing list archive

[Launchpad Bug Tracker <1498474@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package network-manager - 1.0.4-0ubuntu5

---------------
network-manager (1.0.4-0ubuntu5) wily; urgency=medium

  * debian/patches/git_set_vpn_mtu_9736327b.patch: set the MTU for the VPN
    interface. (LP: #1498474)
  * debian/patches/lp1446689_git_use_kernel_pppoe_6fdfb031.patch: use the
    kernel-provided pppoe interfaces rather than requiring the use of rp-pppoe
    to use PPPoE; we switched to rp-pppoe some time ago to workaround a bug in
    detecting disconnects which has seen been fixed and could be worked around
    fairly simply with the right configuration. (LP: #1446689)
  * debian/rules: don't pass --with-pppoe to configure; the option is removed
    by the above patch.

 -- Mathieu Trudel-Lapierre <mathieu-tl@xxxxxxxxxx>  Wed, 14 Oct 2015
12:33:53 -0400

** Changed in: network-manager (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1498474

Title:
  Incorrect MTU on VPN connect

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  On update to wily, vpnc vpn connects, but MTU is incorrectly set to
  1500, instead of default value which is 1412.  This results in
  connectivity issues (packet loss).

  Gnomezilla bug report:
  https://bugzilla.gnome.org/show_bug.cgi?id=754781

  I have attached the included patch from above for convenience, and
  tested that this indeed resolves the issue for me.

  It might be worth mentioning that I had to disable the built in tests
  (--enable-tests=no), or pakage generation with "debuild -us -uc -b"
  fails on 2 of the tests relating to ipv6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1498474/+subscriptions