[2253] in linux-net channel archive
Re: Networking: one IP setup -- Impossible ??
daemon@ATHENA.MIT.EDU (amonk)
Tue Mar 26 01:44:49 1996
Date: Tue, 26 Mar 1996 01:28:38 -0500 (EST)
From: amonk <amonk@labyrinth.cftnet.com>
To: Thomas Pawlikaniec <neutrino@ee.mcgill.ca>
cc: linux Net mailing list <linux-net@vger.rutgers.edu>,
linux PPP mailing list <linux-ppp@vger.rutgers.edu>
In-Reply-To: <Pine.SUN.3.91.960325004218.2648B-100000@skyler>
You have a few options:
But first I'd suggest getting a NIC for each box. Add a static route to
the NIC on the Linux box and make the IP address one in the range of reserved
IP addresses (ie. 172.10.10.2 or something). On your second box, make
the NIC ansewr to 172.10.10.3 or something and make the default route point
to your linux box which should already be resolving names for you properly.
That will establish dandy communication between your two machines and will
also allow the second machine to send datagrams to the internet... but
getting data BACK to the second machine is the rub. That's where your
options come in.
1) Go the SOCKS route with a sockd on box 1 and socksified clients on box 2.
2) Get ipfw or ipfwadm and read all the possible hackery you might manage.
3) Get something like the TIS firewall toolkit and set up proxy servers
on box 1.
Hope that helps a little. For more info, search and read and ask and
search and read and try and try again... 8-)
Kyle
------------------------------------------------------------------------------
Kyle Amon amonk@labyrinth.cftnet.com http://labyrinth.cftnet.com/kka
------------------------------------------------------------------------------
On Mon, 25 Mar 1996, Thomas Pawlikaniec wrote:
>
> [to folx on linux-net list : It seems I am not getting any posts from it.
> Maybe that's normal (?), if not: if answers to my problem appeared there,
> sorry, someone be kind and send them to me please. Thanx!]
>
>
> Here's something I would like to get working, if at all possible:
>
> ( my provider) ( My home )
>
> ISP ---(PPP modem link)--- Machine #1 (one IP, dynamically assigned)
> |
> | (ethernet or ?)
> |
> Old Machine #2 (no real IP available here)
>
> Machine #1 connects, and works well as a part of the Internet once the
> connection is established. But I would like to be able to use
> machine #2 also as another site connected on the net, without having to
> log onto Machine #1 first, and from there jump on the Internet.
> Also, I would like to be able to access Machine #2 from the Internet,
> through Machine #1.
>
> In other terms, I would like to be able to do something like SLIRP does
> for shell accounts, transforming them into regular PPP/SLIP accounts as
> far as software on the Machine #2 is concerned. I don't mind if this is
> complicated, I want to practice and to have fun with networking basically :-)
>
> I read the NET-2 howto and the NAG, but I am still uncertain of the steps
> to take to get what I need. Please correct me or confirm on each of the
> following ideas I have now about making such a setup.
>
> I imagine this will be tricky if at all doable, (is it?) and will probably
> involve the reserved class of addresses (like 10.x.x.x for example) behind
> some sort of firewall/gateway running on Machine #1.
> For example, Machine 1 could get the 10.0.0.1 IP on the home network (as
> well as another regular IP attributed by the ISP at connection: Machine #1
> would have 2 IPs then -- does it have to have 2 IPs actually ?), and
> machine #2 would be 10.0.0.2 (or whatever within the reserved range).
> -OR-
> do I have to have 2 IPs fom the regular ones available ? (in which case
> the whole exercice is impossible)
>
> I am not certain I understood well the principle of a firewall/proxy
> server, but I think I will have to throw that into the setup too. Am I
> right ? In case you wonder, _yes_ I am a little (a lot! ;-) ) confused
> here...
>
> Right now, Machine #1 and Machine #2 have no connection at all: I can
> set-up that one with:
> - 'el cheapo' ;-) ethernet cards [I think the preferred solution]
> - PLIP link [even cheaper, but not so fun ;-) ]
> - serial line PPP (anyone done that ?)
> - anything that might make it work !
>
> [actually Machine #2 is basically not used, that's why they are not
> connected... If I do this it's really to understand how things work!]
>
> I believe there will be no fundamental design differences (other than speed)
> between any of these, in which case I will probably go for NE2000 ethernet
> cards. If the design of the system gets different depending on the choice
> of the connection method, please tell me how and pros/cons.
>
> If it appears I need to run a nameserver on Machine #1 or any other kind
> of serious program like that, I will be glad to do so :-)
>
> However, I would like to have the cleaniest design possible -- not
> necessarily the simplest to set-up, but the most capable, with the least
> limitations (I am sure there are some, if not only the fact that it will
> be much more complex in any case than if I had 2 IPs available -- which I
> probably could have if that was business matters, but again: I would like
> to try this thing out, for the fun of understanding better how networking
> works :-) as far as Linux allows me to! )
>
> Any comments welcome, especially an ordered list of the steps I need to
> take. Thank you in advance :-)
>
>
> Thomas Pawlikaniec
> .sig coming Real Soon Now!
>
>
>
