Here’s another patch for python-agentx that I already did on June 3rd and this one is rather a major one: it overthrows python-agentx’s variable handling completely.
Category: Software
python-agentx: Registering variables repeatedly
All good things come in threes… consider the following code snippet that uses python-agentx: axd.RegisterVar(“a”, 0) axd.RegisterVar(“b”, 1) snmpwalk will show both a and b correctly. Now consider the following code: axd.RegisterVar(“a”, 0) axd.RegisterVar(“b”, 1) axd.RegisterVar(“a”, 2) snmpwalk will show a only. Which is a bug. Why?
Float variables not working with python-agentx
I just found another bug in current versions of the python-agentx. If, in your agent, you do something like this: cpuTemp = 24.5 axd.RegisterVar(“cpuTemp”, cpuTemp) you will hit Internal error in type switching error messages.
“Error: OID not increasing” when declaring SNMP tables with python-agentx
At work, I’m currently working with python-agentx to implement an AgentX-based SNMP agent. Testing around with snmpwalk, I got the following error: $ snmpwalk -Of -v2c -c public localhost DFS-HW-MIB::cpus .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusNumber = INTEGER: 2 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.0 = INTEGER: 0 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuIndex.1 = INTEGER: 0 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuIndex.2 = INTEGER: 1 .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuStatus.1 = INTEGER: OK(1) .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuStatus.2 = INTEGER: OK(1) .iso.org.dod.internet.private.enterprises.dfs.systemhaus.dfsHwMIB.cpus.cpusTable.cpuEntry.cpuNumCores.1… Continue reading “Error: OID not increasing” when declaring SNMP tables with python-agentx
The 30 second delay in booting Windows PE’s pxeboot.com via pxelinux
The Windows Preinstallation Environment (Windows PE) is used to install newer Microsoft operating systems such as Windows 7 and Windows Server 2008 — Windows PE is what boots, when the appropriate install DVD is inserted.
Clarifying the relationship between PXELinux, Etherboot and gPXE/iPXE
Here are some points I’d like to make to clarify the relationship between PXELinux, Etherboot and gPXE/iPXE:
libvirt utilities on openSUSE 12.1 appear to be broken
The libvirt tools on openSUSE 12.1 currently cause me some headache:
How SSL/TLS clients validate certificates in a certificate chain
Certificate chains are a key feature of the entire SSL/TLS concept: a root Certificate Authority (CA) issues certificates for sub CAs, which in turn issue certificates for other sub CAs or end systems such as servers. The Sub CAs are often local departments, branch offices etc. and issuing a certificate for a sub CA, which… Continue reading How SSL/TLS clients validate certificates in a certificate chain
ChilliSpot 1.1.0 patches (not only for x64)
ChilliSpot is a well-known captive portal solution for wireless hotspot providers. With its Universal Access Method (UAM), all user communication is intercepted and HTTP requests with the user’s web browser are redirected to a webserver running a script which asks for authentication credentials. The script feeds those back to ChilliSpot which in turn contacts a… Continue reading ChilliSpot 1.1.0 patches (not only for x64)