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
There doesn't seem to be a good way to log the remote address that a path probe packet is being sent to / received from. This would be very helpful for debugging connection migration.
The text was updated successfully, but these errors were encountered:
Not entirely sure, but isn't this covered by using the path_assigned event and logging the remote address in there?
I know that's somewhat more tedious probably than logging it directly together with the probe, but that's the general approach we've taken to path stuff after tons of discussion in the past. If the migration succeeds, you'd be using that PathID anyway.
Proposal: use existing path_assigned for this use case and close this issue without action.
There doesn't seem to be a good way to log the remote address that a path probe packet is being sent to / received from. This would be very helpful for debugging connection migration.
The text was updated successfully, but these errors were encountered: