Emphasize a bit the need for an all-ones netmask on "secondary"

interface addresses.

PR:		68746
Reported by:	Dave Duchscher <daved@tamu.edu>
Reviewed by:	keramida
This commit is contained in:
Peter Pentchev 2004-08-09 12:00:47 +00:00
parent 038efbe67a
commit ec0f0c3654
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21878

View file

@ -1137,7 +1137,9 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
fortunately quite simple. For a given interface, there must be
one address which correctly represents the network's netmask.
Any other addresses which fall within this network must have a
netmask of all <literal>1</literal>s.</para>
netmask of all <literal>1</literal>s (expressed as either
<literal>255.255.255.255</literal> or <literal>0xffffffff</literal>).
</para>
<para>For example, consider the case where the
<devicename>fxp0</devicename> interface is
@ -1148,7 +1150,15 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen>
We want the system to appear at <hostid role="ipaddr">10.1.1.1</hostid>
through <hostid role="ipaddr">10.1.1.5</hostid> and at
<hostid role="ipaddr">202.0.75.17</hostid> through
<hostid role="ipaddr">202.0.75.20</hostid>.</para>
<hostid role="ipaddr">202.0.75.20</hostid>. As noted above, only the
first address in a given network range (in this case,
<hostid role="ipaddr">10.0.1.1</hostid> and
<hostid role="ipaddr">202.0.75.17</hostid>) should have a real
netmask; all the rest (<hostid role="ipaddr">10.1.1.2</hostid>
through <hostid role="ipaddr">10.1.1.5</hostid> and
<hostid role="ipaddr">202.0.75.18</hostid> through
<hostid role="ipaddr">202.0.75.20</hostid>) must be configured with a
netmask of <literal>255.255.255.255</literal>.</para>
<para>The following entries configure the adapter correctly for
this arrangement:</para>