From: Bart De Schuymer <bdschuym@pandora.be>
To: aijazbaig1@gmail.com
Cc: Jan Engelhardt <jengelh@medozas.de>,
netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: packet flow - ebtables broute DROP target
Date: Fri, 16 Jul 2010 18:54:57 +0200 [thread overview]
Message-ID: <4C408EE1.8070105@pandora.be> (raw)
In-Reply-To: <1279267539.4086.28.camel@aijazbaig1-desktop>
Aijaz Baig schreef:
> Hello Bart and Jan,
>
> Sorry for the belated reply. Im in India so the time gaps makes it bad.
> Thank you for your great inputs. I would surely consider them now. Thank
> you Jan for letting us know you guys are writing a book on netfilter.
> Lord knows we need it. More and more companies across the globe are
> using linux more and more now. This would be of immense help to
> academicians and professionals alike.
>
> Ive got 2 linux boxes, one virtual and one real. The real one has a eth0
> interface which connects to my LAN. It's vmnet8 interface is behind the
> virtual linux box's eth0 interface i.e. the latter is the former's
> gateway. The virtual box has 3 interfaces eth0, eth1 and eth2. Out of
> which eth0 and eth1 are bridged and enslaved to br0. eth2 connects to
> the same LAN as does my real box's eth0. I have added a static route for
> a PC in my outer LAN to force the traffic to go through vmnet8.
>
> Now when I DROP packets for the target PC in the broute table, the
> problem that I described above happens. I did what was told to be done
> as shown the basic brouter example. But still..zilch..nothing seemed to
> be working.
>
> To be specific, I added a rule:
> ebtables -t broute -A BROUTING -p 0x806 --d$MAC_OF_eth0 -j DROP
> to allow the arp replies to arrive on eth0 and not on br0. But even
> after that it didn't work. Even the packet count for this new rule was
> zero all the time so I guess something was suspicious here.
>
> Could someone, bart maybe, let me know what it means by his quote: "Your
> traffic is probably dropped by the networking code because the
> destination MAC address differs from that of the bridge port."
>
> May be I don't really know ARP works to infer how such a rule would be
> helpful in the first place.
>
>
This is explained at the link I gave you. If something is unclear in my
description on the website, feel free to let me know.
Try it out with the example rules I mention on that site and adapt to
your situation from there. In the future, please explicitly list your
complete test setup, including a dump of the firewall tables.
cheers,
Bart
--
Bart De Schuymer
www.artinalgorithms.be
next prev parent reply other threads:[~2010-07-16 16:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1DB91DF937A4544C81E636468B91C21C06F1EC28@CNSHGSMBS03.ad4.ad.alcatel.com>
2010-07-15 8:08 ` 'HELP ME PLEASE. libnetfilter_queue issue MAI JIN
2010-07-15 13:44 ` Mistick Levi
2010-07-15 14:02 ` packet flow - ebtables broute DROP target Aijaz Baig
2010-07-15 14:34 ` Jan Engelhardt
2010-07-15 19:26 ` Bart De Schuymer
2010-07-16 8:05 ` Aijaz Baig
2010-07-16 16:54 ` Bart De Schuymer [this message]
2010-07-16 17:06 ` Payam Chychi
2010-07-15 19:26 ` 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=4C408EE1.8070105@pandora.be \
--to=bdschuym@pandora.be \
--cc=aijazbaig1@gmail.com \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=netfilter@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).