From: Jiri Olsa <jolsa@redhat.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netdev@vger.kernel.org
Subject: Re: no reassembly for outgoing packets on RAW socket
Date: Mon, 7 Jun 2010 16:55:58 +0200 [thread overview]
Message-ID: <20100607145558.GA1939@jolsa.lab.eng.brq.redhat.com> (raw)
In-Reply-To: <4C08EB85.3050900@trash.net>
On Fri, Jun 04, 2010 at 02:03:17PM +0200, Patrick McHardy wrote:
> Jiri Olsa wrote:
> > hi,
> >
> > I'd like to be able to sendout a single IP packet with MF flag set.
> >
> > When using RAW sockets the packet will get stuck in the
> > netfilter (NF_INET_LOCAL_OUT nf_defrag_ipv4 reassembly unit)
> > and wont ever make it out..
> >
> > I made a change which bypass the outgoing reassembly for
> > RAW sockets, but I'm not sure wether it's too invasive..
>
> That would break reassembly (and thus connection tracking) for cases
> where its really intended.
>
> > Is there any standard for RAW sockets behaviour?
> > Or another way around? :)
>
> You could use the NOTRACK target to bypass connection tracking.
ok,
I tried the NOTRACK target, but the packet is still going
throught reassembly, because the RAW filter has lower priority
then the connection track defragmentation..
I was able to get it bypassed by attached patch and following
command:
iptables -v -t raw -A OUTPUT -p icmp -j NOTRACK
again, not sure if this is too invasive ;)
If this is not the way, I'd appreciatte any hint.. my goal is
to put malformed packet on the wire (more frags bit set for a
non fragmented packet)
thanks for help,
jirka
---
diff --git a/include/linux/netfilter_ipv4.h b/include/linux/netfilter_ipv4.h
index 29c7727..d249b6a 100644
--- a/include/linux/netfilter_ipv4.h
+++ b/include/linux/netfilter_ipv4.h
@@ -53,8 +53,8 @@
enum nf_ip_hook_priorities {
NF_IP_PRI_FIRST = INT_MIN,
- NF_IP_PRI_CONNTRACK_DEFRAG = -400,
- NF_IP_PRI_RAW = -300,
+ NF_IP_PRI_RAW = -400,
+ NF_IP_PRI_CONNTRACK_DEFRAG = -300,
NF_IP_PRI_SELINUX_FIRST = -225,
NF_IP_PRI_CONNTRACK = -200,
NF_IP_PRI_MANGLE = -150,
diff --git a/net/ipv4/netfilter/nf_defrag_ipv4.c b/net/ipv4/netfilter/nf_defrag_ipv4.c
index cb763ae..cb865d1 100644
--- a/net/ipv4/netfilter/nf_defrag_ipv4.c
+++ b/net/ipv4/netfilter/nf_defrag_ipv4.c
@@ -74,6 +74,9 @@ static unsigned int ipv4_conntrack_defrag(unsigned int hooknum,
return NF_ACCEPT;
#endif
#endif
+ if (nf_ct_is_untracked(skb))
+ return NF_ACCEPT;
+
/* Gather fragments. */
if (ip_hdr(skb)->frag_off & htons(IP_MF | IP_OFFSET)) {
enum ip_defrag_users user = nf_ct_defrag_user(hooknum, skb);
next prev parent reply other threads:[~2010-06-07 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 11:27 no reassembly for outgoing packets on RAW socket Jiri Olsa
2010-06-04 12:03 ` Patrick McHardy
2010-06-07 14:55 ` Jiri Olsa [this message]
2010-06-09 14:16 ` Patrick McHardy
2010-06-09 15:15 ` Jan Engelhardt
2010-06-09 15:16 ` Patrick McHardy
2010-06-09 15:20 ` Jan Engelhardt
2010-06-10 6:57 ` Jiri Olsa
2010-06-10 6:56 ` Jiri Olsa
2010-06-10 9:14 ` Patrick McHardy
2010-06-10 9:53 ` Jiri Olsa
2010-06-10 10:04 ` Patrick McHardy
2010-06-11 8:16 ` Jiri Olsa
2010-06-11 9:53 ` Jan Engelhardt
2010-06-11 13:10 ` Jiri Olsa
2010-06-15 6:53 ` [PATCH] net: IP_NODEFRAG option for IPv4 socket Jiri Olsa
2010-06-15 7:13 ` Eric Dumazet
2010-06-15 9:18 ` Jiri Olsa
2010-06-15 9:49 ` Eric Dumazet
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=20100607145558.GA1939@jolsa.lab.eng.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=kaber@trash.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).