From: "Nicolas de Pesloüan" <nicolas.2p.debian@free.fr>
To: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Discrepancy in setageing
Date: Wed, 23 Jun 2010 22:32:16 +0200 [thread overview]
Message-ID: <4C226F50.4020307@free.fr> (raw)
In-Reply-To: <4C223084.4080101@ll.mit.edu>
On 06/23/2010 18:04, Jeff Mitchell wrote:
> The documentation for Bridge at
> http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge
> says the following of setageing:
>
> ====
>
> The aging time is the number of seconds a MAC address will be
> kept in the forwarding database after having received a packet
> from this MAC address.
> The entries in the forwarding database are periodically timed out
> to ensure they won't stay around forever.
> Normally there should be no need to modify this parameter,
> but it can be changed with (time is in seconds).
>
> # brctl setageing bridgename time
>
> Setting ageing time to zero makes all entries permanent.
>
> ====
>
> However, according to my testing, this parameter actually turns MAC
> learning off; setting it to zero simply means that entries are never
> added to the table.
Having a quick look at the code, I cannot find a special test for the value "0" for ageing_time nor
ageing_timer. So I assume that learned macs expire right after they are learned, hence your feeling
that mac learning is off.
Can someone double check my code revue, so we decide whether to fix the documentation or not ?
> Searching around the web reveals people with similar experiences.
>
> Is the documentation incorrect, or am I missing something?
>
> Thanks,
> Jeff
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
>
prev parent reply other threads:[~2010-06-23 20:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 16:04 [Bridge] Discrepancy in setageing Jeff Mitchell
2010-06-23 20:32 ` Nicolas de Pesloüan [this message]
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=4C226F50.4020307@free.fr \
--to=nicolas.2p.debian@free.fr \
--cc=bridge@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.