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: "A.Sajjad Zaidi" <sajjad@example.com>
- Date: Fri, 25 May 2001 18:09:47 +0900
- Content-Transfer-Encoding: 7bit
- Content-Type: text/plain; charset=iso-2022-jp
- Organization: Vanguard K.K.
- References: <3B0DEE65.3B255773@example.com> <20010525144314.A30956@example.com> <3B0DFB06.7CB463FD@example.com> <20010525153130.B30956@example.com> <3B0E0929.DC292FA0@example.com> <20010525171435.E30956@example.com>
- Reply-To: tlug@example.com
- Resent-From: tlug@example.com
- Resent-Message-ID: <zdo52.A.mSF.iFiD7@example.com>
- Resent-Sender: tlug-request@example.com
- Sender: sajjad
You dont need 2 NICs. It will also work fine with an aliased IP. Also it might make things clearer if another IP range is used for the local network (10. or 172.). And yes, I did manage to get this setup, including NAT, working without problem inside VMware. asz Jonathan Q wrote: > 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 > > ----------------------------------------------------------------------- > Next Technical Meeting: Sat, May 12 13:30- > Next Nomikai Meeting: Fri, June (TBA) 19:30- Tengu Tokyo Eki Mae > ----------------------------------------------------------------------- > more info: http://www.tlug.gr.jp Sponsor: Global Online Japan
- Follow-Ups:
- Re: networking trouble
- From: B0Ti <9915104t@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>
- 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