mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/2] nft: Upgrade
Date: Wed,  4 Apr 2018 14:56:51 +0200	[thread overview]
Message-ID: <20180404125653.17631-1-ada@thorsis.com> (raw)

This small series has upgrades for nftables and libnftnl. This was
necessary here, because nft v0.6 could not import rulesets dumped with
`nft list ruleset > myruleset` again with `nft -f myruleset`. With nft
v0.8.3 I can successfully import those packet filter rules.

Tested with OSELAS.Toolchain-2014.12.3/arm-v5te-linux-gnueabi and
ptxdist 2017.09.0 on an at91sam9g20 based board.

Greets
Alex

Alexander Dahl (2):
  libnftnl: Upgrade from 1.0.6 to 1.0.9
  nftables: Upgrade from v0.6 to v0.8.3

 ...on-t-enable-xtables-when-without-xtables-.patch | 32 ++++++++++++++++++++++
 patches/nftables-0.8.3/autogen.sh                  |  1 +
 patches/nftables-0.8.3/series                      |  4 +++
 rules/libnftnl.in                                  |  6 ----
 rules/libnftnl.make                                |  5 ++--
 rules/nftables.make                                | 17 +++++-------
 6 files changed, 46 insertions(+), 19 deletions(-)
 create mode 100644 patches/nftables-0.8.3/0001-configure-don-t-enable-xtables-when-without-xtables-.patch
 create mode 120000 patches/nftables-0.8.3/autogen.sh
 create mode 100644 patches/nftables-0.8.3/series

-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2018-04-04 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 12:56 Alexander Dahl [this message]
2018-04-04 12:56 ` [ptxdist] [PATCH 1/2] libnftnl: Upgrade from 1.0.6 to 1.0.9 Alexander Dahl
2018-04-04 12:56 ` [ptxdist] [PATCH 2/2] nftables: Upgrade from v0.6 to v0.8.3 Alexander Dahl

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=20180404125653.17631-1-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=ptxdist@pengutronix.de \
    /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