From: Stephen Hemminger <shemminger@osdl.org>
To: Louis Croisez <louis.croisez@gmail.com>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Information needed about bridge c code
Date: Thu, 9 Feb 2006 09:18:02 -0800 [thread overview]
Message-ID: <20060209091802.2cb9aa1d@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <34d8b2fe0602010131n884f73bt@mail.gmail.com>
On Wed, 1 Feb 2006 10:31:07 +0100
Louis Croisez <louis.croisez@gmail.com> wrote:
> Hello,
> i need to write a little personal patch in the bridge code.
> For this patch, i need to know the original src and dst mac addresses
> of the packet incoming to the bridge. As i work on a brouter (some
> packets are bridged, some are routed based on ebtable rules), packets
> that are routed have their mac addresses modified by the IP stack).
At start of br_handle_frame, dst mac address in skb is as received on
wire. Call sequence is:
netif_receive_skb
handle_bridge
br_handle_frame
The skb on the pre-routing chain is actually after brouting but before
going through bridge forwarding.
> I put a software probe in br_input.c::br_handle_frame( ), but there,
> the dst mac address is already replaced by the bridge local mac
> address.
> My question is: where must i put the probe to get the original src and
> dst mac addresses? At the driver level? In the bridge, but where?
>
> Thx in advance.
> PS: please CC to louis.croisezATgmail.com, because i am receiving the
> digest once per day.
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
--
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger
prev parent reply other threads:[~2006-02-09 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 9:31 [Bridge] Information needed about bridge c code Louis Croisez
2006-02-09 17:18 ` Stephen Hemminger [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=20060209091802.2cb9aa1d@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=louis.croisez@gmail.com \
/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