From: Patrick McHardy <kaber@trash.net>
To: Nishit Shah <nishit@elitecore.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: problem with connection tracking with fragmentation needed icmp error
Date: Fri, 03 Nov 2006 11:19:52 +0100 [thread overview]
Message-ID: <454B17C8.1010904@trash.net> (raw)
In-Reply-To: <013a01c6fe4b$c5032dc0$4c01a8c0@elitecore26>
Nishit Shah wrote:
> Hi,
>
> I have a following setup
>
> machineA ------------------------------router --------------------------
> firewall ------------------------------------ machineB
> 172.16.16.2 172.16.16.1 9.9.9.1 9.9.9.2
> 192.168.1.1 192.168.1.2
>
>
> router has two interfaces, eth0 is connected to machineA with mtu of 1000,
> all other interfaces with mtu of 1500.
> if i ping from machineA to machineB with data size 1200 and DF bit set,
> packet will reach machineB, machineB will reply with DF bit set and data
> size 1200,
> upon receving this packet router sends icmp fragmentation needed and DF bit
> set message to machineB, when this packet comes to firewall conntrack marks
> that packet's state as INVALID. is it the valid case ??
I don't see how this can happen on current kernels that manually
associate locally generated ICMP errors with the original conntrack.
What kernel version are you running on the router?
next prev parent reply other threads:[~2006-11-03 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 6:54 problem with connection tracking with fragmentation needed icmp error Nishit Shah
2006-11-03 10:19 ` Patrick McHardy [this message]
2006-11-03 10:43 ` Nishit Shah
2006-11-03 10:44 ` Patrick McHardy
2006-11-04 5:42 ` Nishit Shah
2006-11-06 14:01 ` Patrick McHardy
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=454B17C8.1010904@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=nishit@elitecore.com \
/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.