Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: networking trouble
- To: tlug@example.com
- Subject: Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Date: Sat, 26 May 2001 13:56:48 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <21DEAE09F017D111969700A0C9840752059DA7C1@example.com>; from SStone@example.com on Fri, May 25, 2001 at 10:18:21AM -0700
- References: <21DEAE09F017D111969700A0C9840752059DA7C1@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <AJL-LC.A.kaG.CgzD7@example.com>
- Resent-Sender: tlug-request@example.com
Scott Stone (SStone@example.com) wrote: > therefore the original poster's use of 192.168.0.0/16 is perfectly valid :) If he were aggregating it, yeah. But when your local subnet is really only 192.168.1.0, no. You should use the correct mask for what your network really, even if you can get away with using the wrong one. There's certainly nothing to be gained from doing it anything less than completely correctly, especially when you don't even have the bad excuse of saving effort by doing it wrong. Jonathan
- References:
- RE: networking trouble
- From: Scott Stone <SStone@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: networking trouble
- Next by Date: Re: Linux and ADSL
- Prev by thread: RE: networking trouble
- Next by thread: RE: networking trouble
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links