nullack wrote: > This is most certainly still a defect. On Jaunty on revision: > > null...@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. > > Yes, can you check whether the https://edge.launchpad.net/~network-manager/+archive PPA packages (0.7 final) or intrepid/jaunty fix this for you?
Thanks! -- NM 0.7 Fails To Set Custom MTU https://bugs.launchpad.net/bugs/258743 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
