Hi Alexander, I am sending ping from hostA to hostB. on all NICs in test (including e1000) mtu is 1500.The only NIC that mtu being changed is igb.
You are right, according to tcpdump, client does not fragment ping packets, looks like gateway does. Thanks, Igor. On Wed, Jan 28, 2009 at 9:48 PM, Duyck, Alexander H <alexander.h.du...@intel.com> wrote: > Igor, > > Can you clear a few thigns up for me. > > First in your tests below is hostA the server or client? I would assume it > is the client but I just want to make certain. > > Second what is the mtu for the e1000 adapter? Based on the tcpdump for > Client you have listed for client in test2 I am not seeing any fragmentation > being done on the client in your example. > > Thanks, > > Alex > > Igor Smolyar wrote: >> Hi Alexander, >> >> fix indeed solve crash problem (in vanilla 2.6.28.2) - thank you very >> much. But now I have another problem. >> When mtu <= 1000 I can not receive packets bigger that 1000. With mtu >> 1050 and bigger, fragmentation is working correct. >> >> hostA ------(e1000)_gateway_(igb)----hostB >> 10.48.201.201 10.48.0.254 >> >> >> ------------------------------------------------------------- >> Sending one ping of size 1500 from host A to hostB is working when >> mtu on igb NIC is 1050 or bigger. >> Test1: >> Ping on client is OK, no packet loss. >> Tcpdump on server: >> 10.48.201.201 > 10.48.0.254: icmp: echo request (frag 63563:1...@0+) >> (ttl 63, len 1044) >> 10.48.201.201 > 10.48.0.254: icmp (frag 63563:4...@1024+) (ttl 63, len >> 476) >> 10.48.201.201 > 10.48.0.254: icmp (frag 63563:2...@1480) (ttl 63, len >> 48) >> 10.48.0.254 > 10.48.201.201: icmp: echo reply (frag 59125:1...@0+) >> (ttl 64, len 1500) >> 10.48.0.254 > 10.48.201.201: icmp (frag 59125:2...@1480) (ttl 64, len >> 48) >> >> On igb NIC: >> mtu 1050, rx_buffer_len=2048 >> rx_errors: 0 >> rx_length_errors: 0 >> rx_long_length_errors: 0 >> >> ------------------------------------------------------------- >> >> Test2 - received reply packet dropped by igb NIC. >> Sending one ping of size 1500 from host A to hostB is not working when >> mtu on igb NIC is 1000 or less. >> >> Client ping statistics: >> 1 packets transmitted, 0 received, 100% packet loss, time 0ms >> >> Tcpdump on client: >> IP (tos 0x0, ttl 64, id 65483, offset 0, flags [+], proto 1, length: >> 1500) 10.48.201.201 > 10.48.0.254: icmp 1480: echo req uest seq 0 >> IP (tos 0x0, ttl 64, id 65483, offset 1480, flags [none], proto 1, >> length: 48) 10.48.201.201 > 10.48.0.254: icmp >> IP (tos 0x0, ttl 63, id 27391, offset 1480, flags [none], proto 1, >> length: 48) 10.48.0.254 > 10.48.201.201: icmp >> >> Tcpdump on server: >> 10.48.201.201 > 10.48.0.254: icmp: echo request (frag 65483:8...@0+) >> (ttl 63, len 900) >> 10.48.201.201 > 10.48.0.254: icmp (frag 65483:6...@880+) (ttl 63, len >> 620) >> 10.48.201.201 > 10.48.0.254: icmp (frag 65483:2...@1480) (ttl 63, len >> 48) >> 10.48.0.254 > 10.48.201.201: icmp: echo reply (frag 27391:1...@0+) >> (ttl 64, len 1500) >> 10.48.0.254 > 10.48.201.201: icmp (frag 27391:2...@1480) (ttl 64, len >> 48) >> >> In igb NIC: >> mtu 900 rx_buffer_len=1024 >> rx_errors: 2 >> rx_length_errors: 2 >> rx_long_length_errors: 2 >> >> # ethregs -s 0000:09:00.0 | grep RCTL >> RCTL 04058022 >> SRRCTL(0) 02000000 >> SRRCTL(1) 80000400 >> SRRCTL(2) 80000400 >> SRRCTL(3) 80000400 >> >> >> Thanks for your help and fast response, >> Igor. > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel
