All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Meyer Raffaele <raffaele.meyer@fhnw.ch>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: Possible segfault in nft utility
Date: Fri, 8 Apr 2016 13:51:44 +0200	[thread overview]
Message-ID: <20160408115144.GA7003@salvia> (raw)
In-Reply-To: <60982738E3650D41B91037A907B50C6A31797345@MXAMU25.adm.ds.fhnw.ch>

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.

      reply	other threads:[~2016-04-08 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 11:10 Possible segfault in nft utility Meyer Raffaele
2016-04-08 11:51 ` Pablo Neira Ayuso [this message]

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=20160408115144.GA7003@salvia \
    --to=pablo@netfilter.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=raffaele.meyer@fhnw.ch \
    /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.