From ec0f0c365469349e2ec97fa210fe0497779ff75e Mon Sep 17 00:00:00 2001 From: Peter Pentchev Date: Mon, 9 Aug 2004 12:00:47 +0000 Subject: [PATCH] Emphasize a bit the need for an all-ones netmask on "secondary" interface addresses. PR: 68746 Reported by: Dave Duchscher Reviewed by: keramida --- en_US.ISO8859-1/books/handbook/config/chapter.sgml | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/config/chapter.sgml b/en_US.ISO8859-1/books/handbook/config/chapter.sgml index 6f1ef25728..2f56093f1d 100644 --- a/en_US.ISO8859-1/books/handbook/config/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/config/chapter.sgml @@ -1137,7 +1137,9 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms 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 1s. + netmask of all 1s (expressed as either + 255.255.255.255 or 0xffffffff). + For example, consider the case where the fxp0 interface is @@ -1148,7 +1150,15 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms We want the system to appear at 10.1.1.1 through 10.1.1.5 and at 202.0.75.17 through - 202.0.75.20. + 202.0.75.20. As noted above, only the + first address in a given network range (in this case, + 10.0.1.1 and + 202.0.75.17) should have a real + netmask; all the rest (10.1.1.2 + through 10.1.1.5 and + 202.0.75.18 through + 202.0.75.20) must be configured with a + netmask of 255.255.255.255. The following entries configure the adapter correctly for this arrangement: