From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] two nics 8139
Date: Thu, 13 Mar 2014 12:11:29 -0400 [thread overview]
Message-ID: <4221cdfdc2e3b6bcea8cae72323bbaa8@ladd.quanstro.net> (raw)
In-Reply-To: <5321D837.2020806@mail.com>
> ok, thanks. If the goal is to manage two separate networks, one local
> and the other for remote/restricted access only, its better to have 2
> stacks or 2 nics under the same stack ?
i don't know about "better", but it's certainly easier to think about
two seperate stacks. one can be certain (absent bridging) that the
stacks don't interact, and the services won't leak between them.
- erik
next prev parent reply other threads:[~2014-03-13 16:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 15:24 Adriano Verardo
2014-03-13 15:44 ` Skip Tavakkolian
2014-03-13 15:52 ` Charles Forsyth
2014-03-13 16:09 ` Adriano Verardo
2014-03-13 16:11 ` erik quanstrom [this message]
2014-03-13 16:20 ` Adriano Verardo
2014-03-13 16:26 ` Charles Forsyth
2014-03-13 16:30 ` Adriano Verardo
2014-03-13 15:56 ` Adriano Verardo
2014-03-13 18:52 ` Bakul Shah
2014-03-13 18:58 ` erik quanstrom
2014-03-13 18:58 ` Charles Forsyth
2014-03-13 21:13 ` Skip Tavakkolian
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=4221cdfdc2e3b6bcea8cae72323bbaa8@ladd.quanstro.net \
--to=quanstro@quanstro.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).