Netdev List
 help / color / mirror / Atom feed
From: leroy christophe <christophe.leroy@c-s.fr>
To: linux-net@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Issue with NFS over NAT since kernel 3.8.x
Date: Sat, 05 Oct 2013 11:32:46 +0200	[thread overview]
Message-ID: <524FDCBE.9070407@c-s.fr> (raw)

I have a system with a panel PC running RedHat 7.3, mounting NFS from a 
RedHat 9 NFS Server.

Inbetween, I have a router which is running standard Kernel 3.8.13 and 
provides NAT (Masquerade) to the PC.

Reading the directory and a first file from the PC works well. But when 
trying to read a second file, the router stops forwarding the packets 
from the server back to the masqueraded PC.

It was working well with Kernel 3.7.10
It still fails with Kernel 3.10

Is there any change between 3.7 and 3.8 which could explain it ? How can 
I investigate this problem ?

Christophe

             reply	other threads:[~2013-10-05 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05  9:32 leroy christophe [this message]
2013-10-05 11:32 ` Issue with NFS over NAT since kernel 3.8.x Richard Weinberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=524FDCBE.9070407@c-s.fr \
    --to=christophe.leroy@c-s.fr \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox