All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org, alexander@alemayhu.com
Subject: Re: [PATCH iptables 2/2] libxtables: pass AI_ADDRCONFIG flag to getaddrinfo()
Date: Wed, 8 Mar 2017 15:00:06 +0100	[thread overview]
Message-ID: <20170308140006.GA11040@salvia> (raw)
In-Reply-To: <alpine.LSU.2.20.1703081453420.4389@n3.vanv.qr>

On Wed, Mar 08, 2017 at 02:56:24PM +0100, Jan Engelhardt wrote:
> 
> On Wednesday 2017-03-08 14:16, Pablo Neira Ayuso wrote:
> >
> >If hints.ai_flags includes the AI_ADDRCONFIG flag, then IPv4 addresses
> >are returned in the list pointed to by res only if the local system has
> >at least one IPv4 address configured, and IPv6 addresses are only
> >returned if the local system has at least one IPv6 address configured.
> 
> But even if a system has no IPv4 address - think of a bridge -, you may
> want to resolve an `iptables -A FORWARD -s ... ` request.

Right, the br_netfilter Frankenstein needs this. Will make a second
shot at this.

  reply	other threads:[~2017-03-08 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 13:16 [PATCH iptables 1/2] iptables-translate: print nft command for each expand rules via dns names Pablo Neira Ayuso
2017-03-08 13:16 ` [PATCH iptables 2/2] libxtables: pass AI_ADDRCONFIG flag to getaddrinfo() Pablo Neira Ayuso
2017-03-08 13:56   ` Jan Engelhardt
2017-03-08 14:00     ` Pablo Neira Ayuso [this message]
2017-03-09  7:23 ` [PATCH iptables 1/2] iptables-translate: print nft command for each expand rules via dns names Alexander Alemayhu

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=20170308140006.GA11040@salvia \
    --to=pablo@netfilter.org \
    --cc=alexander@alemayhu.com \
    --cc=jengelh@inai.de \
    --cc=netfilter-devel@vger.kernel.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.