From: Aijaz Baig <aijazbaig1@gmail.com>
To: bridge@osdl.org
Subject: Re: [Bridge] About local delivery of bridged packets
Date: Tue, 12 Oct 2010 13:01:08 +0000 (UTC) [thread overview]
Message-ID: <loom.20101012T145743-585@post.gmane.org> (raw)
In-Reply-To: loom.20101011T131053-288@post.gmane.org
Aijaz Baig <aijazbaig1 <at> gmail.com> writes:
>
> Hello,
>
> I am trying to understand how does the bridging code determine if the packet
is
> to be delivered locally or is it to be forwarded. Before being delivered
> locally, I mean the packet is to be delivered either to br0 or to a non
enslaved
> interface. If I am wrong here, please do correct me..................
Hello,
Heres answering my own question partially. Since the bridge which is after all a
virtual interface takes one of the L2 addresses of its interfaces (is it the
first real interface which is enslaved?), any packet which is destined with this
L2 dest address in its eth header, will be considered locally destined.
This simple fact solves my issue.
Regards,
Aijaz
next prev parent reply other threads:[~2010-10-12 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 13:29 [Bridge] About local delivery of bridged packets Aijaz Baig
2010-10-12 13:01 ` Aijaz Baig [this message]
2010-10-12 16:37 ` Stephen Hemminger
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=loom.20101012T145743-585@post.gmane.org \
--to=aijazbaig1@gmail.com \
--cc=bridge@osdl.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