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 15:52:04 +0100 [thread overview]
Message-ID: <1064242324.6070.77.camel@angua.localnet> (raw)
In-Reply-To: <Pine.LNX.4.58.0309221358460.9262@tux.rsn.bth.se>
On Mon, 2003-09-22 at 13:00, Martin Josefsson wrote:
> Could you please apply the attached patch and reproduce it again?
> It's just a small patch that enables a little debugging for this.
Very odd - I am seeing ICMPs generated:-
# /usr/sbin/tcpdump -n -i eth0 icmp
tcpdump: listening on eth0
15:26:12.146557 192.168.50.119 > 172.16.28.33: icmp: 10.0.2.2
unreachable - need to frag (mtu 1450) [tos 0xc0]
but no extra chatter in dmesg despite ensuring dmesg -n is turned up.
Checking the module object file shows the extra log messages in there,
so its not me doing something completely silly.
Putting a
iptables -t mangle -A FORWARD -p tcp --syn -j TCPMSS \
--clamp-mss-to-pmtu
in appears to fix things for me.
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 14:52 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 [this message]
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
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=1064242324.6070.77.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