[smokeping-users] Smoketrace using tcptraceroute?
young_einstein at internode.on.net
Tue Jun 17 10:34:37 CEST 2008
David Tomic wrote:
> Hi Tobi [or anyone else who might know] ...
> I'm just curious how much effort would be involved in getting
> Smoketrace to run using tcptraceroute, instead of the 'normal'
> traceroute command?
> Is it something that would be relatively easy to implement, or would
> it be a big hassle to do?
> --David Tomic
FWIW ... I've just tried having a look at this myself, and it seems
pretty trivial to get it running tcptraceroute [with all the right
parameters] *BUT* it runs into trouble on the last hop where
tcptraceroute also includes the [open/closed] port information in its
output as well.
EG - Tracing the path to internode.on.net (126.96.36.199) on TCP port 80
(www), 30 hops max
1 lns1.mel6.internode.on.net (188.8.131.52) 15.632 ms
2 gi1-3.cor1.mel6.internode.on.net (184.108.40.206) 24.406 ms
3 gi5-2.cor3.mel4.internode.on.net (220.127.116.11) 24.678 ms
4 pos3-0.bdr2.adl2.internode.on.net (18.104.22.168) 23.701 ms
5 po2.cor3.adl2.internode.on.net (22.214.171.124) 22.175 ms
6 corp.internode.on.net (126.96.36.199) [open] 22.669 ms
It seems all that's really standing in my way is the need to strip out
[or otherwise deal with] that [open/closed] output, and everything would
Unfortunately being someone who really doesn't know much at all about
coding, that's really beyond my ability to deal with myself.
For someone who actually knows what they're doing though, I imagine that
really shouldn't be too hard for them to work out would it?
More information about the smokeping-users