[1801] in linux-net channel archive
Re: Need help to connect to ISP!
daemon@ATHENA.MIT.EDU (Harvey J. Stein)
Fri Feb 2 17:55:49 1996
Date: Thu, 1 Feb 1996 22:41:19 +0200
From: "Harvey J. Stein" <abel@netvision.net.il>
To: ecarp@netcom.com
In-reply-to: <199601311325.IAA28596@dal1820.computek.net>
CC: hjstein@bogart.nnt.com, linux-net@vger.rutgers.edu
"Ed Carp, KHIJOL SysAdmin" writes:
> > 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.
>
> Why is that? You only need one static IP - any number of sites can hide
> behind you. See the SOCKS documentation for details. You don't need to
> turn on that silly IP masquerading, either.
But what do you do about the fact that the IP address is dynamic? If
I understand the SOCKS docs, you must set up a sockd.route for the
machine with the ppp connection, and must stick the interface address
into sockd.route.
As far as I can tell, this means that you must either
a) snarf the address up after ppp has brought up the interface, and
write it to the sockd.route file, or
b) Figure out the range of addresses that your ip provider will
allocate, and stick them *all* into the sockd.route file, or
c) run your system with ip-forwarding turned on, thus losing the
firewalling protection of SOCKS.
Is this really the case? It'd be nice if the sockd.route file could
be told which *interface* is associated with some set of destinations
as opposed to which interface *address* is associated. Is this
possible?
Thanks,
Dr. Harvey J. Stein
Berger Financial Research
abel@netvision.net.il (temporary address)
