All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Alemayhu <alexander@alemayhu.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] libxtables: duplicated loopback address via host_to_ipaddr()
Date: Thu, 9 Mar 2017 08:32:56 +0100	[thread overview]
Message-ID: <20170309073256.GB32270@gmail.com> (raw)
In-Reply-To: <1488983584-26091-1-git-send-email-pablo@netfilter.org>

On Wed, Mar 08, 2017 at 03:33:04PM +0100, Pablo Neira Ayuso wrote:
> Originally reported as a iptables-translate problem, but this also
> affects iptables and ip6tables.
> 
>  $ iptables-translate -A INPUT -s localhost -j ACCEPT
> 
> gives duplicated rules:
> 
>  nft add rule ip filter INPUT ip saddr 127.0.0.1 counter accept
>  nft add rule ip filter INPUT ip saddr 127.0.0.1 counter accept
> 
> This handling sucks, but libc seem to need if we have 127.0.0.1 and ::1
> entries in /etc/hosts that are common in many distros.
> 
> For more info, see:
> 
> https://sourceware.org/bugzilla/show_bug.cgi?id=4980
> https://bugzilla.redhat.com/show_bug.cgi?id=496300
> 
> Reported-by: Alexander Alemayhu <alexander@alemayhu.com>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>

Was going to test it, but it does not apply.

Applying: libxtables: duplicated loopback address via host_to_ipaddr()
error: patch failed: libxtables/xtables.c:1375
error: libxtables/xtables.c: patch does not apply
Patch failed at 0001 libxtables: duplicated loopback address via host_to_ipaddr()
The copy of the patch that failed is found in: .git/rebase-apply/patch
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

-- 
Mit freundlichen Grüßen

Alexander Alemayhu

      parent reply	other threads:[~2017-03-09  7:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 14:33 [PATCH] libxtables: duplicated loopback address via host_to_ipaddr() Pablo Neira Ayuso
2017-03-08 16:25 ` Jan Engelhardt
2017-03-08 16:25   ` [PATCH 1/3] extensions: libxt_socket: add --restore-skmark option Jan Engelhardt
2017-03-08 16:25   ` [PATCH 2/3] build: resolve build error involving libnftnl Jan Engelhardt
2017-03-08 16:25   ` [PATCH 3/3] extensions: restore matching any SPI id by default Jan Engelhardt
2017-03-08 16:26 ` Filter duplicate IP addresses from libxtables Jan Engelhardt
2017-03-08 16:26   ` [PATCH 1/3] libxtables: remove unnecessary nesting from host_to_ip(6)addr Jan Engelhardt
2017-03-08 16:45     ` Pablo Neira Ayuso
2017-03-08 16:26   ` [PATCH 2/3] libxtables: abolish AI_CANONNAME Jan Engelhardt
2017-03-08 16:46     ` Pablo Neira Ayuso
2017-03-08 16:26   ` [PATCH 3/3] libxtables: avoid returning duplicate address for host resolution Jan Engelhardt
2017-03-08 16:45     ` Pablo Neira Ayuso
2017-03-08 16:56       ` Jan Engelhardt
2017-03-10 18:22         ` Pablo Neira Ayuso
2017-03-08 16:42 ` [PATCH 1/3] libxtables: remove unnecessary nesting from host_to_ip(6)addr Jan Engelhardt
2017-03-08 16:42   ` [PATCH 2/3] libxtables: abolish AI_CANONNAME Jan Engelhardt
2017-03-08 16:42   ` [PATCH 3/3] libxtables: avoid returning duplicate address for host resolution Jan Engelhardt
2017-03-09  7:32 ` Alexander Alemayhu [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=20170309073256.GB32270@gmail.com \
    --to=alexander@alemayhu.com \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.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.