From: Meyer Raffaele <raffaele.meyer@fhnw.ch>
To: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Possible segfault in nft utility
Date: Fri, 8 Apr 2016 11:10:47 +0000 [thread overview]
Message-ID: <60982738E3650D41B91037A907B50C6A31797345@MXAMU25.adm.ds.fhnw.ch> (raw)
Dear Sir or Madam
I am currently using nftables under Ubuntu 15.10. Kernel version is 4.2.0-16-generic and nftables version is nftables v0.4 (Support Edward Snowden).
I was looking for a way to match packets based on the mss optional value in the tcp header. While using the describe command, I encountered a segfault:
user@machine:~$ nft describe tcp reserved
Segmentation fault (core dumped)
It is not really a bad bug since the reserved keyword is probably not used anyway but I thought to report it. At the same time I wanted to ask if it is possible to match packets on wether they have a MaximumSegmentSize set in the TCP header or not. I want this since most of the TCP-Syn flood tools seem to not set this option and most legitimate TCP stacks do set it.
Greetings
Raffaele Meyer
next reply other threads:[~2016-04-08 11:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 11:10 Meyer Raffaele [this message]
2016-04-08 11:51 ` Possible segfault in nft utility Pablo Neira Ayuso
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=60982738E3650D41B91037A907B50C6A31797345@MXAMU25.adm.ds.fhnw.ch \
--to=raffaele.meyer@fhnw.ch \
--cc=netfilter-devel@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 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.