From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: ebtables mac update
Date: Tue, 29 Jun 2010 09:57:31 -0500 [thread overview]
Message-ID: <4C2A09DB.6030205@riverviewtech.net> (raw)
In-Reply-To: <1277821770.4006.33.camel@casper.meteor.dp.ua>
On 06/29/10 09:29, Покотиленко Костик wrote:
> Linux box runs some services and have 3 interfaces, 2 of them are
> bridged to br0 and one is left for separate local segment. So it is a
> router between br0 and eth2 and a bridge between eth0, eth1.
Will you please clarify what interface the Zyxel bridge is connected to?
(I'm guessing that it's connected to either eth0 or eth1, but I'd
like some clarification.)
What is connected to the other two interfaces?
> This is brctl showmacs, right?
I don't know the command off the top of my head, but I know there is a
command to have the bridge show what MAC addresses are associated with
what bridge ports.
> So, this is exactly the same logic that switches use, right?
Should be, yes.
> Can you confirm that if MAC (frame with source MAC) pops up on port
> different from the one it was seen previous time then the port for
> that MAC get updated?
Should be, yes.
> What then "brctl setageing" for?
That should set the aging / expire timer for MAC addresses that have not
been seen in a while. (How long the MAC has to be quite before it is
flooded again.)
> It may happen that rebooting the modems brings port link down and the
> bridge may clear the MAC-port table on that port. This is similar to
> what Zyxel support told me.
Agreed. See my previous reply about a way to test this.
> In my case on moved box I'm unable to make connections or even ping.
This is contrary to how every Linux bridge that I have used ever
behaved. I'm thinking that the Zyxel is at least part of the problem.
That being said, it is very unlikely but there could be some sort of
weird interaction between the Zyxel and Linux bridging that combined is
causing a problem.
> Besides that it is a server, iptables is used to restrict access for
> separate local segment at eth2 (allow access to Internet and not to
> local net). Ebtables is empty now, but I wanted to be able to filter
> bridge traffic if that matters someday.
Remember that it is possible for IPTables to filter bridged traffic.
(It depends if an option is enabled in the kernel.) So IPTables could
be interfering with out you knowing it.
Will you please provide the output of "iptables-save" (sanitized if needed).
Grant. . . .
next prev parent reply other threads:[~2010-06-29 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 10:43 ebtables mac update Покотиленко Костик
2010-06-29 12:36 ` Pascal Hambourg
2010-06-29 14:29 ` Покотиленко Костик
2010-06-29 14:57 ` Grant Taylor [this message]
2010-06-30 9:24 ` Покотиленко Костик
2010-06-30 15:39 ` Pascal Hambourg
2010-06-30 23:38 ` Покотиленко Костик
2010-06-30 23:54 ` Grant Taylor
2010-07-01 9:08 ` Покотиленко Костик
2010-07-01 16:10 ` Grant Taylor
2010-07-01 17:00 ` Покотиленко Костик
2010-07-01 17:13 ` Покотиленко Костик
2010-07-01 9:59 ` Pascal Hambourg
2010-07-01 10:11 ` Покотиленко Костик
2010-07-01 10:49 ` Pascal Hambourg
2010-07-01 11:05 ` Покотиленко Костик
2010-06-29 14:45 ` Grant Taylor
2010-06-29 17:03 ` Jan Engelhardt
2010-06-29 19:02 ` Grant Taylor
2010-06-30 9:09 ` Покотиленко Костик
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=4C2A09DB.6030205@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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).