Re: problem with InetAddress

2011-01-13 Thread Dave Shield
On 13 January 2011 16:58, Wes Hardaker wrote: JP> Could you explain should "4" (between "1" and IP) be in the OID or JP> not? WH> Yes.  It gives the length of address following it so that it can be WH> properly decoded.  Although you could determine the length from the IP WH> address type Note t

Re: generating user defined traps

2011-01-13 Thread Wes Hardaker
> On Mon, 10 Jan 2011 23:35:45 +0530, "MAS ." said: M> I have snmp daemon running on my special hardware. I want to generate trap M> after checking particular register. so how and where to add my code (in c). M> how to monitor some register continuously? In case of snmpget and snmpset I M> us

Re: table_iterator2?

2011-01-13 Thread Wes Hardaker
> On Wed, 12 Jan 2011 21:12:50 +0100, Bart Van Assche > said: BVA> See also r19859. Thank you! I like that much better! Now, I'd also argue that we should have an api stub-name to indicate ownership rather than the 2, but I'm at a loss for what would be a good choice there. -- Wes Ha

Re: Send snmptrap

2011-01-13 Thread Wes Hardaker
The better way would be to use the API to send a trap. Rather than call snmptrap from within a system call, look at the insides of the apps/snmptrap.c file and copy how it creates a trap (or inform) PDU and send it via function calls instead. -- Wes Hardaker Please mail all replies to net-snmp-

Re: SVN trunk multi-platform build errors

2011-01-13 Thread Dave Shield
On 12 January 2011 22:05, Niels Baggesen wrote: > Right, having spent the evening with it, it now compiles for OpenBSD > 4.7, NetBSD 4 and 5, FreeBSD 7 and 8, DragonFly 1.12 and 2.6, and > RedHat/CentOS 4, 5, 6 ... > > You can find the results at http://baggesen.net/~nba/buildbot/ including > a sm

Re: problem with InetAddress

2011-01-13 Thread Wes Hardaker
> On Thu, 13 Jan 2011 16:57:19 +0100, Jacek Poplawski > said: JP> TCP-MIB::tcpConnectionState.ipv4.\"192.168.85.92\".56470.ipv4.\"192.168.85.53\".22 JP> Error in packet JP> Reason: (noSuchName) There is no such variable name in this MIB. JP> Failed object: TCP-MIB::tcpConnectionState.i

Re: problem with InetAddress

2011-01-13 Thread Jacek Poplawski
On Thu, Jan 13, 2011 at 4:42 PM, Robert Story wrote: > On Thu, 13 Jan 2011 13:42:32 +0100 Jacek wrote: > JP> 3) I try to get OID I received in step 1, it fails > JP> snmpget -v 1 -c public localhost > JP> > TCP-MIB::tcpConnectionState.ipv4."192.168.85.92".49207.ipv4."192.168.85.53".22 > JP> > JP>

Re: DTLSUDP: Past-end-of-buffer read in netsnmp_tdomain_dump()

2011-01-13 Thread Robert Story
On Wed, 12 Jan 2011 20:57:10 +0100 Bart wrote: BVA> Since recently Valgrind complains about the DTLSUDP code in the trunk. BVA> Apparently the DTLSUDP code does not NULL-terminate the domain prefix list ? Yep, my bad. Fixing...

Re: problem with InetAddress

2011-01-13 Thread Robert Story
On Thu, 13 Jan 2011 13:42:32 +0100 Jacek wrote: JP> 3) I try to get OID I received in step 1, it fails JP> snmpget -v 1 -c public localhost JP> TCP-MIB::tcpConnectionState.ipv4."192.168.85.92".49207.ipv4."192.168.85.53".22 JP> JP> TCP-MIB::tcpConnectionState.ipv4.192.168.85.92.49207.ipv4.192.168.

Re: SNMP OID Inquery

2011-01-13 Thread Niels Baggesen
On Thu, Jan 13, 2011 at 04:07:44PM +0800, [email protected] wrote: > C:\Documents and Settings\Administrator>snmpset -v2c -c 192.168.10.1 > 1.3.6.1.4.171.12.9.6.1.1.3.3.1 i 6000 > i: Bad object type: 6 You are missing the community after the -c /Niels -- Niels Baggesen - @home - År

problem with InetAddress

2011-01-13 Thread Jacek Poplawski
Hello, I use NET-SNMP version: 5.6 compiled myself for Arch Linux with ipv6 enabled. I have trouble with understanding how Net-SNMP translates InetAddressType/InetAddress OIDs. 1) I run walk on tcpConnectionState snmpwalk -v 1 -c public localhost TCP-MIB::tcpConnectionState (...) TCP-MIB::tcpConne

Re: SNMP OID Inquery

2011-01-13 Thread Dave Shield
2011/1/13 > snmpset -v2c -c 192.168.10.1 1.3.6.1.4.171.12.9.6.1.1.3.3.1 i 6000 > i: Bad object type: 6 > > It always show  "Bad object type" First problem - this OID does not match the one in the description you posted (1.3.6.1.4.171 vs 1.3.6.1.4.*1*.171.) Second problem - the '-c' op

SNMP OID Inquery

2011-01-13 Thread Mark_Huang
Hello, Support, We face one question about setting via snmp. We did the testing for creating flow meter via the SNMP (we check the figure you provide and test it via SNMP command) C:\Documents and Settings\Administrator>snmpset -v2c -c 192.168.10.1 1.3.6.1.4.171.12.9.6.1.1.3.3.1 i 6000 i: