FreeBSD Bugzilla – Attachment 50662 Details for
Bug 77131
Fix a error in the firewall section (0.32 -> 0/32)
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
file.diff
file.diff (text/plain), 2.30 KB, created by
Brad Davis
on 2005-02-05 12:40:23 UTC
(
hide
)
Description:
file.diff
Filename:
MIME Type:
Creator:
Brad Davis
Created:
2005-02-05 12:40:23 UTC
Size:
2.30 KB
patch
obsolete
>--- doc-ori/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml Sat Feb 5 05:24:00 2005 >+++ doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml Sat Feb 5 05:24:46 2005 >@@ -1547,7 +1547,7 @@ > role="ipaddr">192.168.1.0/24</hostid>.</para> > > <para>The <replaceable>PUBLIC_ADDRESS</replaceable> can either >- be the external IP address or the special keyword `0.32', >+ be the external IP address or the special keyword `0/32', > which means to use the IP address assigned to > <replaceable>IF</replaceable>.</para> > </sect2> >@@ -1567,7 +1567,7 @@ > range specified to the left of the arrow symbol on the > <acronym>NAT</acronym> rule. On a match the packet has its > source IP address rewritten with the public IP address >- obtained by the `0.32' keyword. <acronym>NAT</acronym> posts a >+ obtained by the `0/32' keyword. <acronym>NAT</acronym> posts a > entry in its internal <acronym>NAT</acronym> table so when the > packet returns from the public Internet it can be mapped back > to its original private IP address and then passed to the >@@ -1614,7 +1614,7 @@ > with a <programlisting> tag ?--> > <para>A normal NAT rule would look like:</para> > >- <programlisting>map dc0 192.168.1.0/24 -> 0.32</programlisting> >+ <programlisting>map dc0 192.168.1.0/24 -> 0/32</programlisting> > > <para>In the above rule the packet's source port is unchanged > as the packet passes through IP<acronym>NAT</acronym>. By >@@ -1624,13 +1624,13 @@ > IP<acronym>NAT</acronym> to modify the source port to be > within that range:</para> > >- <programlisting>map dc0 192.168.1.0/24 -> 0.32 portmap tcp/udp 20000:60000</programlisting> >+ <programlisting>map dc0 192.168.1.0/24 -> 0/32 portmap tcp/udp 20000:60000</programlisting> > > <para>Additionally we can make things even easier by using the > <literal>auto</literal> keyword to tell IP<acronym>NAT</acronym> to determine > by itself which ports are available to use:</para> > >- <programlisting>map dc0 192.168.1.0/24 -> 0.32 portmap tcp/udp auto</programlisting> >+ <programlisting>map dc0 192.168.1.0/24 -> 0/32 portmap tcp/udp auto</programlisting> > </sect3> > > <sect3>
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 77131
: 50662