Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Arunsundar <arun.sundar@sawridgesystems.com>
To: netfilter@vger.kernel.org
Subject: Conntrack does not Re-Fragment, defragmented packet while forwarding
Date: Tue, 14 Jun 2016 18:39:57 +0530	[thread overview]
Message-ID: <57600225.8000906@sawridgesystems.com> (raw)

Hi All,

As per few online documents, conntrack will defragment the received 
packets in Prerouting and it again re-fragment before packet leaves the 
machine. But I observe that conntrack defragments and forward the same 
defragmented packet, re-fragment while forwarding is not happening. 
Details below

Requirement:
Receive the fragmented packets in ingress in interface0, mark the packet 
based on IP and port and the marked packet will be sent via a particular 
TC HTB class as it is received in the interface1. IP forward is enabled.

Procedure followed:
used below commands to mark the packet.
     iptables -t mangle -A PREROUTING -i em1 -d 192.xxx.xxx.xxx -p udp 
--dport xxxx -j MARK --set-mark 0x400
     iptables -t mangle -A PREROUTING -i em1 -d 192.xxx.xxx.xxx -p udp 
--dport xxxx -j CONNMARK --save-mark
     iptables -t mangle -A PREROUTING -i em1 -p udp -d 192.xxx.xxx.xxx 
--dport xxxx -j CONNMARK --restore-mark

These above commands work fine for my requirement. As per these 
commands, Contrack defragment the received packets and mark it correctly 
based on IP and port. But when the packet is forwarded to the next 
interface, the defragmented packet is forwarded as it is instead of 
sending the received packets.

Can some one let me know how to re-fragment the packets after 
defragmentation done by conntrack.

Other Info:
iptables v1.4.21
conntrack v1.4.1
Linux Kernel - 4.4.6


-- 
Regards,
Arunsundar.


                 reply	other threads:[~2016-06-14 13:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=57600225.8000906@sawridgesystems.com \
    --to=arun.sundar@sawridgesystems.com \
    --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