Re: problem with InetAddress

2011-01-20 Thread Robert Story
On Thu, 13 Jan 2011 20:14:34 + Dave wrote: DS> I'm also not totally convinced that escaping the quotes around the IP DS> address will work correctly. My suspicion is that this might well be DS> interpreted as a printable string (that happened to contain a sequence DS> of digits and period cha

Re: problem with InetAddress

2011-01-20 Thread Dave Shield
On 20 January 2011 13:22, Jacek Poplawski wrote: >> Try >>   >> TCP-MIB::tcpConnectionState.ipv4.4.192.168.85.92.52219.ipv4.4.192.168.85.53.22 > > Thanks! It works. > What about ipv6? Do I need to pass decimal values too? Probably, yes. I don't believe the OID parser is clever enough to recogni

Re: problem with InetAddress

2011-01-20 Thread Jacek Poplawski
On Thu, Jan 20, 2011 at 1:58 PM, Dave Shield wrote: > On 20 January 2011 12:20, Jacek Poplawski wrote: >>> Both Wes and I responded to your post (on the same day), >>> explaining what we thought was happening. >> >> But the reply was that escaped address should work and as I wrote >> before it do

Re: problem with InetAddress

2011-01-20 Thread Dave Shield
On 20 January 2011 12:20, Jacek Poplawski wrote: >> Both Wes and I responded to your post (on the same day), >> explaining what we thought was happening. > > But the reply was that escaped address should work and as I wrote > before it doesn't. Actually, I expressed a belief that it probably woul

Re: problem with InetAddress

2011-01-20 Thread Jacek Poplawski
On Thu, Jan 20, 2011 at 1:11 PM, Dave Shield wrote: > On 20 January 2011 11:49, Jacek Poplawski wrote: >> There was no reply to my issue for 7 days so I will try to explain it >> once again. > > Both Wes and I responded to your post (on the same day), > explaining what we thought was happening.  

Re: problem with InetAddress

2011-01-20 Thread Dave Shield
On 20 January 2011 11:49, Jacek Poplawski wrote: > There was no reply to my issue for 7 days so I will try to explain it > once again. Both Wes and I responded to your post (on the same day), explaining what we thought was happening. So it's a little unfair to say that "there was no reply". >

Re: problem with InetAddress

2011-01-20 Thread Jacek Poplawski
There was no reply to my issue for 7 days so I will try to explain it once again. Please repeat these steps yourself if you think I am wrong. And if I am wrong please explain at which point I am doing mistake. I use Net-SNMP as a reference. I started snmpd and I use snmpwalk/snmpget to communicat

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: 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: 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.