From: Nigel Metheringham <Nigel.Metheringham@dev.InTechnology.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: NAT, ICMP and MTU issues
Date: Mon, 22 Sep 2003 12:07:34 +0100 [thread overview]
Message-ID: <1064228854.6070.16.camel@angua.localnet> (raw)
In-Reply-To: <1064224183.6070.4.camel@angua.localnet>
On Mon, 2003-09-22 at 10:49, Nigel Metheringham wrote:
> On Fri, 2003-09-19 at 17:19, Cedric Blancher wrote:
> > Just a 0.02e quick thought...
> > You're facing a situation a bit like routing LANs through a PPPoE link.
> > Solution is to clamp TCPMSS down to correct value when routing them.
>
> Interesting idea. I'm not sure these packets go through the FORWARD
> table - the rules I have in would not allow them to. However it gives
> me something to try playing with - variations using another table
> probably.
OK, I was talking utter rubbish...
The connection does indeed go through the FORWARD table and there is
indeed a set of rules to allow it to do so, written by myself, so my
mind has finally gone :-/
Putting a mangle table rule in to clamp MSS does appear to have fixed
the problem - just need to redo the whole test from scratch to ensure I
haven't something else in the chain thats affecting it.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham@InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
prev parent reply other threads:[~2003-09-22 11:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 15:41 NAT, ICMP and MTU issues Nigel Metheringham
2003-09-19 16:19 ` Cedric Blancher
2003-09-22 9:49 ` Nigel Metheringham
2003-09-22 11:07 ` Nigel Metheringham [this message]
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=1064228854.6070.16.camel@angua.localnet \
--to=nigel.metheringham@dev.intechnology.co.uk \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.