From owner-freebsd-questions Mon Dec 14 15:29:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29769 for freebsd-questions-outgoing; Mon, 14 Dec 1998 15:29:41 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from voyager.planb.com.au (voyager.planb.com.au [203.35.172.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA29764 for ; Mon, 14 Dec 1998 15:29:38 -0800 (PST) (envelope-from kevin@planb.net.au) Received: from fossil.planb.com.au (fossil.planb.com.au [203.35.172.145]) by voyager.planb.com.au (8.8.7/8.8.8) with SMTP id KAA15418; Tue, 15 Dec 1998 10:29:05 +1100 (EST) Received: by fossil.planb.com.au with Microsoft Mail id <01BE280D.76F4E780@fossil.planb.com.au>; Tue, 15 Dec 1998 09:29:50 +1100 Message-ID: <01BE280D.76F4E780@fossil.planb.com.au> From: Kevin Sheehan To: Dan , "'Lew Payne'" Cc: "freebsd-questions@FreeBSD.ORG" Subject: RE: Strange Network Problem Date: Tue, 15 Dec 1998 09:29:48 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 2) What is the proper netmask for aliased IPs? I have found reasonably >> authoritative references to both 255.255.255.255 and 255.255.255.254 in >> the archives. I would like to clear this up. > >Huh? The proper netmask to use is the netmask which accurately >represents the address block you've been assigned. You must ASK >what the actual address block is that those other IP's came from, >and set your netmask accordingly. Setting an arbitrary netmask >is an invitation to disaster. The broadcast address, computed >from your netmask, MAY BE ALREADY ASSIGNED TO ANOTHER MACHINE. A mask of 255.255.255.255 is not so bad for an alias. Rgs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message