Hi,
I merged your patch in:
http://nbd.name/gitweb.cgi?p=luci2/netifd.git;a=commitdiff;h=2008ae9a80fb82b0018fd510043c291b58e7cc46
... and set the default prio to 0x7FFF in:
http://nbd.name/gitweb.cgi?p=luci2/netifd.git;a=commitdiff;h=0f0fa4f1c8cb4f793c31edd1420483e9e325
It will appear in O
Hi again,
On 02/04/2013 08:32 PM, Niels Boehm wrote:
>
> On 02/04/2013 08:13 PM, Jo-Philipp Wich wrote:
>> I wonder if it would make sense to set a lower priority by default (while
>> still keeping this option to allow overriding again).
>
> I'm not sure, I haven't really thought about that.
>
Hello,
On 02/04/2013 08:13 PM, Jo-Philipp Wich wrote:
> I wonder if it would make sense to set a lower priority by default (while
> still keeping this option to allow overriding again).
I'm not sure, I haven't really thought about that.
I guess one has to consider several points when making the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
just a random thought...
I wonder if it would make sense to set a lower priority by default
(while still keeping this option to allow overriding again).
~ Jow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG
[netifd] add bridge priority option
Using the bridge priority (lower numbers are higher in the
hierarchy), one can ensure that the router is chosen as root
bridge in a setup with spanning tree protocol.
For instance, one can set the priority of network lan to 32767,
causing the router to win over
