Hello list.
Just subscribed; my first message on the Net-SNMP list in
several years.
It's been > 3 years since I've compiled using MinGW.
Now I'm sticking more to clang-cl and MSVC and notice
the support for MSVC wrt. to IPv6 is in a real (excuse my
French) shitty state. E.g. the '{ }' syntax is
Bart Van Assche wrote:
As one can see on https://ci.appveyor.com/project/BVanAssche87257/net-snmp
the build of the Net-SNMP master branch
passes for MSVC-2017,
Really? From:
https://ci.appveyor.com/project/BVanAssche87257/net-snmp/build/job/shuwoe93gfu2af2t
just now (search for 'error C20
With this command:
snmpwalk.exe -M mibs -m ALL -v1 -c public 10.0.0.21
I've getting lines with junk in the output:
IPV6-MIB::ipv6NetToMediaValid.1.''.12 = INTEGER: true(1)
IPV6-MIB::ipv6NetToMediaValid.1.''.22 = INTEGER: true(1)
IPV6-MIB::ipv6NetToMediaVali
Niels Baggesen wrote:
With this command:
snmpwalk.exe -M mibs -m ALL -v1 -c public 10.0.0.21
I've getting lines with junk in the output:
IPV6-MIB::ipv6NetToMediaValid.1.''.12 = INTEGER: true(1)
It is trying to show an OCTET STRING as a string, which in most cases is usef
Madhusudhana R wrote:
Hi Coders,
I am trying to compile netsnmp 5.8 on windows 7 platform using VS2013 framework.
I am getting compilation errors on asprintf and vasprintf usage as shown below
As per my analysis I don’t see VS2013 compiler provides support for asprintf and vasprintf. I observ
