From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Setting up an ip-tunnel
Date: Mon, 05 May 2003 15:01:24 +0000 [thread overview]
Message-ID: <marc-lartc-105214696205960@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105214625905066@msgid-missing>
Patrick,
I would recommend first consulting with the firewall administrator, as
setting up tunnels through firewalls is not always regarded by security
admins as a friendly action. It may even be against your corporate
policy.
: I'm totally new to this mailinglist so I apologise for all and any
: profoundly stupid questions that I ask, but I haven't found what I was
: looking for anywhere else.
Here's an example of using GRE tunnels ("ip tunnel"):
http://lartc.org/howto/lartc.tunnel.gre.html#AEN333
: I have one computer that sits behind a firewall and another computer
: with a public IP-address outside the firewall. I would now want to set
: up an ip-tunnel between these two so that they can communicate
: "transparently".
If you need any sort of generic tunnel through which the two hosts can
communicate, you can also consider CIPE.
: I'm desperate for this information as I _need_ to be able to access the
: computer behind the firewall from the the one with a public ip.
Have you thought of using ssh port forwarding?
-Martin
--
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-05-05 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 14:49 [LARTC] Setting up an ip-tunnel Patrick Börjesson
2003-05-05 15:01 ` Martin A. Brown [this message]
2003-05-05 15:39 ` Patrick Börjesson
2003-05-05 15:54 ` Martin A. Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-105214696205960@msgid-missing \
--to=mabrown-lartc@securepipe.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.