From: Arturo Borrero <aborrero@cica.es>
To: netfilter@vger.kernel.org
Subject: Double stack IPv4&&IPv6 for a firewall
Date: Fri, 24 Aug 2012 12:40:06 +0200 [thread overview]
Message-ID: <50375A06.6000808@cica.es> (raw)
[-- Attachment #1: Type: text/plain, Size: 1018 bytes --]
Hi there!
The way is recommended to implement IPv6 in a network while IPv4 is
still alive is double stack.
In a network where all have DNS records, double stack means that each
FQDN has an A reg. and an AAAA reg.
So, deploying a DNS-based firewall takes you to duplicate the ruleset,
first for iptables/ip6tables and then for ipset family inet/ipset family
inet6
The question is:
Do anyone knows a program, framework, script, method or whatever to face
this situation?
I'm talking of an 'abstraction' method that hides the differences
between iptables/ip6tables, as long as is using almost always FQDNs with
both DNS regs to configure the ruleset.
Best regards.
--
Arturo Borrero González
Departamento de Seguridad Informática, @NIS_CICA (twitter)
Centro Informático Científico de Andalucía (CICA)
Avda. Reina Mercedes s/n - 41012 - Sevilla (Spain)
Tfno.: +34 955 056 600 / FAX: +34 955 056 650
Consejería de Economía, Innovación, Ciencia y Empleo
Junta de Andalucía
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4238 bytes --]
next reply other threads:[~2012-08-24 10:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 10:40 Arturo Borrero [this message]
2012-08-24 14:29 ` Double stack IPv4&&IPv6 for a firewall John A. Sullivan III
2012-08-24 14:41 ` Jan Engelhardt
[not found] ` <CAPfcJatemcsT5PK+m8__xhB7gBRinAuq2wNX_g93CQrSmvtDhQ@mail.gmail.com>
2012-08-24 23:46 ` Jan Engelhardt
2012-08-26 3:38 ` Julien Vehent
[not found] ` <CAPfcJaugwb5DboUYGAfEktHCDZX0KxdCWdS9CyAu3rh94P8inQ@mail.gmail.com>
2012-08-28 8:55 ` Arturo Borrero
2012-08-28 11:43 ` Julien Vehent
2012-08-28 11:45 ` Amos Jeffries
2012-08-28 12:08 ` Arturo Borrero
2012-08-28 12:21 ` Amos Jeffries
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=50375A06.6000808@cica.es \
--to=aborrero@cica.es \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox