From: Nigel Metheringham <Nigel.Metheringham@dev.InTechnology.co.uk>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: NAT and MTU issues
Date: Mon, 22 Sep 2003 16:46:59 +0100 [thread overview]
Message-ID: <1064245619.6070.94.camel@angua.localnet> (raw)
In-Reply-To: <Pine.LNX.4.58.0309221739330.9794@tux.rsn.bth.se>
On Mon, 2003-09-22 at 16:41, Martin Josefsson wrote:
> On Mon, 22 Sep 2003, Nigel Metheringham wrote:
>
> > Took a closer look.
> > If I put that mangle rule in then:-
> > * I see no ICMP packets on the wire between the originating box
> > and the linux g/w (tested in 2 places to make sure I don't have
> > any packet sniffing/netfilter interactions). Previously I saw
> > ICMP need frag packets as quoted above
> > * those icmp_reply log messages appear to fire on each and every
> > packet
> >
> > icmp_reply: outer SRC -> 192.168.50.119
> > icmp_reply: inner DST -> 192.168.50.119 1500
>
> Uhm, let me see if I got this right...
>
> If you add that mangle rule you don't see any icmp packets on the wire but
> you see the icmp_reply messages?
yup.
With no mangle rule I get broken ICMP frag-needed messages on the wire
and your debug messages do not trigger.
With the mangle rule I see no ICMP on the wire but the debug messages
trigger frequently (ie probably once per packet).
I'm confused too!
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham@InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
next prev parent reply other threads:[~2003-09-22 15:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-19 15:28 NAT and MTU issues Nigel Metheringham
2003-09-20 9:15 ` n00b question..... How to get details on active connections Paul Gibson
2003-09-20 16:09 ` Nox
2003-09-20 19:04 ` NAT and MTU issues Martin Josefsson
2003-09-22 9:53 ` Nigel Metheringham
2003-09-22 12:00 ` Martin Josefsson
2003-09-22 14:52 ` Nigel Metheringham
2003-09-22 15:03 ` Martin Josefsson
2003-09-22 15:08 ` Nigel Metheringham
2003-09-22 15:41 ` Martin Josefsson
2003-09-22 15:46 ` Nigel Metheringham [this message]
2003-09-22 17:06 ` Martin Josefsson
2003-09-23 12:03 ` Nigel Metheringham
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=1064245619.6070.94.camel@angua.localnet \
--to=nigel.metheringham@dev.intechnology.co.uk \
--cc=gandalf@wlug.westbo.se \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox