Date: Thu, 29 Jul 2004 10:32:32 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: "Hakim Z. Singhji" <system-administrator@earthlink.net> Cc: Hakim Singhji <Hakim.Singhji@nychhc.org> Subject: Re: HOWTO Ping LAN??? Message-ID: <20040729093232.GA86114@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <41088DB2.7010506@earthlink.net> References: <20040728T131509Z_C5AF00120003@nychhc.org> <20040728132659.2f368ade.wmoran@potentialtech.com> <41088DB2.7010506@earthlink.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Thu, Jul 29, 2004 at 01:40:02AM -0400, Hakim Z. Singhji wrote:
> Figure 1
>=20
> ***************
> * Internet *
> *24.199.1xx.xx*
> ***************
> ~ |
> ~ |
> *************** **************
> * Defaut GW * __ __ *Kids Machine*
> *192.68.0.0 * *192.68.0.3 *
> ~ FreeBSD 4.10 * * Mandrake 10*
> *************** **************
> ~ |
> ~ |
> ***************
> *Wrk Station 1*
> *192.68.0.1 *
> *Redhat 9 *
> ***************
>=20
> This is a rough diagram of the network... I would like to ssh, ping,
> etc. the machines behind the default gateway directly (without
> tunneling) from the outside the network (at work for example). Is this
> possible and if so how do I config. Keep in mind that my default
> gateway is FreeBSD. I know this may be a complicated project but if you
> could help that would help me greatly. Many thanks to everyone in advanc=
e.
I'm afraid that's not going to be possible with your current network
layout. If you want all of your machines to be accessible from the
Internet, then you'll need routable addresses on all of your machines.
I know you've said you don't want to use tunnelling, but
unfortunately, that's the only way you can access a private address
space as you have from outside it. A relatively simple way of doing
that is to ssh into your gateway box, and use the '-L' or '-R'
portforwarding options to create a tunnel to one of the internal
machines, and then ssh or otherwise connect through that tunnel: see
eg.
http://www.linux.ie/articles/tutorials/ssh.php
One other point: you're going to have problems if you're using
192.168.0.0 as the IP number on your FreeBSD machine. That's the
*network* address, and shouldn't be applied directly to any specific
machine. If you're running your internal network using 192.168.0.0/24
as the address space, then you have 254 addresses (from 192.168.0.1 to
192.168.0.254) to use for client machines, since 192.168.0.0 (network
address) and 192.168.0.255 (broadcast address) are reserved as part of
the networking setup.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--UugvWAfsgieZRqgk
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD4DBQFBCMQwiD657aJF7eIRAhAKAJjYBlhisUw8hTCZZwcxcUpETczSAJ9y/aP+
KZOfq7ctOWJImL/xgfEmZA==
=aJT/
-----END PGP SIGNATURE-----
--UugvWAfsgieZRqgk--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040729093232.GA86114>