From: "Samuel Díaz García" <samueldg@arcoscom.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] setportprio problem with bridge-utils 1.0.6
Date: Wed, 31 May 2006 23:02:14 +0200 [thread overview]
Message-ID: <447E0456.10609@arcoscom.com> (raw)
In-Reply-To: <20060531091022.12361f66@localhost.localdomain>
Thanks Stepen, again, and sorry for my english, perhaps is this the
problem too: my english.
I want to set port prio, to values as 1, 2, 3, 4, etc.. (little values),
my problem is that when I run:
brctl setportprio br0 eth1 3
That "3" goes to "port cost" no goes into "port priority", that is my
problem.
Any help more?
Stephen Hemminger escribió:
> On Wed, 31 May 2006 13:01:56 +0200
> Samuel Díaz García <samueldg@arcoscom.com> wrote:
>
>> Thanks Stephen.
>>
>> The problem is I want to set the port prio, not the cost. The cost is
>> working (at least brctl showstp br0 shows fine, gg).
>>
>> Would work with ..../port_prio too?
>
> You know that port_prio is limited to 6 bits now that bridge can have up
> to 1024 ports.
>
--
Samuel Díaz García
Director Gerente
ArcosCom Wireless, S.L.L.
CIF: B11828068
c/ Romero Gago, 19
Arcos de la Frontera
11630 - Cadiz
http://www.arcoscom.com
mailto:samueldg@arcoscom.com
msn: samueldg@arcoscom.com
Móvil: 651 93 72 48
Tlfn.: 956 70 13 15
Fax: 956 70 34 83
next prev parent reply other threads:[~2006-05-31 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 21:46 [Bridge] setportprio problem with bridge-utils 1.0.6 Samuel Díaz García
2006-05-30 23:21 ` Stephen Hemminger
[not found] ` <447D77A4.5050205@arcoscom.com>
[not found] ` <20060531091022.12361f66@localhost.localdomain>
2006-05-31 21:02 ` Samuel Díaz García [this message]
2006-05-31 21:33 ` [Bridge] [PATCH] Fix bug where changing port priority changed path cost instead Stephen Hemminger
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=447E0456.10609@arcoscom.com \
--to=samueldg@arcoscom.com \
--cc=bridge@lists.osdl.org \
--cc=shemminger@osdl.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