Does PHP produce any errors? Have you set your error level to "E_ALL | E_STRICT" (in both environments)? Maybe what was just a notice in WAMPP became important on CentOS.

It's possible that your server firewall is not configured to allow outgoing connections to the router (though PHP should've complained if that's the case, hence making sure you enable error reporting). Try disabling it temporarily to verify and if that's the case, add the "php", "php-cgi" and/or "apache" executables to the list of applications allowed to estabilish outgoing connections.

$ API-> comm ('/queue/simple/add', array ( "name" => "boenrobot" ));

$ clientname = "boenrobot"; $ API-> comm ('/queue/simple/add', array ( "name" => $ clientname ));

what error you get in reply? usually !re is quite descriptive

Connection attempt #1 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 0]!done Connection attempt #2 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 0]!done Connection attempt #3 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 0]!done Connection attempt #4 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 0]!done Connection attempt #5 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 0]!done Error... An error ocurred [if !done myself message]

Connection attempt #1 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 0]!done Connection attempt #2 to 192.168.55.1:8728... <<< [6] /login >>> [5/5] bytes read. >>> [5, 1]!done >>> [37/37] bytes read. >>> [37, 1]=ret=333d39b82d8e978ba92bc4f080f08fc7 <<< [6] /login <<< [9] =name=sge <<< [44] =response=00426ccaf36f522ae6422dd4dfb7a34c87 >>> [5/5] bytes read. >>> [5, 1]!done Connected... <<< [17] /queue/simple/add <<< [12] =name=teste5 <<< [32] =target-addresses=192.168.55.213 >>> [5/5] bytes read. >>> [5, 10]!done >>> [8/8] bytes read. >>> [8, 1]=ret=*17 Done ! [if !done myself message]

debug = true; if ($API->connect('192.168.55.1', 'sge', 'sge')) { // Change this as necessery $API->comm('/queue/simple/add', array( "name" => "clientname", "target-addresses" => "clienteip" )); echo "
Done !"; } else { echo "

An error occurred"; } echo "

"; ?>

Looking at the log, it appears you're having some issues with the connection between the server and the router.

The reason could still be in a misconfigured firewall, but if your router is many switches away and/or serving a good number of clients, a more likely cause is that your links are weak (a buggy switch/cable) and/or that the router is simply being overloaded.

Also, as a side note, check in the "Active Users" session that you don't have any hanging connections (you shouldn't have such with 5.*, but just in case...).

Excellent.

左挂connectio唯一可能的问题ns. In the router, check the active users in "/user active". You should only see one or two, and no "api" sessions. If there are more, it means some connections are left hanging for a while. If that's the case, it might be wise to close them explicitly once you're done by sending a "/quit" command and calling the disconnect() function.

Excellent.

左挂connectio唯一可能的问题ns. In the router, check the active users in "/user active". You should only see one or two, and no "api" sessions. If there are more, it means some connections are left hanging for a while. If that's the case, it might be wise to close them explicitly once you're done by sending a "/quit" command and calling the disconnect() function.

Dude...
In /user/active have only my conection using winbox...

Would if I connect the Centos server directly to a port of RB it work?

Excellent.

左挂connectio唯一可能的问题ns. In the router, check the active users in "/user active". You should only see one or two, and no "api" sessions. If there are more, it means some connections are left hanging for a while. If that's the case, it might be wise to close them explicitly once you're done by sending a "/quit" command and calling the disconnect() function.

Dude...
In /user/active have only my conection using winbox...

Would if I connect the Centos server directly to a port of RB it work?

If even that doesn't work, I'm officially out of ideas.

You mentioned in the start that it works with WAMP... does it work at the very same node? That is, if you plug the windows machine in place of the CentOS (have the Windows machine directly connected to the router board), does it work?

If it does, this might be a PHP bug related to the way it uses sockets on CentOS. Solution: Use another kind of Linux and/or report this to the PHP/CentOS devs.

If even then it doesn't work, this might be a bug in RouterOS that occurs only on that router board. Solution: Upgrade to the latest RouterOS, and if even then it doesn't work, contact support.

Is Windows using the same PHP version? Again, this is a bug in either PHP or CentOS. So, if the version on CentOS is older than the one on Windows, it might be the cause. Try with PHP 5.3.10.

. Fixed forward stream seeking emulation in streams that don't support seeking
in situations where the read operation gives back less data than requested
and when there was data in the buffer before the emulation started. Also
made more consistent its behavior -- should return failure every time less
data than was requested was skipped. (Gustavo)

To solve it edit the script and add:

sleep (2);

on a new line after line 85