-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I'm new to STP and RSTP. I'm however trying to implement a new bridge
protocol. I'm trying the RSTP code available at :
git clone git://git.kernel.org/pub/scm/linux/kernel/git/shemminger/rstp.git
It compiles fine. However, it segfaults using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Hemminger a écrit :
| That said, we really need to get the STP updated to RSTP. There are
currently
| four options:
I agree since RSTP is now part of 802.1D-2004 and is backward compatible
with STP (with some limitations of course).
|
| 1) E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello there,
I've been studying routing protocol during my studies, like OSPF, BGP,
EGP, IGP, RIP, OLSR.. All those protocols are based on the routing
table concept and each of them has its own way to compute routing table
which is then used by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there,
I'm working on very strange stuff using linux kernel bridge. Anyway, I
have a quick question.
Let's say I have 2 linux machines. Each has one bridge with several
interfaces. One interface of the first bridge (say eth0) is connected to
one i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Hemminger a écrit :
| Rather than an ask a detailed question like "what will happen if I
misconfigure
| the system, then change the behaviour", instead start a discussion about
| your requirements. Like "I need to forward only frames from some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malcolm Scott a écrit :
| At 22:06 today, Benoit PAPILLAULT wrote:
|
|> I am in a very preliminary phase, trying to learn how to implement
|> routing and bridging under Linux. In order for the routing protocol to
|> have proper topology
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stephen Hemminger a écrit :
| On Fri, 15 Aug 2008 21:17:27 +0100 (BST)
| Malcolm Scott <[EMAIL PROTECTED]> wrote:
|
|> At 22:06 today, Benoit PAPILLAULT wrote:
|>
|>> I am in a very preliminary phase, trying to learn how to impleme
