You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When faucet switches are configured in stacking mode, a broadcast-in packet on a switch port will eventually get echoed out on the same port. This happens because the broadcast is always first sent all the way up to the root of the stacking tree, and then sent back down -- and then when it reaches the leaf node switch it no longer has the context of which input port it came from. This is different than in "normal" switch mode because in that case packets are broadcast locally at the leaf node first, implicitly sending it up the hierarchy, but they never come back!
Not sure how significance this is, but it's a "difference" so I thought I'd flag it.
The text was updated successfully, but these errors were encountered:
It is as you say - I should have documented this (in ensuring no loops
between switches). It is not ideal. On my list for cleaning up. Thank you
for documentating.
On Wed, Jan 24, 2018, 16:09 Trevor ***@***.***> wrote:
When faucet switches are configured in stacking mode, a broadcast-in
packet on a switch port will eventually get echoed out on the same port.
This happens because the broadcast is always first sent all the way up to
the root of the stacking tree, and then sent back down -- and then when it
reaches the leaf node switch it no longer has the context of which input
port it came from. This is different than in "normal" switch mode because
in that case packets are broadcast locally at the leaf node first,
implicitly sending it up the hierarchy, but they never come back!
Not sure how significance this is, but it's a "difference" so I thought
I'd flag it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1564>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEgZ14MMhr7z8QAgZ9WbgRjL-oYs4kF8ks5tNp7tgaJpZM4Rqp-D>
.
anarkiwi
changed the title
stacked broadcast gets echoed out input port
stacked broadcast gets echoed out input port for stacks with max hops from root > 2
Sep 26, 2018
This is addressed/tested in #3117 - ensure that when an external switch is connected to a FAUCET stack, that the switch is connected on a FAUCET port with loop_protect_external: True (necessary for any size FAUCET stack to prevent a loop appearing to the non-FAUCET network).
When faucet switches are configured in stacking mode, a broadcast-in packet on a switch port will eventually get echoed out on the same port. This happens because the broadcast is always first sent all the way up to the root of the stacking tree, and then sent back down -- and then when it reaches the leaf node switch it no longer has the context of which input port it came from. This is different than in "normal" switch mode because in that case packets are broadcast locally at the leaf node first, implicitly sending it up the hierarchy, but they never come back!
Not sure how significance this is, but it's a "difference" so I thought I'd flag it.
The text was updated successfully, but these errors were encountered: