[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200125162357.GE18311@lunn.ch>
Date: Sat, 25 Jan 2020 17:23:57 +0100
From: Andrew Lunn <andrew@...n.ch>
To: "Allan W. Nielsen" <allan.nielsen@...rochip.com>
Cc: Vinicius Costa Gomes <vinicius.gomes@...el.com>,
Horatiu Vultur <horatiu.vultur@...rochip.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
bridge@...ts.linux-foundation.org, jiri@...nulli.us,
ivecera@...hat.com, davem@...emloft.net, roopa@...ulusnetworks.com,
nikolay@...ulusnetworks.com, anirudh.venkataramanan@...el.com,
olteanv@...il.com, jeffrey.t.kirsher@...el.com,
UNGLinuxDriver@...rochip.com
Subject: Re: [RFC net-next v3 00/10] net: bridge: mrp: Add support for Media
Redundancy Protocol (MRP)
> Lets say that the link between H1 and H2 goes down:
>
> +------------------------------------------+
> | |
> +-->|H1|<--- / --->|H2|<---------->|H3|<--+
> eth0 eth1 eth0 eth1 eth0 eth1
>
> H1 will now observe that the test packets it sends on eth1, is not
> received in eth0, meaninf that the ring is open
Hi Allan
Is H1 the only device sending test packets? It is assumed that H2 and
H3 will forward them? Or does each device send test packets, and when
it stops hearing these packets from a neighbour, it assumes the link
is open?
Andrew
Powered by blists - more mailing lists