From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: netfilter@lists.netfilter.org
Subject: Re: routing within same nic card
Date: Tue, 31 May 2005 01:59:52 -0500 [thread overview]
Message-ID: <429C0B68.8090101@riverviewtech.net> (raw)
In-Reply-To: <00e801c565ad$29c91a00$d40aa8c0@winxp>
Beyond a little bit of house keeping of duplicate rules and more open allows (destination or source only matches) I think what you have would work. I do not see any thing that would keep your traffic from flowing like you want though you might find some traffic flow that you do not want.
Grant. . . .
prev parent reply other threads:[~2005-05-31 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 5:20 routing within same nic card Wennie V. Lagmay
2005-05-31 5:49 ` Taylor, Grant
2005-05-31 6:10 ` Wennie V. Lagmay
2005-05-31 6:31 ` Taylor, Grant
2005-05-31 6:51 ` Wennie V. Lagmay
2005-05-31 6:59 ` Taylor, Grant [this message]
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=429C0B68.8090101@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@lists.netfilter.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