MTU is reset to 1280 often

Bug #1512576 reported by nemith
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

My interfaces on some state changes seems to reset the MTU to 1280 after connecting to Wifi, new interface, or around every 10 minutes on VPN.

Seems to be an upstream bug with network-manager that wasn't fixed before release of 15.10

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=a92d8b0c678e17d1cc175c3aad50afb1443785d2
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=c44069c10a4a9c696910baf0dbbefc41528f6dbe
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e0fa48f224abcb73a1a129f10050f7cd942ee629

All seem to be related.

This is a major bug.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Nov 2 22:15:13 2015
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2015-10-31 (2 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IpRoute:
 default dev vpn0 proto static scope link metric 50
 default via 192.168.1.1 dev wlp4s0 proto static metric 600
 169.254.0.0/16 dev vpn0 scope link metric 1000
 172.26.96.0/20 dev vpn0 proto kernel scope link src 172.26.108.224 metric 50
 192.168.1.0/24 dev wlp4s0 proto kernel scope link src 192.168.1.246 metric 600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-11-02T00:33:31.364599
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
nemith (bennetb) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.