|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2003-07-25 07:45 UTC] iliaa@php.net
|
|||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Tue Oct 28 22:00:01 2025 UTC |
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