#24760 [Opn->Csd]: Setting SNMP port fails to actually change anything

ID: 24760 Updated by: iliaa@php.net Reported By: chuck+php at 2003 dot snew dot com -Status: Open +Status: Closed Bug Type: SNMP related Operating System: FreeBSD (4 & 5) PHP Version: 4.3.3RC1 New Comment: 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. Previous Comments: ------------------------------------------------------------------------ [2003-07-22 19:05:34] chuck+php at 2003 dot snew dot com Description: ------------ snmpget ("myhost:10161", $community, $OID); ends up putting out packets to port, er, 161, not 10161. verified with tcpdump. Putting printfs in ext/snmp/snmp.c shows that the port is being parsed right, but the packets still go out wrong. Compiled against net-snmp-5.0.8 (current version of netsnmp) A nice bonus would be to allow TCP to be used (5.0.8 allows this just fine). Reproduce code: --------------- <?php $sysLoc = snmpwalk("host03.mydomain:10161", "public", "sysLocation.0", 20); ?> tcpdump will show it going out 161 Expected result: ---------------- It *should* use port 10161 and talk to agent there. Actual result: -------------- Warning: snmpget(): No response from host03.$mydomain in /var/www/docs/foo.php on line 2 # agent is not listening on port 161 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=24760&edit=1