rb_sys_fail(socket(2)) - errno == 0

[Glen Holcomb]

[Note: parts of this message were removed to make it a legal post.]

That is the error message I get when I try either of these methods for
creating an ICMP packet:

socket = Socket.new(Socket:F_INET, Socket::SOCK_RAW, Socket::IPPROTO_ICMP)

or

with net-ping

icmp = Ping::ICMP.new('machine_name')

icmp.ping?

I am on Windows XP. The account I'm logged in as has local administrator
rights.


What I'm trying to do is check to see if a system is up before I try and
make a WIN32OLE connection to it as they take forever to time-out

 

[Phill Davies]

You can use Ping from the Ruby standard library.

require 'ping'
Ping.pingecho "google.com", <timeout>, <port>

Where timeout is the number of seconds to wait for a reply (defaults to
5) and port is the port to use (defaults to the 'echo' port)


Unless you have something more specific you are trying to do this ought
to work.

 

[Glen Holcomb]

[Note: parts of this message were removed to make it a legal post.]

You can use Ping from the Ruby standard library.

require 'ping'
Ping.pingecho "google.com", <timeout>, <port>

Where timeout is the number of seconds to wait for a reply (defaults to
5) and port is the port to use (defaults to the 'echo' port)


Unless you have something more specific you are trying to do this ought
to work.

I was actually hoping for something that creates a real ICMP packet as I
can't be certain what ports are open on given workstations on the network.

 

[Daniel Berger]

It's a problem with the socket.so file that ships with the one click
installer. Take a look at this ticket for more information:

http://rubyforge.org/tracker/?func=detail&group_id=167&aid=9438&atid=715

Regards,

Dan

 

[Heesob Park]

It's a problem with the socket.so file that ships with the one click
installer. Take a look at this ticket for more information:

http://rubyforge.org/tracker/?func=detail&group_id=167&aid=9438&atid=715

The socket.so has nothing to do with this problem.
It's a problem with the msvcrt-ruby18.dll file.

That bug is related to the winsock2 compatibility.

The OCI version was built with the flag '--with-winsock2'.
If you build ruby without '--with-winsock2', it will work fine.

Regards,

Park Heesob

Park Heesob

 

[Daniel Berger]

That is the error message I get when I try either of these methods for
creating an ICMP packet:

socket =3D Socket.new(Socket:F_INET, Socket::SOCK_RAW, Socket::IPPROTO_= ICMP)

or

with net-ping

icmp =3D Ping::ICMP.new('machine_name')

icmp.ping?

I am on Windows XP. =A0The account I'm logged in as has local administrat= or
rights.

What I'm trying to do is check to see if a system is up before I try and
make a WIN32OLE connection to it as they take forever to time-out

It's a busted socket.so in the one click installer I'm afraid (who, in
turn, get it from the core team).

See http://rubyforge.org/tracker/?func=3Ddetail&group_id=3D167&aid=3D9438&a=
tid=3D715
for more information.

Works fine when I use a version of Ruby built with VC++ 8.

Regards,

Dan

 

[Daniel Berger]

2008/8/6 Daniel Berger <[email protected]>:




id=3D715

The socket.so has nothing to do with this problem.
It's a problem with the msvcrt-ruby18.dll file.

That bug is related to the winsock2 compatibility.

The OCI version was built with the flag '--with-winsock2'.
If you build ruby without '--with-winsock2', it will work fine.

My bad. Thanks for the clarification.

Dan

 

[Glen Holcomb]

[Note: parts of this message were removed to make it a legal post.]

My bad. Thanks for the clarification.

Dan

Thanks guys.

 

[Daniel Berger]

O_ICMP)



It's a busted socket.so in the one click installer I'm afraid (who, in
turn, get it from the core team).

Seehttp://rubyforge.org/tracker/?func=3Ddetail&group_id=3D167&aid=3D9438&= atid=3D715
for more information.

Works fine when I use a version of Ruby built with VC++ 8.

Regards,

Dan

Ignore this dupe. Submitting replies via the Google groups interface
is seriously messed up. Lately about a third of my posts never arrive,
another third show up several days later (as this one did), with the
final third actually posting in a timely manner.

Dan