mirror of
https://gitlab.com/shorewall/code.git
synced 2025-04-10 10:48:52 +02:00
Update IPv6 Article
- Remove 'No NAT' bullet Signed-off-by: Tom Eastep <teastep@shorewall.net>
This commit is contained in:
parent
75df718865
commit
646572098c
@ -202,23 +202,6 @@
|
|||||||
Shorewall with some notable exceptions:</para>
|
Shorewall with some notable exceptions:</para>
|
||||||
|
|
||||||
<variablelist>
|
<variablelist>
|
||||||
<varlistentry>
|
|
||||||
<term>No NAT</term>
|
|
||||||
|
|
||||||
<listitem>
|
|
||||||
<para>In Shorewall6, there is no NAT of any kind (Netfilter6 doesn't
|
|
||||||
support any form of NAT). Most people consider this to be a giant
|
|
||||||
step forward.</para>
|
|
||||||
|
|
||||||
<para>When an ISP assigns you an IPv6 address, you are actually
|
|
||||||
assigned an IPv6 <firstterm>prefix</firstterm> (similar to a
|
|
||||||
subnet). A 64-bit prefix defines a subnet with 4 billion hosts
|
|
||||||
squared (the size of the IPv4 address space squared). Regardless of
|
|
||||||
the length of your prefix, you get to assign local addresses within
|
|
||||||
that prefix.</para>
|
|
||||||
</listitem>
|
|
||||||
</varlistentry>
|
|
||||||
|
|
||||||
<varlistentry>
|
<varlistentry>
|
||||||
<term>Default Zone Type</term>
|
<term>Default Zone Type</term>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user