From: Philip Craig <philipc@snapgear•com>
To: Jiri Pirko <jpirko@redhat•com>
Cc: "Rémi Denis-Courmont" <remi.denis-courmont@nokia•com>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [question] bridged tunnel
Date: Tue, 28 Jul 2009 18:28:05 +1000 [thread overview]
Message-ID: <4A6EB695.2070202@snapgear.com> (raw)
In-Reply-To: <20090728081818.GA6522@psychotron.englab.brq.redhat.com>
Jiri Pirko wrote:
> Well generally there could be anything (e.g. internet) in between ROUTER A and
> B. That's why.
If the internet is in the middle, then you don't want to invent your own
tunneling. Using something like OpenVPN in tap mode, or gretap over IPSec.
next prev parent reply other threads:[~2009-07-28 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 7:59 [question] bridged tunnel Jiri Pirko
2009-07-28 8:11 ` Rémi Denis-Courmont
2009-07-28 8:18 ` Jiri Pirko
2009-07-28 8:28 ` Philip Craig [this message]
2009-07-28 8:43 ` Jiri Pirko
2009-07-28 8:12 ` Philip Craig
2009-07-28 8:20 ` Jiri Pirko
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=4A6EB695.2070202@snapgear.com \
--to=philipc@snapgear$(echo .)com \
--cc=jpirko@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=remi.denis-courmont@nokia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox