From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Weird NAT problem
Date: Sun, 02 Nov 2008 12:50:28 -0600 [thread overview]
Message-ID: <490DF674.5020705@riverviewtech.net> (raw)
In-Reply-To: <490D8A25.6020506@plouf.fr.eu.org>
On 11/2/2008 5:08 AM, Pascal Hambourg wrote:
> Or with the ICMP error not being generated at all, because of the MTU
> mismatch not occuring at an IP device. This is quite common with a DSL
> modem acting as transparent bridge : as it works only at the link layer,
> when it receives a PPPoE frame bigger than 1500 bytes from the ISP, it
> cannot either forward it on the ethernet link, fragment it or send an
> ICMP error.
Interesting point. I had not considered a layer 2 device having to do
some ""conversion and it not being able to. This just further
exasperates the problem.
> The ISP routers should be responsible for doing the fragmentation and
> sending ICMP errors. But unfortunately they don't always do it.
> Sometimes the ISP don't even know the customer uses PPPoE, for example
> when it uses a third-party DSL carrier which deals with the PPPoX stuff
> and delivers user sessions to the ISP in L2TP tunnels.
Do you ever wonder where the out sourcing will stop? It seems like
despite the best intentions of outsourcing, problems always seem to come up.
> Be aware that this workaround only works for TCP, not for other IP
> protocols such as UDP, ICMP (big pings), GRE, IPSec (AH, ESP), IPIP,
> 6in4...
Very good points. /Fortunately/ I've not run in to them yet but I can
see how it would certainly be possible.
Grant. . . .
next prev parent reply other threads:[~2008-11-02 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-01 22:07 Weird NAT problem Bernhard Rosenkraenzer
2008-11-01 22:48 ` Grant Taylor
2008-11-01 22:52 ` Grant Taylor
2008-11-01 23:52 ` Bernhard Rosenkraenzer
2008-11-02 0:51 ` Grant Taylor
2008-11-02 11:08 ` Pascal Hambourg
2008-11-02 18:50 ` Grant Taylor [this message]
2008-11-01 22:59 ` Bernhard Rosenkraenzer
2008-11-01 23:14 ` Grant Taylor
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=490DF674.5020705@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@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