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: Fri, 25 May 2001 17:14:35 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <3B0E0929.DC292FA0@example.com>; from 9915104t@example.com on Fri, May 25, 2001 at 04:26:34PM +0900
- References: <3B0DEE65.3B255773@example.com> <20010525144314.A30956@example.com> <3B0DFB06.7CB463FD@example.com> <20010525153130.B30956@example.com> <3B0E0929.DC292FA0@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <dBBB4.A._MF.dThD7@example.com>
- Resent-Sender: tlug-request@example.com
B0Ti (9915104t@example.com) wrote: > My ISP is leasing an NTT OCN line (128k) for its server. They're providing > internet services for the dorm I live in using the phonelines with a TUT > Systems Home Run adapter that connects to an ethernet card. Dang, that must be slow! So what happens is you call a number on the internal phone system of the dorm to get Internet access, right? In that case, their access server is probably assigning it's IP pool out of 192.168.1.0/24, so some of the addresses in that range will be in use at any given time. If the "ISP" is only giving you one IP address, obtained by dialup, then a setup like the one below should work. Note that this requires two NICs in your desktop machine. It's just like dialing into a real ISP that assigns an IP address to the dialup host. If you want more machines on the link, the dialup host has to NAT for them: *************** dialup * phone line| eth0 ***************** access *---------------------------------*Your desktop * server * | 192.168.1.83 * machine * 192.168.1.254 * ***************** *************** | eth1 (192.168.2.1) | | eth0 (192.168.2.2) ***************** * Your notebook * * *************** ***************** * * VMWare * * 192.168.2.3 * *************** In this example, the desktop is being assigned 192.168.1.6 by the access server. It's gateway is 192.168.1.1 The desktop serves as the NAT box for the notebook machine. Network 192.168.2.0/24 is connected to eth0 on the desktop, and is NATted. The notebook's eth0 has address 192.168.2.2, and it's gateway is 192.168.2.1. In VMWare, give Windows 192.168.2.3 for its virtualized NIC as presented to it by VMWare. It's gateway will also be 192.168.2.1. Jonathan
- Follow-Ups:
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: "A.Sajjad Zaidi" <sajjad@example.com>
- References:
- networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Re: networking trouble
- From: B0Ti <9915104t@example.com>
- Re: networking trouble
- From: Jonathan Q <jq@example.com>
- Re: networking trouble
- From: B0Ti <9915104t@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