I have written a simple "Get" request in Delphi7 using the Indy10 TIdSNMP component but it returns an empty reply.
The target device's Agent doesn't support v1 SNMP so I have configured it for SNMP version 2c.
I know that the OID I am requestin is correct as I used a MIB Browser to obtain it from the same device using its MIB.
I vaguely recall seeing a comment on the forums that Indy 9 only supported SNMP version 1, so I am wondering that's still the case for Indy 10?
At this time, Indy 10 still does not support SNMP versions above v1. It is on the TODO list:
#56: Update TIdSNMP to support newer SNMP versions
Related
I need to test some software drivers for SNMP v2 protocol. I am not getting it clear whether this protocol supports BOOL tags or not. I am using this simulator (SNMP Agent simulator (https://ireasoning.com/download.shtml). How do I configure digital tag in this simulator ?
I'm doing some polling of specific adapters on some PCs running windows via SNMP. I've noticed that polling using an OID constructed with the interface's ifIndex is unreliable as it appears that the ifTable is created dynamically.
I found some Cisco documentation that mentions that ifIndex is no longer persistent as of RFC2863. The documentation introduces a feature of Cisco routers that allows for ifIndex persistence between reboots.
Can such a thing be achieved in Windows? I want to avoid enumeration and identification of interfaces as it is impractical/difficult to do for my application
Unlike (newer, IOS 12+) Cisco devices, Windows does not have a fixed interface scheme.
The interface list is generated on boot and can change while running (think Wireless, dial-up, VPN, or tunneling interfaces; or link loss). That being said, on a stable Windows system the values should be consistent.
I would try the last known value, do a sanity check and re-enumerate the interfaces if it fails.
I saw SOCKS protocol have the version 4 and version 5, which can be referenced from:
https://www.rfc-editor.org/rfc/rfc1928
http://www.openssh.com/txt/socks4.protocol
My question is:
Does SOCKS exist version 1 , version 2 or version 3 prior to version 4(SOCKS4)?
Yes, there were earlier versions of SOCKS prior to version 4, as evident by the following comment in the SOCKS v4 protocol spec:
http://ftp.icm.edu.pl/packages/socks/socks4/SOCKS4.protocol
SOCKS was originally developed by David Koblas and subsequently modified
and extended by me to its current running version -- version 4.
This is also mentioned in QNX's SOCKS reference:
http://www.qnx.com/developers/docs/6.5.0/topic/com.qnx.doc.neutrino_lib_ref/socksappendix.html
The original SOCKS was written by David Koblas (koblas#netcom.com). The SOCKS protocol has changed over time. The client library shipped as of printing corresponds to SOCKS v4.2. Since the server and the clients must use the same SOCKS protocol, this library doesn't work with servers of previous releases; clients compiled with these libraries won't work with older servers.
And no, you don't need to bother worrying about those earlier versions, as nobody actually uses them anymore. SOCKS4 is the minimum version still in use, though SOCKS4A and SOCKS5 are preferred.
I need to implement an SNMP manager (client) to run on a vxworks embedded single board computer, in order to monitor and control some other Linux boards, each running an SNMP agents for reading and writing local data.
Windriver supplies an example called 'snmptalk' but with no help on how to use it or how to implement it on vxworks.
option 1. Port snmptalk to vxworks
Windriver supplies snmptalk ( located at: /vxworks...\demo\snmptalk...) but only for non-vxworks implementations.
option 2.
I called Windriver support and they gave me a sample of a working SNMP get and set, and it worked great. My vxworks code can now get and set from any SNMP agent on the network.
I have now implemented an embedded web site for my client, with pages in JavaScript, which can read and write data at any SNMP data object on the network, controlled by the user web page.
I need to set the DSCP field of packets sent from a specific (tcp) socket in windows XP.
It seems that the GQOS API should serve this purpose (see http://blogs.msdn.com/wndp/archive/2006/07/05/657196.aspx) but I really, really, can't find any working example or figure how to use it on my own.
I would be very grateful if anyone of you have a working example he/she could share.
However, the following workarounds are not acceptable:
Using the QOS2 api - it's only available on Vista and up (and I'll use it there)
Using the TC api - it's not specific to a given socket (it tries to match outgoing packets to a filter) and requires admin rights to use 3.
Using SetSockOpt with IP_TOS - it's deprecated in XP, was not meant for setting the DSCP field and requires changing the registery.
Thanks!