ip over ip tunneling

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What I'm suggesting is not NAT nor masquerading, although I suspect
that this will be taking place on machine b, once the tunnel is
setup. If you want to call it something other then ip over ip
tunneling, you could for all intents and purposes, call it a VPN
(virtual private, or maybe in this case, virtual public network). In fact, if you would have taken the time to look at the URLs
I provided in my original post, you would have immediately discovered
that this is not NAT/masquerading. I am familiar with iptables already,
and am currently running what I consider to be a fairly advanced
firewall setup here.

Greg


On Wed, Aug 11, 2004 at 10:55:16AM -0700, Ralph W. Reid wrote:
> What you are describing here sounds like network address translation
> (NAT) using masquerading.  I have not done this for a while, but the
> file /usr/doc/Linux-HOWTOs/Masquerading-Simple-HOWTO proved useful
> once I found it on my Slackware system.  As I recall, the systems must
> be able to communicate with each other first before NAT will work
> (kind of follows if a connection to the outside world is to be
> established).  The examples in the file I specified above are pretty
> basic, and as you get more involved with firewalling, you may want to
> do more with iptables.  If you do not have access to the file I
> mentioned above, let me know, and I can put it on my web site.  Keep
> plugging away at it--NAT and masquerading were pretty hard for me to
> figure out at first, but I did eventually get the mess working.  Let
> me know if I can provide any more help.  HTH and have a _great_ day.
> 

- -- 
Free domains: http://www.eu.org/ or mail dns-manager at EU.org

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFBGmdJ7s9z/XlyUyARAuQvAJsHqV4IjLkcFzCgoHo/u4HhZ4COuwCguFDH
0vDxogiJAqcNfFo3dgiS22k=
=0DkD
-----END PGP SIGNATURE-----