From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] two ethernet in a raspberry pi.
Date: Tue, 30 Jun 2015 23:29:38 +0100 [thread overview]
Message-ID: <d81bf2686377e9c66173f7f396cf53ec@quintile.net> (raw)
In-Reply-To: <CAFSF3XMqP-nZDSq3ZPTM4W14XhNYTNwWr0Y1nekEMYxiL139ng@mail.gmail.com>
> Why do you need a computer, a hub is not good enough?
Its to straddle inside to outside of a restrictive firewall, I want to make sure no
packets can jump from one to another, however you can import(1) the outside interface
if you can login from inside (I think I got that the right way round :-)
-Steve
next prev parent reply other threads:[~2015-06-30 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 20:54 Steve Simon
2015-06-30 22:17 ` hiro
2015-06-30 22:29 ` Steve Simon [this message]
2015-06-30 22:47 ` Skip Tavakkolian
2015-07-01 4:58 ` Jeff Sickel
2015-07-01 5:19 ` lucio
2015-07-04 16:10 ` michaelian ennis
2015-07-06 8:30 ` hiro
2015-07-06 12:41 ` Joseph Stewart
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=d81bf2686377e9c66173f7f396cf53ec@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).