From: Abraham van der Merwe <abz@frogfoot.net>
To: Ramin Dousti <ramin@cannon.eng.us.uu.net>
Cc: Netfilter Discussions <netfilter@lists.netfilter.org>
Subject: Re: clearing dont-fragment bit
Date: Thu, 9 Oct 2003 16:52:48 +0200 [thread overview]
Message-ID: <20031009145248.GA26549@oasis.frogfoot.net> (raw)
In-Reply-To: <20031009144334.GB14078@cannon.eng.us.uu.net>
Hi Ramin >@2003.10.09_16:43:34_+0200
> > > > Are there any iptables extensions out there that allow you to clear the DF
> > > > (Dont Fragment) bit in ip headers?
> > > AFAIK no. Why would you want to do that?
> > > I think I might write a module that would do that.
> >
> > I need it for tunnels. In a perfect world that wouldn't be necessary at all,
> > but reality is that there's many brain dead admins that filter icmp, so if
> > you build a tunnel over the big bad internet, you're screwed.
> >
> > You can use the TCPMSS target which solves it for tcp, but you still have
> > the same problem with udp packets, so imho the only way to solve this
> > properly is to fragment packets even if DF=1.
>
> The applications that set the DF bit, do so for a reason not just for the
> fun. Sometimes (well, actually most of the time) it's for the performance
> reasons in which case turning it off and having a poor performance is
> preferable than it not working at all. On the other hand, the DF bit would be
> set by the application probes to figure the PMTU. Setting that off on the
> firewall would harm the purpose.
Ideally one would want to leave DF untouched unless a packet with DF=1 is
resent in which case you clear it - that way you solve PMTU probes, but I
suspect this would be overly complicated / resource intensive.
Even better would be if there was a tunnelling protocol that would just take
packets on side A (incl ip headers, galore), chop it up, and reassemble it
on the other side. Unfortunately there is no such thing :P
> Can you come up with a list of the non-TCP-based application protocols that
> would use the PMTU (DF bit)?
Basically any UDP application that sends packets bigger than the maximum
allowed mtu. I would assume TFTP, SNMP, etc. would all get into trouble. I
know that some protocols such as DNS try to stay below 512 bytes payload,
but there is probably a gazillion protocols out there that don't.
--
Regards
Abraham
The meek shall inherit the earth; the rest of us will go to the stars.
___________________________________________________
Abraham vd Merwe - Frogfoot Networks CC
9 Kinnaird Court, 33 Main Street, Newlands, 7700
Phone: +27 21 686 1665 Cell: +27 82 565 4451
Http: http://www.frogfoot.net/ Email: abz@frogfoot.net
next prev parent reply other threads:[~2003-10-09 14:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-09 13:43 clearing dont-fragment bit Abraham van der Merwe
2003-10-09 14:03 ` Maciej Soltysiak
2003-10-09 14:08 ` Abraham van der Merwe
2003-10-09 14:43 ` Ramin Dousti
2003-10-09 14:52 ` Abraham van der Merwe [this message]
2003-10-09 15:49 ` Ramin Dousti
2003-10-09 16:13 ` Abraham van der Merwe
2003-10-09 19:44 ` Ramin Dousti
2003-10-09 16:23 ` Ralf Spenneberg
2003-10-09 16:50 ` Abraham van der Merwe
2003-10-09 17:12 ` Ralf Spenneberg
2003-10-09 18:11 ` Abraham van der Merwe
2003-10-10 5:13 ` Ralf Spenneberg
2003-10-10 8:17 ` Abraham van der Merwe
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=20031009145248.GA26549@oasis.frogfoot.net \
--to=abz@frogfoot.net \
--cc=netfilter@lists.netfilter.org \
--cc=ramin@cannon.eng.us.uu.net \
/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