just "ping"; now "psst"
[1/5] from: acmetech::sonic::net at: 19-Aug-2002 21:31
Thanks Gabriel. Sorry everybody... I'm just a wannabe programmer frustrated at my own
foibles. In response to pekr's point about no-can-do because of no root access on unix
(?), I'll just concede that ping is not what I need. I'll call it "hey", "yo", "rebyo",
"boo", "reboo", "psst", "ying", "zing", "pang", "rebkiss", or something. All I really
want is to see an echo, or any other response from a live host.
This doesn't work for me:
>>> port: open/no-wait tcp://target.machine:7
>>> insert port "PING"
>>> copy port
>== "PING"
>>> close port
I get several seconds of nothing, then Cannot connect to (whatever). For (whatever),
I've tried different IPs, domain names, localhost, other ports besides 7, and udp instead
of tcp. But ping works <se grin>, and I can get a connection and response in rebol using
pop: open/lines tcp://mypopserver.com:110
I'll figure this out if it kills me, or I'll take it to the beginner's rebol group. Sorry
for buggin' y'all. Then I'll put psst.r in the library if/when I'm done, and when I can
get it to log the up/down status of a list of hosts. (Presently I'm doing this with ping
in klever.net's BigBrother, DOS find, redirected batch file output, and various file
concatenations. Yuk!)
--Ken.
____________________________ ____________________________
Ah, you hate Microsoft too! So comrade, ven do vee plan to defect?
[2/5] from: g:santilli:tiscalinet:it at: 20-Aug-2002 19:20
Hi Ken,
On Tuesday, August 20, 2002, 6:31:39 AM, you wrote:
KBC> I get several seconds of nothing, then Cannot connect to (whatever).
As I said, that port is usally closed. If you have control on
those machines, you can turn the echo service on (but beware of
security risks - I'd rather suggest to write a little server
script that answers with "I'm here" to everyone that connects...).
Otherwise, you can use any other service the machine provides to
discover if it is up or not.
Anyway, asking questions never hurts, so don't feel sorry. :-)
Regards,
Gabriele.
--
Gabriele Santilli <[g--santilli--tiscalinet--it]> -- REBOL Programmer
Amigan -- AGI L'Aquila -- REB: http://web.tiscali.it/rebol/index.r
[3/5] from: tomc:darkwing:uoregon at: 20-Aug-2002 12:33
Hi Ken,
If you know a port is open on a machine you can assume it is doen if you
cannot connect, you dont need any response beyond that a connection is
possible.
maybe these will help
>> either error? try[port: open/no-wait tcp://rebol.com:80]
["ahrgg"][close port "ping!"]
== "ping!"
(with a bad/closed port number)
>> either error? try[port: open/no-wait tcp://rebol.com:0]
["ahrgg"][close port "ping!"]
== "ahrgg"
>> either error? try[port: open/no-wait tcp://whatever.com:80]
["ahggg"][close port "ping!"]
== "ahggg"
>> either error? try[port: open/no-wait tcp://www.whatever.com:80]
["ahggg"][close port "ping!"]
== "ping!"
On Mon, 19 Aug 2002, Ken B. Cadby wrote:
[4/5] from: acmetech:sonic at: 22-Aug-2002 14:39
Okay, thanks Tom, Gabrielle, Sunanda, Petr. I finally understand that ping and traceroute
are ICMP animals (sometimes with UDP added), and icmp doesn't specify ports. Per my research
of the list archives, rt's not interested in rebol being used on a net for diagnostics,
or at least not with ICMP and unix root rights. Meanwhile, I'll have to continue to generate
(rebol-readable) report files with my windows icmp and dos kludges, or do a port-open
or other kludge on other hosts. I'll probably eventually have to cross firewalls and
overcome nat somehow, too
--Ken.
At 12:33 PM 8/20/02 -0700, you wrote:
>Hi Ken,
>If you know a port is open on a machine you can assume it is doen if you
<<quoted lines omitted: 14>>
> ["ahggg"][close port "ping!"]
>== "ping!"
____________________________ ____________________________
Ah, you hate Microsoft too! So comrade, ven do vee plan to defect?
[5/5] from: petr:krenzelok:trz:cz at: 23-Aug-2002 6:55
Ken B. Cadby wrote:
>Okay, thanks Tom, Gabrielle, Sunanda, Petr. I finally understand that ping and traceroute
are ICMP animals (sometimes with UDP added), and icmp doesn't specify ports. Per my research
of the list archives, rt's not interested in rebol being used on a net for diagnostics,
or at least not with ICMP and unix root rights. Meanwhile, I'll have to continue to generate
(rebol-readable) report files with my windows icmp and dos kludges, or do a port-open
or other kludge on other hosts. I'll probably eventually have to cross firewalls and
overcome nat somehow, too
>
Or just buy /Pro version with shell and library support and a) call
external tool to handle it for you or b) try to link to some library,
which will do it for you ...
-pekr-
Notes
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted