From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tim Groeneveld Date: Mon, 15 Oct 2007 13:12:40 +0000 Subject: Re: FW: [LARTC] Routing public IP's through a gateway Message-Id: <200710152312.43342.tim@timg.ws> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0679564760==" List-Id: References: <200710142307.12127.tim@timg.ws> In-Reply-To: <200710142307.12127.tim@timg.ws> To: lartc@vger.kernel.org --===============0679564760== Content-Type: multipart/signed; boundary="nextPart1237562.K50YhZCxmW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart1237562.K50YhZCxmW Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Monday 15 October 2007 11:07:39 pm Dan wrote: > So, according to your emails, your external (eth1) interface on the Gateway > machine ** needs to be .209 not .211 or .210 ** (as this is where the ISP's > 'router' is pointing the .72 subnet according to what you said), and you > need to type echo 1 > /proc/sys/net/ipv4/ip_forward on the gateway machine. > No route commands needed: the Gateway machine knows where the .72 subnet > is, because it has an interface on it. The Gateway Machine's default > gateway is set to your normal ISP's gateway. .209 is taken by the routers gateway, so, it needs to be 210. --nextPart1237562.K50YhZCxmW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHE2dLRPexiTfIAEIRAt3NAKDjqA4KIZFTcGzz6d8KXpbAUu3BwQCfaOqP h91U/GMJgOc1xuyOeGwYD0M= =gZKK -----END PGP SIGNATURE----- --nextPart1237562.K50YhZCxmW-- --===============0679564760== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============0679564760==--