[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Yura Pakhuchiy, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507/comments/32 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in linux package in Ubuntu: Invalid Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
First, let me say I'm not an Ubuntu developer. Second, is this still a problem for you? On a system running Precise, this seems to work for me: Linux yak 3.2.0-107-generic #148-Ubuntu SMP Mon Jul 18 20:22:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. >From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. >From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. >From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. >From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors On a system running Trusty, it also seems to work: Linux tuna 3.13.0-93-generic #140-Ubuntu SMP Mon Jul 18 21:21:05 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=1500 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=800 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=600 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=1500 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms On Xenial, it also seems to work: Linux grape 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=1500 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=800 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=600 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. ping: local error: Message too long, mtu=1500 --- 10.1.1.2 ping statistics --- 1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in linux package in Ubuntu: Incomplete Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush ca
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Hi Richard, I do not use Precise anymore, so I do not know whether this bug still present. But this problem was present only in 3.2 kernel. MTU always worked fine with 3.5 kernel, Pricese and Trusty. Your logs indicate that it was probably fixed in 3.2 kernel as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in linux package in Ubuntu: Incomplete Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to the default precise kernel 3.2? 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.2 Archi
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
I meant: MTU always worked fine with 3.5 kernel, Trusty and Xenial.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Oh, really? I think appreciate tag would be developer-emulating-work. Anyone can check that problem with ubuntu kernel 3.2 on every system, independently of hw configuration and bios version. More over, problem is fixed upstream. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to the default precise kernel 3.2? 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu17.2 Architecture: i386 ArecordDevices:
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
** Tags added: refused-troubleshooting
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Also Joseph Salisbury (jsalisbury) already marked this change as
Triaged. I reverted this to Verified by accident before.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
I'm pretty sure this problem is not depends on hardware. I tried not only on mine laptop, but on several servers with different hardware configurations. You can run attached script and will see that it happens on your system too (if you are running ubuntu kernel 3.2). ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in “linux” package in Ubuntu: Confirmed Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to the default precise kernel 3.2? 1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html --- AlsaVersion: Advanced Linux Sound Architec
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
I meant: this bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1177507
Title:
per route mtu settings are broken in linux kernel 3.2
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
Hello,
Looks like setting per route mtu (as described in [1]) is broken in linux
kernel 3.2 (default kernel from ubuntu 12.04).
I made script to illustrate this:
root@germany7:~# cat route-mtu
#!/bin/bash
uname -a
ip tuntap add dev test mode tun
ifconfig test 10.1.1.1/16 mtu 1500
echo =
echo No per route mtu entry
ping -c1 -Mdo -s2000 10.1.1.2
echo =
echo Per route MTU is set to 800
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800
echo =
echo Per route MTU is set to 600
ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600
echo =
echo No per route mtu entry
ip route flush cache
ping -c1 -Mdo -s2000 10.1.1.2
ip tuntap del dev test mode tun
With kernel 3.2 I get following output:
Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC
2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
After once set to 800, MTU is always 800, even if you add different
route and clean routing cache.
It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything
works like expected:
root@germany7:~# ./route-mtu
Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05
UTC 2013 i686 i686 i386 GNU/Linux
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 800
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
Per route MTU is set to 600
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
=
No per route mtu entry
PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data.
From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500)
--- 10.1.1.2 ping statistics ---
0 packets transmitted, 0 received, +1 errors
I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise),
results are same to 3.5.
Is there any chance to get fixes from 3.5/3.8 backported to the
default precise kernel 3.2?
1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COM
[Kernel-packages] [Bug 1177507] Re: per route mtu settings are broken in linux kernel 3.2
Yura Pakhuchiy, as per http://us.acer.com/ac/en/US/content/drivers an update is available for your BIOS (1.36). If you update to this, does it change anything? If not, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date Thank you for your understanding. ** Tags added: bios-outdated-v1.36 ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1177507 Title: per route mtu settings are broken in linux kernel 3.2 Status in “linux” package in Ubuntu: Incomplete Bug description: Hello, Looks like setting per route mtu (as described in [1]) is broken in linux kernel 3.2 (default kernel from ubuntu 12.04). I made script to illustrate this: root@germany7:~# cat route-mtu #!/bin/bash uname -a ip tuntap add dev test mode tun ifconfig test 10.1.1.1/16 mtu 1500 echo = echo No per route mtu entry ping -c1 -Mdo -s2000 10.1.1.2 echo = echo Per route MTU is set to 800 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 800 echo = echo Per route MTU is set to 600 ip route add 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip route del 10.1.1.2 dev test proto static src 10.1.1.1 mtu lock 600 echo = echo No per route mtu entry ip route flush cache ping -c1 -Mdo -s2000 10.1.1.2 ip tuntap del dev test mode tun With kernel 3.2 I get following output: Linux germany7 3.2.0-41-generic-pae #66-Ubuntu SMP Thu Apr 25 03:50:20 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors After once set to 800, MTU is always 800, even if you add different route and clean routing cache. It looks like that problem is fixed in ubuntu kernel 3.5. With it, everything works like expected: root@germany7:~# ./route-mtu Linux germany7 3.5.0-28-generic #48~precise1-Ubuntu SMP Wed Apr 24 21:43:05 UTC 2013 i686 i686 i386 GNU/Linux = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 800 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 800) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = Per route MTU is set to 600 PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 600) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors = No per route mtu entry PING 10.1.1.2 (10.1.1.2) 2000(2028) bytes of data. From 10.1.1.1 icmp_seq=1 Frag needed and DF set (mtu = 1500) --- 10.1.1.2 ping statistics --- 0 packets transmitted, 0 received, +1 errors I also tested with kernels 2.6.35 (in lucid) and 3.8 (in precise), results are same to 3.5. Is there any chance to get fixes from 3.5/3.8 backported to th
