Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: tlug: It works!
- To: tlug@example.com
- Subject: Re: tlug: It works!
- From: Jim Tittsler <jwt-tlug@example.com>
- Date: Fri, 9 Oct 1998 13:42:34 +0900
- Content-Type: text/plain; charset=us-ascii
- In-Reply-To: <3.0.6.32.19981009123510.0095b3e0@example.com>; from Darren Cook on Fri, Oct 09, 1998 at 12:35:10PM +0000
- Organization: 7J1AJH/AI8A Tokyo
- References: <Pine.LNX.3.96LJ1.1b7.981009113813.2528B-100000@example.com> <Pine.LNX.3.96LJ1.1b7.981009114358.2090F-100000@example.com jp> <3.0.6.32.19981009123510.0095b3e0@example.com>
- Reply-To: tlug@example.com
- Sender: owner-tlug@example.com
On Fri, Oct 09, 1998 at 12:35:10PM +0000, Darren Cook wrote: > Am I right in thinking those extra machines (eg. 192.168.1.2) can't do web > browsing, ftp, connect to a POP server, etc? So the only external machine > that can see them is the one with the two network cards? With Linux's IP Masquerading, it (almost*) all works transparently. The server keeps track of which of the private network machines made which request/connection, and automagically routes reply packets back to the appropriate private network host. Things like web browsing, POP, IMAP, telnet, etc. all work transparently. The private network host thinks it is talking directly to its destination host, but the masquerading host acting as the gateway, is rewriting the addresses so it looks like the requests from the outside world are coming from it. (*) It gets trickier with protocols like FTP that set up a connection on one port and then perform communications on another. There are modules that understand many of the "interesting" protocols and will keep track of the necessary private connections. There is a catch-all program that attempts to handle still other odd protocols that may not have a specific module to support them. > What I'm thinking is that when a web server on the net gets a request from > 192.168.1.2 how will it know where to send the reply to? Or am I > misunderstanding something (again :-)? The server will have rewritten the address to its real address, when the reply comes back, it puts the private address of the requesting machine back. IP Masquerade (and Network Address Translation, the larger category) info: http://w3.clat.hi-tech.ac.jp/LDP/HOWTO/mini/IP-Masquerade.html http://ipmasq.home.ml.org/ http://linas.org/linux/load.html (This feature is also present in many ISDN routers, such as the MN128-SOHO family.) -- Jim Tittsler, Tokyo ICQ: 5981586 --------------------------------------------------------------- Next Meeting: 10 October, 12:30 Tokyo Station Yaesu central gate Featuring the IMASY Eng. Team on "IPv6 - The Next Generation IP" Next Nomikai: 20 November, 19:30 Tengu TokyoEkiMae 03-3275-3691 --------------------------------------------------------------- Sponsor: PHT, makers of TurboLinux http://www.pht.co.jp
- Follow-Ups:
- Re: tlug: It works!
- From: Scott Stone <sstone@example.com>
- Re: tlug: It works!
- From: "Stephen J. Turnbull" <turnbull@example.com>
- References:
- Re: tlug: It works!
- From: Jonathan Byrne - 3Web <jq@example.com>
- Re: tlug: It works!
- From: Darren Cook <darren@example.com>
Home | Main Index | Thread Index
- Prev by Date: Re: tlug: It works!
- Next by Date: tlug: A little NT chuckle...
- Prev by thread: Re: tlug: It works!
- Next by thread: Re: tlug: It works!
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links