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
After a bit of a search, it seemed like there was nothing out there that could multiplex traceroutes and let us do them in parallel, but on further reflection it feels like this is something fping could be bent into doing somewhat. We've already got the ability to specify TTL, and the parallel RR of responses is do-able. New record structures would need to be made, and output formats decided on (prefix each line with ultimate destination and output as received? Or wait until completed and output blocks? etc...), but nothing too horribly insurmountable.
This would come in very handy for our monitoring system, which uses fping for massively parallel pinging, but ends up doing serial traceroutes on things that are unreachable, which obviously slows things down.
I'd be willing to help work on a patch, but I wanted to put this RFE out there first :)
The text was updated successfully, but these errors were encountered:
After a bit of a search, it seemed like there was nothing out there that could multiplex traceroutes and let us do them in parallel, but on further reflection it feels like this is something fping could be bent into doing somewhat. We've already got the ability to specify TTL, and the parallel RR of responses is do-able. New record structures would need to be made, and output formats decided on (prefix each line with ultimate destination and output as received? Or wait until completed and output blocks? etc...), but nothing too horribly insurmountable.
This would come in very handy for our monitoring system, which uses fping for massively parallel pinging, but ends up doing serial traceroutes on things that are unreachable, which obviously slows things down.
I'd be willing to help work on a patch, but I wanted to put this RFE out there first :)
The text was updated successfully, but these errors were encountered: