Hi David, Did you update the MTU argument on Click's IPFragmenter element? And do you use an IPOutputCombo element? That also has an MTU argument. Check for CheckLength elements as well.
Eddie David Biot wrote: > Hello, > > I am having some problems with path MTU discovery with a click router. > > In this router I fragment and defragment IP-packets. I have a IPFragmenter > element that issues a ICMPError-message when a packet arrives that is too > big and has the don't fragment bit up. This ICMP-message is configured as > ICMPError(WAN1, 3, 4, PMTU 1400, MTU 1400), but still when I try running > iperf to test the router, I get 536 as the MTU and not the 1400 I > configured. Is there something else I need to do to ensure path MTU > discovery works? > > With regards, > David Biot > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.476 / Virus Database: 269.9.10/873 - Release Date: 26/06/2007 > 23:54 > > _______________________________________________ > click mailing list > [email protected] > https://amsterdam.lcs.mit.edu/mailman/listinfo/click _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
