Age | Commit message (Collapse) | Author |
|
|
|
|
|
bmk/snmp/snmp420_integration
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
|
|
|
|
|
|
|
|
(an empty) appup entry.
|
|
for which we are building man-pages.
|
|
|
|
snmpc to snmpc(command)...
|
|
|
|
|
|
line tool. Also updated the central .gitignore file.
|
|
Also added some proper documentation.
|
|
|
|
|
|
Merge branch 'bmk/snmp/minor_doc_improvements/OTP-9037' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
|
|
Merge branch 'bmk/snmp/snmpc/OTP-9004' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
lib/snmp/vsn.mk
|
|
snmp_view_based_acm_mib:snmp_view_based_acm_mib:reconfigure/1 on a
running node, the table vacmAccessTable was not properly cleaned.
This meant that if some entries in the vacm.conf file was removed
(compared to the "current" config), while others where modified
and/or added, the removed entrie(s) would still exist in the
vacmAccessTable table.
Merge branch 'bmk/snmp/vacmAccessTable_cleanup/OTP-8981' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
lib/snmp/vsn.mk
|
|
is_set_ok and set operation(s), all values of the
vacmAccessSecurityModel column was incorrectly translated
to *any*.
Merge branch 'bmk/snmp/verify_vacm_security_model/OTP-8980' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
lib/snmp/test/snmp_appup_test.erl
lib/snmp/vsn.mk
|
|
print functions, for each mib handled by the SNMP (agent)
application. This will be usefull when debugging a running
agent. See snmpa:print_mib_info/0, snmpa:print_mib_tables/0
and snmpa:print_mib_variables/0 for more info.
Merge branch 'bmk/snmp/add_snmp_table_print/OTP-8977' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/src/app/snmp.appup.src
lib/snmp/vsn.mk
|
|
AGENT-CAPABILITIES and full support for textual convention
MODULE-COMPLIANCE, both defined by the SNMPv2-CONF mib.
The *reference* and *modules* part(s) are stored in the
assocList field of the mib-entry (me) record.
Only handled if the option(s) agent_capabilities and
module_compliance (respectively) are provided to the
compiler.
For backward compatibillity, the MIBs provided with
this application are *not* compiled with these options.
Merge branch 'bmk/snmp/add_compiler_support_agent_capabilities/OTP-8966' into bmk/snmp/snmp419_integration/OTP-9068
Conflicts:
lib/snmp/test/snmp_compiler_test.erl
|
|
|
|
not actually be part of the release notes) and appup file.
|
|
|
|
|
|
|
|
|
|
Also added entry in the appup file.
|
|
|
|
|
|
into bmk/snmp/snmpc/OTP-9004
Conflicts:
lib/snmp/doc/src/notes.xml
lib/snmp/vsn.mk
|
|
|
|
|
|
*) Update release notes (with regard to module_compliance)
*) New compiler options: agent_capabilities and module_compliance
*) Update mib compiler option description (new options
for agent_capabilities and module_compliance)
*) New test case for module_compliance.
*) Added test mib for module_complianc test case.
*) Added some options for the MIB makefile.
...
|
|
|
|
|
|
|
|
the vacmAccessTable whas not properly cleaned.
This means that if some entries in the vacm.conf file was removed
compared to the "current" config), while others where modified
and/or added, the removed entrie(s) would still exist in the vacmAccessTable.
|
|
opteration(s), all values of the vacmAccessSecurityModel column was
incorrectly translated to "any".
|
|
opteration(s), all values of the vacmAccessSecurityModel column was
incorrectly translated to "any".
|
|
|
|
|
|
* maint-r13:
snmp: Patch 1130
inets: Patch 1129
ssh: Patch 1127
ssh: Patch 1126
Conflicts:
lib/inets/doc/src/notes.xml
lib/inets/src/inets_app/inets.appup.src
lib/inets/vsn.mk
lib/snmp/vsn.mk
lib/ssh/doc/src/notes.xml
lib/ssh/src/ssh.appup.src
lib/ssh/vsn.mk
|
|
OTP-8761 When the function FilterMod:accept_recv/2 returned false
the SNMP agent stopped collecting messages from UDP.
|
|
OTP-8478 [agent] Added very basic support for multiple SNMPv3 EngineIDs
in a single agent.
|
|
OTP-8574 The SMI specifies that an table row OID should be named:
{ "1" }. An option has been introduced, relaxed_row_name_assign_check,
that allows for a more liberal numbering scheme.
OTP-8594 Changes to make snmp (forward) compatible with the new version
of the crypto application (released in R14). As of R14,
crypto is implemented using NIFs. Also, the API is more
strict.
OTP-8648 [manager] Changed default value for the MIB server cache.
Auto GC is now on by default.
OTP-8563 Decoding of Counter64 values larger then 9306882749598007295
fails. Counter64 is encoded as an 64 bit signed integer,
but is actually an unsigned integer, which the decoder does
not take into account.
OTP-8595 [compiler] Fails to compile non-contiguous BITS. Per Hedeland
OTP-8646 [manager] Raise condition causing the manager server process
to crash. Unregistering an agent while traffic (set/get-operations)
is ongoing could cause a crash in the manager server process
(raise condition).
|
|
OTP-8480 [agent] A minor mnesia related performance improvement.
OTP-8481 [manager] Fixed an upgrade/downgrade problem.
Upgrade/downgrade from/to 4.13.5 did not work for the net-if
process. This has now been fixed
|
|
|
|
|