ID:               21653
 Comment by:       laudanp at yahoo dot com
 Reported By:      support at hostcolor dot com
 Status:           Closed
 Bug Type:         Sockets related
 Operating System: RedHat 7.2
 PHP Version:      4.3.3RC2-dev
 New Comment:

Download: .bz2 (3.5M) .gz (4.3M) 
Built On: Jun 30, 2003 11:30 GMT
php4-STABLE-200306301130

http://64.246.34.44/phpinfo.php
http://64.246.34.44/testpaul.php

Hi, I grabbed the latest stable cvs snapshot and it appears the problem
persists.  Its the same code, no change, since I started using it prior
to PHP 4.2.3.  For some reason, it doesn't work with 4.3.x.

Now, for my UDP scanner
(http://www.computercops.biz/modules.php?name=UDP_Scanner) on PHP 4.3.x
I use the following code which works well with either 4.2.3 or 4.3.x:

$handle = fsockopen($this-> targetIP, $portNumber, &$errno, &$errstr,
2);

For the TCP Scanner
(http://www.computercops.biz/modules.php?name=TCP_Scanner), I have this
line:

$handle = fsockopen($this-> targetIP, $index, $errno, $errstr, $this->
timeout);

So something is different between the TCP and UDP connections.  Now,
I'm running these scans from a box that is dropping the probes.  Hence,
since UDP is connectionless and TCP is connection oriented, the bug may
have something to do with this?  I haven't tested it on a system that
is not running a firewall recently.  What do your tests show now with
the current snapshot?

Thanks

(Phew, this is one elusive bug).

P.S.  Here is my configure statement:

./configure --with-mysql --with-apxs --with-gd
--with-jpeg-dir=../jpeg-6b/ --with-zlib


Previous Comments:
------------------------------------------------------------------------

[2003-06-29 22:18:07] laudanp at yahoo dot com

Hi, thanks for the reply.  I'll grab the newest stable source tomorrow
morning and give it a try once more.  But as of my last comment above,
the error message I get is:

Warning: fsockopen(): unable to connect to ...

Again, I'll test it out again tomorrow with the newest build and report
back.

Thanks

------------------------------------------------------------------------

[2003-06-29 21:27:00] [EMAIL PROTECTED]

This bug has been fixed in CVS.

In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
 
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.

In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
 
Thank you for the report, and for helping us make PHP better.

Sample script appears to work correctly, assuming fixed.

------------------------------------------------------------------------

[2003-06-27 08:48:21] laudanp at yahoo dot com

HI, I grabbed the newest stable snapshot today
(http://snaps.php.net/php4-STABLE-latest.tar.gz), build:

php4-STABLE-200306271330 / PHP Version 4.3.3RC2-dev

And the problem still shows up:

http://64.246.34.44/testpaul.php

Warning: fsockopen(): unable to connect to xxx.xxx.xxx.xxx in
/var/www/html/testpaul.php on line 134

Which is this line in the script:

$fp = fsockopen($REMOTE_ADDR, $portno, $errno, $errstr, 1);

For confirmation of the build, you can use this:

http://64.246.34.44/phpinfo.php

Thanks

------------------------------------------------------------------------

[2003-06-23 20:48:40] [EMAIL PROTECTED]

Yes, get the latest stable snapshot..


------------------------------------------------------------------------

[2003-06-22 15:09:21] laudanp at yahoo dot com

Yes that error message pops up.  If you run it with a couple of those
open ports, what do you get?

But yes, I'm getting those errors.  Re-download newest stable?

------------------------------------------------------------------------

The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
    http://bugs.php.net/21653

-- 
Edit this bug report at http://bugs.php.net/?id=21653&edit=1

Reply via email to