Sorry you are using rip44d I guess and I don't so I can't comment as I have to read that script.
Is interface mtu 0 not discovery off? (as the path mtu was set to nopmtudisc)
Maybe setting the interface mtu to a fixed value will solve your problem.
Setting the ttl to a fixed value did switch path mtu discovery on originally but maybe this new behaviour with interface mtu 0 is causing the problem you have?
Bob
On 13-12-30 03:22 PM, Brian Rogers wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Mon, 2013-12-30 at 15:03 -0500, Bob Tenty wrote:
/sbin/ifconfig tunl0 44.135.85.151 txqueuelen 1000 up gives here a mtu of 1480 (and a mask of 255.0.0.0)
Have you done a full update of wheezy on your pi? I suspect it may have something to do with the libc update. I know Ubuntu and Mint's libc breaks apps, I hope pi isn't doing the same with Raspbian.
(and ttl inherit nopmtudisc) So I'm wondering how you get mtu 0 there.
mtu 0 is auto discover. This is forced in the updated wheezy. I don't know if it's the same with jessie or not.
Are you using an other command line to start your tunnel interface?
Nope. This is a new forced config with raspbian from what I've seen. You can still change MTU but you can't change ttl. If you haven't updated... DONT!