os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

ipnat doesn't support IP ranges with a.b.c.d-w.x.y.z notation,

Browse source 
but only with /netmask or /cidr notation

PR:		docs/95261
Submitted by:	fbsd_user@a1poweruser.com
This commit is contained in:
Giorgos Keramidas 2006-08-08 20:22:08 +00:00
parent 98fc7940a2
commit 74dc593238
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=28434
1 changed files with 13 additions and 8 deletions

21
en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml
View file

@ -1905,19 +1905,24 @@ block in log first quick on dc0 all
<sect3>
<title>Using a pool of public addresses</title>
<para>In very large LANs there comes a point where there are
just too many LAN addresses to fit into a single public
address. By changing the following rule:</para>
<para>In very large LANs there comes a point where there are just too
many LAN addresses to fit into a single public address. If a block
of public IP addresses is available, you can use these addresses as
a <quote>pool</quote>, and let IP<acronym>NAT</acronym> pick one of
the public IP addresses as packet-addresses are mapped on their way
out.</para>
<para>For example, instead of mapping all packets through a single
public IP address, as in:</para>
<programlisting>map dc0 192.168.1.0/24 -&gt; 204.134.75.1</programlisting>
<para>Currently this rule maps all connections through <hostid
role="ipaddr">204.134.75.1</hostid>. This can be changed
to specify a range:</para>
<para>A range of public IP addresses can be specified either with a
netmask:</para>
<programlisting>map dc0 192.168.1.0/24 -&gt; 204.134.75.1-10</programlisting>
<programlisting>map dc0 192.168.1.0/24 -&gt; 204.134.75.0/255.255.255.0</programlisting>
<para>Or a subnet using CIDR notation such as:</para>
<para>or using CIDR notation:</para>
<programlisting>map dc0 192.168.1.0/24 -&gt; 204.134.75.0/24</programlisting>
</sect3>