* Possible segfault in nft utility
@ 2016-04-08 11:10 Meyer Raffaele
2016-04-08 11:51 ` Pablo Neira Ayuso
0 siblings, 1 reply; 2+ messages in thread
From: Meyer Raffaele @ 2016-04-08 11:10 UTC (permalink / raw)
To: netfilter-devel@vger.kernel.org
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Possible segfault in nft utility
2016-04-08 11:10 Possible segfault in nft utility Meyer Raffaele
@ 2016-04-08 11:51 ` Pablo Neira Ayuso
0 siblings, 0 replies; 2+ messages in thread
From: Pablo Neira Ayuso @ 2016-04-08 11:51 UTC (permalink / raw)
To: Meyer Raffaele; +Cc: netfilter-devel@vger.kernel.org
On Fri, Apr 08, 2016 at 11:10:47AM +0000, Meyer Raffaele wrote:
> 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)
This is already fixed in 0.5 as weel as in the upcoming 0.6 release.
# nft describe tcp reserved
payload expression, datatype integer (integer), 4 bits
> 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.
Several people already asked for TCP options matching already, this is
coming soon.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2016-04-08 11:51 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-04-08 11:10 Possible segfault in nft utility Meyer Raffaele
2016-04-08 11:51 ` Pablo Neira Ayuso
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).