From: "Tyler J. Wagner" <tyler@tolaris.com>
To: Pandu Poluan <pandu@poluan.info>
Cc: Kumar Swamy <kswamy@barracuda.com>,
"netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: iptables and virtual NIC
Date: Thu, 28 Jul 2011 17:28:39 +0200 [thread overview]
Message-ID: <4E318027.8010308@tolaris.com> (raw)
In-Reply-To: <CAA2qdGVekbZP=x0oUspJY6-ewqvgGB7OLcbZ0Om7LMmVz1UBRg@mail.gmail.com>
On 2011-07-28 14:00, Pandu Poluan wrote:
> How does the routing work? I.e., when does a packet exits through eth0
> or eth0:1 or eth0:2?
Pandu,
eth0 and eth0:1 are the same interface. The :1 suffix is just an alias
associated with a secondary IP address. There is no difference internally.
If you want to behave differently based on different aliases, you must
define rules by IP.
Regards,
Tyler
--
"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders, give
orders, cooperate, act alone, solve equations, analyze a new problem,
pitch manure, program a computer, cook a tasty meal, fight efficiently,
die gallantly. Specialization is for insects."
-- Lazarus Long, "Time Enough for Love", by Robert A. Heinlein
next prev parent reply other threads:[~2011-07-28 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 10:05 iptables and virtual NIC Kumar Swamy
2011-07-28 11:53 ` Jan Engelhardt
2011-07-28 12:00 ` Pandu Poluan
2011-07-28 15:21 ` Jan Engelhardt
2011-07-28 15:28 ` Tyler J. Wagner [this message]
2011-07-28 15:04 ` Michal Soltys
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=4E318027.8010308@tolaris.com \
--to=tyler@tolaris.com \
--cc=kswamy@barracuda.com \
--cc=netfilter@vger.kernel.org \
--cc=pandu@poluan.info \
/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