From: "Eble, Dan" <DanE@aiinet.com>
To: "'bridge@osdl.org'" <bridge@osdl.org>
Subject: Re: [Bridge] Bridge and PACKET-socket
Date: Mon, 2 Feb 2004 11:50:04 -0500 [thread overview]
Message-ID: <AD59566A9D83864F871AE2E52503064001663D5C@aimail.aiinet.priv> (raw)
On Tuesday 13 January 2004 12:41:55 -0800, Bart De Schuymer wrote:
> Reading the man page is indeed confusing for a user, w.r.t. bridge ports.
> I think it would be more logical if all PF_PACKET
> sockets see the frames before the bridge code.
I agree. I just ran into this problem trying to read bridge PDUs from a
daemon listening on a packet socket. I'm glad I found this thread; it saved
me a lot of debugging time.
> How about placing the call to __handle_bridge() right after the second
> list_for_each? If I'm not mistaken the relevant pt_pre->func that would
deal
> with the packet will not have been executed yet, while those PF_PACKET
> functions will already have been called...
Has anyone tested this in the two weeks since it was suggested?
--
Dan Eble <dane@aiinet.com> _____ .
| _ |/|
Applied Innovation Inc. | |_| | | "All Protocols MUST be odd"
http://www.aiinet.com/ |__/|_|_| -- RFC 1661 (PPP)
next reply other threads:[~2004-02-02 16:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 16:50 Eble, Dan [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-05 22:33 [Bridge] Bridge and PACKET-socket Luke Gorrie
2004-01-05 23:13 ` Bart De Schuymer
2004-01-05 23:50 ` Luke Gorrie
2004-01-08 16:34 ` Jason Lunz
2004-01-12 21:02 ` Luke Gorrie
2004-01-12 21:47 ` Bart De Schuymer
2004-01-12 22:14 ` Luke Gorrie
2004-01-13 19:35 ` Bart De Schuymer
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=AD59566A9D83864F871AE2E52503064001663D5C@aimail.aiinet.priv \
--to=dane@aiinet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.