From: Anatoly Muliarski <x86ever@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: ebtables & VLAN redirect
Date: Mon, 28 Jun 2010 20:33:13 +0300 [thread overview]
Message-ID: <AANLkTikeVKxFv4jTp2vLTh80BOQW1nAQxmCc8M7EsPJ1@mail.gmail.com> (raw)
In-Reply-To: <4C2805A3.4070801@riverviewtech.net>
2010/6/28 Grant Taylor <gtaylor@riverviewtech.net>:
> Will you please provide an example of what redirection you are talking
> about?
Unfortunately, I have a set of tasks to cope with.
1. UDP broadcast relaying for specific ports from specific VLANs - on
second thought I've decided to use udp-broadcast-relay as it's the
simplest way.
2. Multicast feeding and IGMP exchange snooping - I tried to avoid
using igmpproxy but probably I should use it.
3. Mirroring specific sessions to VLAN 9 - and I can postpone this
task for the future.
>
> Remember that you can set a default policy of DROP in your BROUTING chain to
> cause the packets to be routed like normal. So any frames that you don't
> want bridged will simply be routed like normal. There by only bridging the
> frames that you want to.
Yes, I knew about it - very nice feature.
>> That would work but I need to redirect traffic that is not destined to
>> VLAN 9 and ARP-proxy trick does not work for this case.
>
> So you are going to have to intercept the traffic and alter the destination
> MAC (and possibly IP) address(es)?
For mirroring purpose I have to alter destination MAC and I can do
that in POSTROUTING chain.
Other tasks use broadcast/multicast destination addresses so I do not
need to alter them.
>
> I believe that EBTables can do that. If not, you can probably have IPTables
> work on bridged frames, and I know that it will do that.
>
> I'm still not sure that you can't do what you want to do with EBTables and /
> or IPTables.
>
> Remember that EBTables will learn where MAC addresses are and won't flood
> frames out (go in to dumb hub mode).
>
> I don't think you will be bridging too many packets. (That is unless I
> really misunderstand what you are wanting to do.)
Bridging is a good idea, but its current implementation lacks some
features important to me - as impossibility to limit traffic
directions between bridge devices and the fact that a network device
can belong to one bridge only.
>
> Can you provide an example (sanitized if need be) of what you are trying to
> do? Including (hypothetical) source and destination MAC and IP addresses on
> either side of the bridge?
In two words :). All user VLANs(eth1.100-eth1.200) have IP belonging
to one subnet( but sometimes to other ) and they can communicate each
other by using proxy-arp trick under control of the router. And now I
need to extend capabilities of this communication as I stated above.
Owing to talking with you and thinking on the problems I understand my
tasks clearer.
Grant, thank you for your support.
--
Best regards
Anatoly Muliarski
next prev parent reply other threads:[~2010-06-28 17:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 12:43 ebtables & VLAN redirect Anatoly Muliarski
2010-06-26 16:41 ` Grant Taylor
2010-06-27 6:04 ` Anatoly Muliarski
2010-06-28 2:14 ` Grant Taylor
2010-06-28 17:33 ` Anatoly Muliarski [this message]
2010-06-28 20:45 ` Grant Taylor
2010-06-29 18:15 ` Anatoly Muliarski
2010-06-29 19:29 ` Grant Taylor
2010-06-29 19:31 ` Grant Taylor
2010-06-30 3:20 ` /dev/rob0
2010-06-30 3:33 ` Grant Taylor
2010-06-30 20:54 ` Anatoly Muliarski
2010-06-30 21:09 ` Grant Taylor
2010-06-30 21:21 ` Grant Taylor
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=AANLkTikeVKxFv4jTp2vLTh80BOQW1nAQxmCc8M7EsPJ1@mail.gmail.com \
--to=x86ever@gmail.com \
--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).