From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter@vger.kernel.org,
"Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
Subject: Re: More ethernet port same ip address
Date: Sat, 19 Jul 2008 18:05:00 +0200 [thread overview]
Message-ID: <488210AC.9030102@unipex.it> (raw)
In-Reply-To: <alpine.LNX.1.10.0807191739560.21244@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
>> Ok. Thanks for the simple, but complete explain. But where to say
>> "go out through the right one?"
>
> The fact is, you do not know in advance which is the right one.
So there is no solution with the "marking into PREROUTING" technique?
Into my environ a packet that come from an interface MUST go out through
that one.
>>> And depending on the situation you might also need to enforce
>>> routing at the bridge border so as to not open security holes.
>> Have you some more words about this? Where can I found problems?
>> How to modify routing?
>
> ebtables -t broute -P BROUTING DROP
>
> which will force all packets being routed.
I'll try it soon.
But in this case, why the kernel doesn't "lost" the package that ebtables
wants to DROP? Or the kernel starts to see which is the first hole where
the packet can go inside and leave it there?
Seem a very contorted thinking to me...
Thanks,
MIchele
next prev parent reply other threads:[~2008-07-19 16:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 7:34 More ethernet port same ip address Michele Petrazzo - Unipex srl
2008-07-19 8:18 ` Bernhard Bock
2008-07-19 13:46 ` Michele Petrazzo - Unipex srl
2008-07-19 14:01 ` Leonardo Rodrigues Magalhães
2008-07-19 14:13 ` Jan Engelhardt
2008-07-19 15:14 ` Michele Petrazzo - Unipex srl
2008-07-19 15:42 ` Jan Engelhardt
2008-07-19 16:05 ` Michele Petrazzo - Unipex srl [this message]
2008-07-19 16:13 ` Jan Engelhardt
2008-07-19 16:17 ` Leonardo Rodrigues Magalhães
2008-07-19 16:34 ` Jan Engelhardt
2008-07-19 16:45 ` Leonardo Rodrigues Magalhães
2008-07-19 15:11 ` Michele Petrazzo - Unipex srl
2008-07-20 23:41 ` Grant Taylor
2008-07-21 7:00 ` Anatoly Muliarski
2008-07-21 14:08 ` Grant Taylor
2008-07-21 18:11 ` Michele Petrazzo - Unipex srl
2008-07-21 19:46 ` Grant Taylor
2008-07-22 13:03 ` Anatoly Muliarski
2008-07-22 15:06 ` Grant Taylor
2008-07-22 15:20 ` Jan Engelhardt
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=488210AC.9030102@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=jengelh@medozas.de \
--cc=leolistas@solutti.com.br \
--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