linux-3.0.x regression with ipv4 routes having mtu

[Timo Teräs <timo.teras@xxxxxx>]

Hi,

I'm testing linux-3.0.10 and it appears to have a mtu bug with ipv4.
There was recent funniness in ipv6 side as well [1,2], but this seems
quite different.

Basically, doing something like (ipA being the IPv4 host):
 1. do a tcp session to ipA (telnet to open ipv4 port, chat, close)
 2. "ip route get ipA" to see the route cache entry
 3. "ip route add ipA via (whatever was the router) mtu 1400"
 4. "ip route flush cache"
 5. "ip route get ipA" and you still get the old same info as in step 2:
    the mtu was not updated
    (btw. how long the tcp info from step 1 gets cached? is it tunable?)

So something is does not get updated here. This used to work though.
The current production boxes where I know this work is 2.6.38.8.

Sounds like the TCP info is used if it exists. But it never gets updated
after it's gone, and the new MTU is not being updated.

- Timo

[1] http://www.spinics.net/lists/netdev/msg174468.html
[2] http://marc.info/?l=linux-netdev&m=131529445904858
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html