Re: Any issues with packet updates?
Scott MacKay <scottmackay-/[email protected]>
| Newsgroups | gmane.linux.network.bridge.ebtables.devel |
|---|---|
| Message-ID | <[email protected]> |
--- Bart De Schuymer <[email protected]> wrote: > You can find out the bridge port the packet was > received on in the FORWARD > chain. Your queue handler receives the skb, check > out the nf_bridge member of > the struct sk_buff. I actually went and tried shifting the QUEUE entries to INPUT & OUTPUT instead of PREROUTING and POSTROUTING, since my current tests are on the 2 boxes themselves and not the hosts behind them. That actually worked generating the proper results. Why this worked and not PRE/POST routing is beyond me...thanks! The bigger problem to detect is thru traffic, tho. I believe I get a ipq_packet_msg_t entry, not a sk_buff up thru to the userspace iptables QUEUE target. Unless I am looking at the wrong header, I do not see how to get the sk_buff which would have the physindev/physoutdev fields. Is there a separate function call to get the sk_buff (and thus the nf_bridge field)? -Scott __________________________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo http://search.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf