From: gianluca <gianluca@gurutech.it>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] bypass bridge for backup
Date: Wed, 14 Nov 2007 15:13:27 +0100 [thread overview]
Message-ID: <473B0287.6090303@gurutech.it> (raw)
In-Reply-To: <96CF49BD8B56384395D698BA99007FA32D48@exchange.pacwire.local>
Thank you.
in fact this is what i need, but i've a problem: my device is an
embedded platform
http://www.pcengines.ch/alix2c3.htm
so i need something external or a link to a do-it-yourself instructions
(i'm able with solder and electronics part)
Bye
Gianluca
Leigh Sharpe escribio':
> Portwell have some 2-port and 4-port bypass cards which will do the job.
> So do some other manufacturers.
>
>
> -----Original Message-----
> From: bridge-bounces@lists.linux-foundation.org
> [mailto:bridge-bounces@lists.linux-foundation.org] On Behalf Of gianluca
> Sent: Saturday, 10 November 2007 9:24 AM
> To: bridge@lists.linux-foundation.org
> Subject: [Bridge] bypass bridge for backup
>
> Hi everyone,
> I'm using linux bridging for a trasparent firewall.
> There is some kind of external hardware that I can use to bypass
> my firewall in case of failure?
> I mean: if I power off my firewall I want to join physically the
> two network segments without reconnecting any wire (and possibly without
> touching any button)
>
> Thank You
> Gianluca
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>
next parent reply other threads:[~2007-11-14 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96CF49BD8B56384395D698BA99007FA32D48@exchange.pacwire.local>
2007-11-14 14:13 ` gianluca [this message]
2007-11-12 21:48 [Bridge] bypass bridge for backup Leigh Sharpe
-- strict thread matches above, loose matches on Subject: below --
2007-11-09 22:23 gianluca
2007-12-26 7:14 ` richardvoigt
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=473B0287.6090303@gurutech.it \
--to=gianluca@gurutech.it \
--cc=bridge@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox