Re: Linux NFS no-DF status

2003-02-21 Thread Srebrenko Sehic
On Fri, Feb 21, 2003 at 02:40:29PM -0500, Jason Dixon wrote:
 I don't want anyone's hair to stand on end, but I was just curious...
 with the clarification recently given by the Linux camp on the
 NFS/DF-bit issue, is there an effort currently under way to recognize
 and support their implementation for 3.3 -release?  Meaning, PF won't
 break it anymore?

AFAIK, this issue is fixed -current and will be in 3.3.

// haver




Re: Linux NFS no-DF status

2003-02-21 Thread Daniel Hartmeier
On Fri, Feb 21, 2003 at 08:59:58PM +0100, Srebrenko Sehic wrote:

 AFAIK, this issue is fixed -current and will be in 3.3.

Yes, the no-df option has been modified in -current so it applies
earlier and also covers fragments with DF (clearing the DF flag), so you
can make these NFS connections work by adding the no-df option to the
relevant scrub rules.

Daniel



Re: Linux NFS no-DF status

2003-02-21 Thread Jason Dixon
On Fri, 2003-02-21 at 15:04, Nathan Ryan Milford wrote:
 PF does not break Linux NFS.
 
 Using the scrub directive will probably detect and drop packets from Linux
 NFS as they decided to not follow standards.
 
 I'm not a pf developer, but I'd doubt they'd waste thier time on something
 that isn't thier fault.  I'd wait for Linux NFS to follow protocol.

I'm not suggesting it's PF's fault (hence the quotes around broken). 
If you've followed recent developments, you'd understand the reason
Linux NFS doesn't work through normalized PF (scrub) is that the PF
developers refused to respect the DF bit on fragmented Linux NFS traffic
without understanding WHY in the hell they wanted to do it that way.

Although the RFC's dictate otherwise, the Linux maintainers stand by the
notion that the RFC's are _not_LAW_, and are only there as a guideline. 
Now that this has come to light
(http://kerneltrap.org/node.php?id=579cid=2386pid=2382#2386), I expect
that Daniel plans on integrating this in due course.

Just curious when that may be.

-J.

 - Original Message -
 From: Jason Dixon [EMAIL PROTECTED]
 To: PF Mailing List [EMAIL PROTECTED]
 Sent: Friday, February 21, 2003 2:40 PM
 Subject: Linux NFS no-DF status
 
 
  I don't want anyone's hair to stand on end, but I was just curious...
  with the clarification recently given by the Linux camp on the
  NFS/DF-bit issue, is there an effort currently under way to recognize
  and support their implementation for 3.3 -release?  Meaning, PF won't
  break it anymore?
 
  I don't need it, I was just sitting around thinking about it and got
  curious.
 
  -J.
 
 
 
 
 




Re: Linux NFS no-DF status

2003-02-21 Thread Mike Frantzen
 I'm not suggesting it's PF's fault (hence the quotes around broken). 
 If you've followed recent developments, you'd understand the reason
 Linux NFS doesn't work through normalized PF (scrub) is that the PF
 developers refused to respect the DF bit on fragmented Linux NFS traffic
 without understanding WHY in the hell they wanted to do it that way.

It's not that we refused to respect it.  We respect it.  Hell, we even
admit it makes sense in some situations.  But it is open for ambiguous
interpretation and thus SCRUB must normalize it away.
 
.mike