Hi Harald,

Harald Welte wrote:

>On Fri, Dec 06, 2002 at 01:56:18AM +0100, Patrick McHardy wrote:
>  
>
>>Hi,
>>
>>Harald Welte wrote:
>>    
>>
>>I experienced the same problem since almost 6 months with nfs and netfilter,
>>nfs was veery slow, it wasn't even possible to listen to mp3s over nfs.
>>    
>>
>
>I have experienced the problem the last two days, which I was running a
>debian woody system with an 2.4.18-k7 kernel.  I've now compiled my own
>kernel again (2.4.20-final with lots of patch-o-matic stuff) and the
>problem is gone again [nothing but the kernel on the conntracking
>nfs-serve was changed].
>
The machine making troubles here only runs self-compiled kernels.
IIRC it started with 2.4.18, also lots of patch-o-matic stuff applied.
Since then i've tried a lot kernels, with- and without pom,
atm i'm running 2.4.19-rc4-ac1, attached is a list of applied pom-patches.
If you send me a list of your patches i can try if it helps here.
Also if you would like to have a look for yourself i could create an 
account for you ...

>I'm running lots of Conectiva and Redhat systems with 2.4.18+ kernels
>and don't have this particular conntrack problem on any machine.
>
Here is how tcpdump looks with nfs-server(+conntrack) mtu set to 1500:

0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16283:1480@4440+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16284:1480@2960+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16284:1480@4440+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16284:1480@5920+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 962: 192.168.0.1 > 192.168.0.23: 
(frag 16284:928@7400) (ttl 64, len 948)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 154: 192.168.0.23.359760184 > 
192.168.0.1.2049: 112 read [|nfs] (DF) (ttl 64, id 0, len 140)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1.2049 > 
192.168.0.23.359760184: reply ok 1472 read REG 100644 ids 0/0 [|nfs] 
(frag 16285:1480@0+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16284:1480@4440+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16285:1480@2960+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16285:1480@4440+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1514: 192.168.0.1 > 192.168.0.23: 
(frag 16285:1480@5920+) (ttl 64, len 1500)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 962: 192.168.0.1 > 192.168.0.23: 
(frag 16285:928@7400) (ttl 64, len 948)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18135, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18136, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18137, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18138, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18139, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18140, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18141, len 576)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 590: 192.168.0.23 > 192.168.0.1: 
icmp: ip reassembly time exceeded [tos 0xc0]  (ttl 64, id 18142, len 576)
...

with mtu 1486 tcpdump looks like this (no icmp reassemly time exceeded):
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1498: 192.168.0.1 > 192.168.0.23: 
(frag 16436:1464@1464+) (ttl 64, len 1484)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1498: 192.168.0.1 > 192.168.0.23: 
(frag 16436:1464@2928+) (ttl 64, len 1484)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1498: 192.168.0.1 > 192.168.0.23: 
(frag 16436:1464@4392+) (ttl 64, len 1484)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1498: 192.168.0.1 > 192.168.0.23: 
(frag 16436:1464@5856+) (ttl 64, len 1484)
0:e0:7d:74:ab:cd 0:e0:7d:74:ab:cc 0800 154: 192.168.0.23.2339471672 > 
192.168.0.1.2049: 112 read [|nfs] (DF) (ttl 64, id 0, len 140)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1042: 192.168.0.1 > 192.168.0.23: 
(frag 16436:1008@7320) (ttl 64, len 1028)
0:e0:7d:74:ab:cc 0:e0:7d:74:ab:cd 0800 1498: 192.168.0.1.2049 > 
192.168.0.23.2339471672: reply ok 1456 read REG 100644 ids 0/0 [|nfs] 
(frag 16437:1464@0+) (ttl 64, len 1484)
...

Bye,
Patrick