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
It would be useful if showpaths were able to check the health of printed paths, for users to be able to differentiate between healthy, revoked, unknown, etc. This mode of operation could be enabled by specifying a flag, e.g., -p.
The text was updated successfully, but these errors were encountered:
The original idea was to use SVC_BR (see #1801) to check the health of the path. However, I think it muddles the layering of the stack.
SVC_BR implies that the packet reaches BR application but it in fact does not. It only reaches the dispatcher which in turn generates the reply.
The alternative would be to use SVC_NONE instead, with the semantics "don't even try to dispatch to a specific service and reply straight away".
That of course, would require dispatcher to live on all nodes in the network, including the BRs. But that may be a reasonable requirement in the first place: If the dispatcher is, in fact, an ersatz kernel, then running without a dispatcher is like running without a kernel.
After more discussion with Sergio and Sam, let's do it in the following way: Showpath will send a packet with SVC_NONE. The border router at the destination AS will fail to forward the packet and will send an SCMP error back to showpath. Showpath will use the error as a confirmation that the path is alive.
It would be useful if
showpaths
were able to check the health of printed paths, for users to be able to differentiate between healthy, revoked, unknown, etc. This mode of operation could be enabled by specifying a flag, e.g.,-p
.The text was updated successfully, but these errors were encountered: