>> Hmm, so you say it was the 2.0.x NFS client that SYN flooded the NFS
>> server. Ok, thanks for the clarification.
>
>The 2.0 NFS client is UDP only. So it wasnt that.
`mount` uses _TCP_ (and mountd sits at an address at around 6xx here). So
a mount bug/loop may explain some kind of flood. Dan can be _right_ saying
"it was all me".
Anyway this doesn't seems a 2.0.x security issue but a mount/mountd
userspace problem if something. So I only suggest to upgrade `mount` as
first thing and the nfs server (rpc.mountd mainly) as second thing, and
also the kernel if 2.0.x still doesn't work stable for you.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/