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: jwb@example.com (Jim Breen)
- Date: Fri, 25 May 2001 15:35:41 +0900 (JST)
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <sbLnj.A.cvE.70fD7@example.com>
- Resent-Sender: tlug-request@example.com
From: B0Ti <9915104t@example.com> >> Jonathan Q wrote: >> >> > > IP address: 192.168.1.83 (assigned by the ISP) >> >> > Try renumbering this to 192.168.1.10 and see if it helps. >> >> > > IP address: 192.168.2.11 >> > Like above, renumber this to 192.168.1.11 255.255.255.0. >> >> The reason I didn't do this was because I assume 192.168.1.* adresses are >> handled by the ISP, >> and there is a chance that for example 192.168.1.11 is assigned to >> somebody else, so if I set laptop or vmware to be the same IP it might >> interfere with that. No chance, unless the ISP is breaking the rules. 192.168.*.* is one of a range of IP addresses that cannot be routed. They are intended purely for private networks hiding behind NAT, portmapping, etc. This is all in RFC1597. The other such ranges are 10.0.0.0 - 10.255.255.255 and 172.16.0.0 - 172.31.255.255. You can read all about this in some old lecture notes of mine: http://www.csse.monash.edu.au/~jwb/subjects/cse5803/addr/addr_issues.html Jim -- Jim Breen [jwb@example.com http://www.csse.monash.edu.au/~jwb/] Visiting Professor, Institute for the Study of Languages and Cultures of Asia and Africa, Tokyo University of Foreign Studies, Japan +81 3 5974 3880 [$B%8%`!&%V%j!<%s(B@$BEl5~30Bg(B]
- Follow-Ups:
- Re: networking trouble
- From: Jonathan Q <jq@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: networking trouble
- Next by Date: Re: networking trouble
- Prev by thread: Re: networking trouble
- Next by thread: Re: networking trouble
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links