[smokeping-users] smoketrace for dummies - oh so close

[jsg at internode.on.net]

Thanks tobi ...

That's done the trick, and now everything is up and running properly.  
Much appreciated.

There are a couple of things which I've wondered about  in my short 
amount of testing though.

None of them are really major, but I hope that you might find the 
feedback useful. ;)

1. If you use the filter search to find a host, then the * link for the 
traceroute doesn't seem appear.

2. What needs to be edited to change the default number of probes that 
the script sends, and can you lock it to a specific amount?

IE - I'd prefer not to have people be able to launch a ridiculously 
large number of pings.

3. I've seen some scripts that  have a popup window launch centered in 
the screen.  Would that be possible/easy to implement here?  It just 
looks much nicer IMHO.


Tobias Oetiker wrote:
> Hi Jsg,
>
> Traceroute should be setuid root. The problem is that there were
> security problems with traceroute (in 2002) that allowed a local
> user to cause problems (?) by executing it setuid. So today, in
> some distros the setuid bit is gone. Unfortunately without the
> setuid bit, traceroute can not work properly for normal users. My
> understanding is that the problems have been fixed, but the setuid
> bit is gone anyway ... My suggestion is to run
>
>  chown root:root /usr/bin/traceroute
>  chmod u+s /usr/bin/traceroute
>
> that will make things work for you.
>
> Maybe there are more knowledgable people on the list who can
> suggest  other solutions.
>
> cheers
> tobi
>
>
>
>   
>> Hi guys,
>>
>> I've upgraded to the new smoketrace 2.4.1, and following Tobi's improved
>>    documentation, I've ALMOST got it up and running.  There's just
>> [hopefully] one small glitch that still remains.
>>
>> Here's my problem ...
>>
>> tr.html loads/displays properly, but when it tries to actually execute a
>> traceroute, it throws up the error message "The specific type of
>> tracerouting is allowed for superuser only."
>>
>> Okay ... so obviously I need to change some permissions - that's simple
>> enough - but what I'm not sure about is exactly which file(s) in
>> particular actually need to be given superuser rights?
>>
>> Much appreciated ...
>>
>> _______________________________________________
>> smokeping-users mailing list
>> smokeping-users at lists.oetiker.ch
>> https://lists.oetiker.ch/cgi-bin/listinfo/smokeping-users
>>
>>
>>     
>
>