This is most certainly still a defect. On Jaunty on revision:
nullack@PPP:~$ sudo apt-cache policy network-manager network-manager: Installed: 0.7~~svn20081018t105859-0ubuntu2 Candidate: 0.7~~svn20081018t105859-0ubuntu2 Version table: *** 0.7~~svn20081018t105859-0ubuntu2 0 500 http://archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status
My test steps are:
1. Change automatic default mtu field population to 1492 2. Confirm the custom mtu is set 3. Reboot system
The result is always that the MTU has not retained the user preference and has reverted back to an automatic MTU value.
This is most certainly still a defect. On Jaunty on revision:
nullack@PPP:~$ sudo apt-cache policy network-manager 8t105859- 0ubuntu2 8t105859- 0ubuntu2 8t105859- 0ubuntu2 0 archive. ubuntu. com jaunty/main Packages dpkg/status
network-manager:
Installed: 0.7~~svn2008101
Candidate: 0.7~~svn2008101
Version table:
*** 0.7~~svn2008101
500 http://
100 /var/lib/
My test steps are:
1. Change automatic default mtu field population to 1492
2. Confirm the custom mtu is set
3. Reboot system
The result is always that the MTU has not retained the user preference and has reverted back to an automatic MTU value.