[1805] in linux-net channel archive
Re: Need help to connect to ISP!
daemon@ATHENA.MIT.EDU (Michael De La Rue)
Fri Feb 2 22:18:49 1996
Date: Fri, 2 Feb 1996 08:21:07 +0100 (MET)
From: Michael De La Rue <mikedlr@indy.unipress.waw.pl>
To: Greg Stein <gstein@eshop.com>
cc: Jim Serven <Jims@glix.com>, Nicolas Sayer <sayer@imaginet.fr>,
linux-admin@vger.rutgers.edu, linux-net@vger.rutgers.edu
In-Reply-To: <Pine.LNX.3.91.960131104449.9726C-100000@trouble.eshop.com>
On Wed, 31 Jan 1996, Greg Stein wrote:
> On Tue, 30 Jan 1996, Jim Serven wrote:
> > You Mumbled some Crazy Plan about "Need help to connect to ISP!":
> >
> > >But since my internet provider only gave me one dynamic adresse,
> > >all respons gets stopped on mercury.
> >
> > Get -3- STATIC IP #s from your ISP.
> >
> > With only 1 dynamic IP, you can't do anything with what you are trying to
> > accomplish.
> > You need 3 IP #s for this.
>
> Many won't provide 3 IPs. I was thinking about the same problem for here
> at home. Couldn't you run a SOCKS firewall on Linux? Then, all outgoing
> connections would be from the Linux machine's IP address.
>
> Would this work?
The problems here are fundamental, and what you are attempting is
essentially hackery (in the nice sense.. but also possibly in the
crackery sense). Each packet on the internet is identified by IP
address, so that it gets to the correct machine with the matching IP
address. No problem so far.
If you have only one IP address, then you have only one machine to send
packets to. Ah, you say, but my machines all have different addressses,
192.x.x.x. But this is where the problem is 192 is an address that can't
send packets outside. Anyone can construct a 192.x network (including
one with exactly the same addresses as you) and connect it safely to the
internet anywhere, but only because no gateway/router/brouter on the
internet will (should :-) ever transfer 192 packets, so those machines
can never communicate outside their network.
The reason your ISP has given you only one IP address may well be
precisely to stop you from connecting more than one machine. In this
case (and probably anyway, given that they have given you a dynamic IP
address) you should consider changing internet service provider.
SOCKS firewall:- This is fine as long as you have every program you want
to run SOCKS aware (replace libraries and they should all work except for
any which have been statically compiled etc..). But you still don't count
as properly connected. For example, running an FTP server on your PC
won't work properly.
Now here's where you could be really clever. Build a connection system
(into the gateway code of linux) which remaps internet connections from
the PC on it's ftp port to a different port on your linux machine. Then,
it will seem as if your Linux machine has two ftp servers running, and you
can connect to the second one with
ftp your.machine.name 3435
assuming you remapped the ftp service to port 3435....
This has the advantage that.. err.... that .... oh you can use the file
space on your windows machine for ftp saving space for linux... no you
could do that using local NFS anyway... um...
Alternatively, you could change service provider.
<rant on>
Serious service providers provide static addresses. The address is meant
to identify the machine. Just because it's cheaper dosen't mean it's
better.
<rant off>
<http://www.tardis.ed.ac.uk/~mikedlr/biography.html>
Scottish Climbing Archive: <http://www.tardis.ed.ac.uk/~mikedlr/climbing/>
Linux/Unix clone@ftp://src.doc.ic.ac.uk/packages/linux/sunsite.unc-mirror/docs/
