Hi all,
OK, I discovered and fixed several v3 bugs while testing this config.
1) A regresion introduced with SVN r256678 breaking parsing of v3
authentication part of a PDU - this is only in current; stable should
be fine; I've uploaded a patch here -
Hi all,
The modules implementing SNMPv3 in bsnmpd(1) are snmp_usm(3),
snmp_vacm(3) and snmp_target(3) all based on standard RFC. snmp_usm(3)
handles v1/v2c and v3 user configuration including user name,
auth/priv protocol type and relevant keys. snmp_vacm(3) allows
restricting users to specific
Dear all,
I am happy to announce that work on SNMPv3 support for bsnmpd(1) is
now completed and ready for testing. I want to thank the FreeBSD
Foundation for funding this work. A quick how-to get started with the
changes bsnmpd(1) follows.
The patch against FreeBSD current sources is available
Hi all,
Thanks for the feedback and comments.
I've uploaded an updated tarball at
http://people.freebsd.org/~syrinx/snmp/snmp_wlan-20100719-01.tar .
On Sun, Jul 11, 2010 at 8:23 PM, Gabor PALI p...@freebsd.org wrote:
A few comments:
- I think there should be bsnmpd(1) instead of bsnmpd(8) in
Hi all,
As some of you may know, I've been awarded a grant by the FreeBSD
Foundation to make several improvements to FreeBSD's SNMP daemon. The
first part of the project - a module for monitoring wireless
networking under FreeBSD - is now completed and I'd really appreciate
if I could get some
Hi,
On what kind of CPU are you trying to get VirtualBox to work? In some
cases VirtualBox requires VT-x/AMD-V support in the CPU to work - you
might want to make sure your CPU supports that and it's actually on.
Otherwise, I've see the same errors trying to get VirtualBox to work
on Intel Atom
