A destination behind a lagg on the XGS 136: refused, and in hardware now; and a port's connections taken back when its link goes, 2026-11-15
The XGS 136's driver resolved a connection's original direction - toward its destination - with no port to fall
back on, so a destination whose route names a lagg was refused, and the host forwarded the whole connection; the
reply direction, to an opener behind a lagg, already took the port its own frames arrive on. Since the change the
original direction takes the port the destination's own frames arrive on, for a lagg's route only and only when
that port is one of the lagg's members (npuep_nhop_hint_fits), as the XGS 3300's driver does. A refused next hop
is counted (flow.make_nonhop) and named in flow.accelerate's answer.
The whole page, with how it was taken and what it does not show: A destination behind a lagg on the XGS 136: refused, and in hardware now; and a port's connections taken back when its link goes, 2026-11-15.
The discussion of this page is held in the project's GitHub Discussions. Showing it here loads giscus from giscus.app and GitHub, and writing in it needs a GitHub account - what that means.