All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 13961] New: ip6tables-nft build does not include MASQUERADE target options
Date: Tue, 02 Nov 2021 20:13:26 +0000	[thread overview]
Message-ID: <bug-13961-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=13961

            Bug ID: 13961
           Summary: ip6tables-nft build does not include MASQUERADE target
                    options
           Product: buildroot
           Version: 2021.02.3
          Hardware: All
                OS: Linux
            Status: RESOLVED
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: mbuil@suse.com
                CC: buildroot@uclibc.org
  Target Milestone: ---
        Resolution: DUPLICATE
            Status: RESOLVED

Since 1.6, iptables supports the MASQUERADE target options:

MASQUERADE target options:
 --to-ports <port>[-<port>]
                                Port (range) to map to.
 --random
                                Randomize source port.
 --random-fully
                                Fully randomize source port.

When building iptables-nft, the MASQUERADE target options are included in the
iptables-nft binary, however, they are not in the ip6tables-nft:

$> sudo ./output/target/usr/sbin/iptables-nft -A POSTROUTING -s 10.244.0.0/16 !
-d 224.0.0.0/4 -j MASQUERADE --help | grep random
 --random
 --random-fully
                                Fully randomize source port.
$> sudo ./output/target/usr/sbin/ip6tables-nft -A POSTROUTING -s 10.244.0.0/16
! -d 224.0.0.0/4 -j MASQUERADE --help | grep random
$>

Those targets come from the files libipt_MASQUERADE.c and libip6t_MASQUERADE.c
in https://git.netfilter.org/iptables/tree/extensions but for some reason the
ip6 one does not get included in the binary

--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---


*** This bug has been marked as a duplicate of bug 13971 ***

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

                 reply	other threads:[~2021-11-02 20:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-13961-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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.