Re: DHCPCD on an internal LAN
- From: Davorin Vlahovic <nrubA@xxxxxxxxxxxxxx>
- Date: Mon, 10 Dec 2007 23:31:49 +0000 (UTC)
On 2007-12-10, Mike <Not@xxxxxxxxxxx> wrote:
Quite the opposite. I don't want the LAN machines to ever connect to
the internet at all. The only machine that should ever connect to the
internet should be the P2 machine. All others on the LAN should only
be able to SSH into an account on the P2 and run P2 applications
remotely via SSH to surf etc. Therefore, only one machine ever goes
online (the P2), and only one internet connection required. And, each
internal LAN machine should remain isolated from any other on the
LAN. A kind of "blind tentacle" arrangement with the P2 as head.
Hope you don't have any unix prodigies on the client side; I can
think of at least two ways to fool p2 computer and let clients to use
the Internet directly :) One would be a ssh tunnel, the other could be a
small python/perl script that would act as a proxy :)
I guess you should add some L7 filtering to the p2 machine ;)
--
Ignorance has taken over
Yo, we gotta take the power back!
-- Rage Against The Machine, Take the power back
.
- Follow-Ups:
- Re: DHCPCD on an internal LAN
- From: Mike
- Re: DHCPCD on an internal LAN
- References:
- DHCPCD on an internal LAN
- From: Mike
- Re: DHCPCD on an internal LAN
- From: Ivan Marsh
- Re: DHCPCD on an internal LAN
- From: Mike
- DHCPCD on an internal LAN
- Prev by Date: Re: DHCPCD on an internal LAN
- Next by Date: Re: DHCPCD on an internal LAN
- Previous by thread: Re: DHCPCD on an internal LAN
- Next by thread: Re: DHCPCD on an internal LAN
- Index(es):
Relevant Pages
|