Linux Netfilter discussions
 help / color / mirror / Atom feed
From: bossk <bossk@tyntec.biz>
To: netfilter@vger.kernel.org
Subject: ICMP fragmentation needed packets lost
Date: Thu, 20 Mar 2008 18:13:35 +0100	[thread overview]
Message-ID: <200803201813.36278.bossk@tyntec.biz> (raw)

Hi,

I have the following setup

-------           ----------------                     -----------------            -------------           ----------------
| B   |--------| VPN-GW2 |=======|  VPN-GW1 | --------|   GW      |--------|       A        |
-------          -----------------                     ------------------           -------------           ---------------- 

The server GW is in the same net (10.0.1.0/28) as VPN-GW via interface bond0 and connected to the same network (10.0.3.0/24) as server A with interface bond2.
Server A can send packets to server B which can be reached through the VPN.

Now the tricky part if server A sends a packet with a size of 1460 Bytes the VPN-GW1 sends an ICMP fragmentation-needed packet to A which
is not passing the GW, if the FORWARD policy is set to DROP.

I have enabled the following rules
iptables -A FORWARD -i bond0 -o bond2 -j ACCEPT
iptables -A FORWARD -i bond2 -o bond0 -j ACCEPT

and specials rules 
iptables -A FORWARD -s 10.0.1.0/28 -d 10.0.3.0/24 -j ACCEPT
iptables -A FORWARD -s 10.0.3.0/24 -d 10.0.1.0/28 -j ACCEPT

If I set the FORWARD policy to ACCEPT then the ICMP fragmentation-needed packet is passing the GW. After I change the FORWARD policy to DROP
that packet is not passing the GW.

Has someone an idea why this happens?

Thanks,
bossk

             reply	other threads:[~2008-03-20 17:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 17:13 bossk [this message]
2008-03-31 21:07 ` ICMP fragmentation needed packets lost Martijn Lievaart

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=200803201813.36278.bossk@tyntec.biz \
    --to=bossk@tyntec.biz \
    --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