Ping / Trace route in REBOL.
[1/2] from: james::mustard::co::nz at: 15-Nov-2002 14:25
I was hunting around the net today and couldn't sem to find any examples of
a ping tool for rebol - is this a 'missing feature' like someone quoted in
2001 that was left out on purpose? Or is the ping behaviour as specified in
RFC-1574, RFC-1575(draft) possible to create through using the existing port
object?
I was originally intending to write a 1 liner in rebol to do a mass scan on
the local network to detect all alive pc's (sometimes when we upgrade
existing network installations its useful to be able to quickly detect which
address are free - most IT depts we clean up after don't record these or use
DHCP servers.)
If it is possible does anyone have some sample code to point me in the right
direction?
Thanks :)
James.
[2/2] from: sunandadh:aol at: 15-Nov-2002 4:24
James:
> I was hunting around the net today and couldn't sem to find any examples of
> a ping tool for rebol - is this a 'missing feature' like someone quoted in
> 2001 that was left out on purpose?
A similar question was asked by in August -- search the archives for subject
ping
for the whole thread. A couple of quick summaries:
<petr>
Forget ping - we were said it requires root access on Unix, so it is not
in-there. Many ppl requested it. I thought that Rebol could check for rights
somehow, but I can't know Rebol internals of course.
Or just buy /Pro version and use shell access to call it.
</petr>
<gabrielle>
The ICMP protocol is not a user protocol, so REBOL does not handle it; if
you want more detailed reasons, or just want to complain about it, please
contact RT.
Both TCP and UDP provide standard echo ports. That service is
usually disabled on most servers (for obvious reasons), but
servers will have IMP echo disabled too in most cases; so, you
may want to try something like:
>> port: open/no-wait tcp://target.machine:7
>> insert port "PING"
>> copy port
== "PING"
>> close port
</gabrielle>
Sunanda.