Menu
▾
▴
net-snmp-coders — Discussion of internal project coding (Please use this OR -users, NOT both!)
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(315) |
Dec
(298) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(254) |
Feb
(467) |
Mar
(430) |
Apr
(345) |
May
(406) |
Jun
(336) |
Jul
(313) |
Aug
(265) |
Sep
(433) |
Oct
(462) |
Nov
(387) |
Dec
(232) |
| 2002 |
Jan
(352) |
Feb
(556) |
Mar
(463) |
Apr
(500) |
May
(557) |
Jun
(337) |
Jul
(317) |
Aug
(279) |
Sep
(273) |
Oct
(354) |
Nov
(267) |
Dec
(347) |
| 2003 |
Jan
(351) |
Feb
(445) |
Mar
(520) |
Apr
(665) |
May
(499) |
Jun
(393) |
Jul
(304) |
Aug
(425) |
Sep
(262) |
Oct
(329) |
Nov
(220) |
Dec
(174) |
| 2004 |
Jan
(365) |
Feb
(479) |
Mar
(515) |
Apr
(522) |
May
(214) |
Jun
(471) |
Jul
(292) |
Aug
(341) |
Sep
(243) |
Oct
(446) |
Nov
(294) |
Dec
(147) |
| 2005 |
Jan
(171) |
Feb
(209) |
Mar
(218) |
Apr
(321) |
May
(233) |
Jun
(534) |
Jul
(268) |
Aug
(345) |
Sep
(498) |
Oct
(557) |
Nov
(459) |
Dec
(238) |
| 2006 |
Jan
(288) |
Feb
(180) |
Mar
(151) |
Apr
(113) |
May
(164) |
Jun
(277) |
Jul
(160) |
Aug
(383) |
Sep
(221) |
Oct
(404) |
Nov
(358) |
Dec
(163) |
| 2007 |
Jan
(293) |
Feb
(175) |
Mar
(202) |
Apr
(155) |
May
(427) |
Jun
(484) |
Jul
(414) |
Aug
(125) |
Sep
(131) |
Oct
(160) |
Nov
(79) |
Dec
(70) |
| 2008 |
Jan
(133) |
Feb
(115) |
Mar
(158) |
Apr
(194) |
May
(197) |
Jun
(230) |
Jul
(146) |
Aug
(68) |
Sep
(93) |
Oct
(53) |
Nov
(95) |
Dec
(69) |
| 2009 |
Jan
(81) |
Feb
(162) |
Mar
(215) |
Apr
(216) |
May
(78) |
Jun
(131) |
Jul
(61) |
Aug
(176) |
Sep
(127) |
Oct
(28) |
Nov
(83) |
Dec
(94) |
| 2010 |
Jan
(100) |
Feb
(187) |
Mar
(320) |
Apr
(161) |
May
(194) |
Jun
(142) |
Jul
(129) |
Aug
(139) |
Sep
(239) |
Oct
(202) |
Nov
(139) |
Dec
(196) |
| 2011 |
Jan
(195) |
Feb
(191) |
Mar
(201) |
Apr
(127) |
May
(84) |
Jun
(126) |
Jul
(101) |
Aug
(237) |
Sep
(123) |
Oct
(104) |
Nov
(197) |
Dec
(114) |
| 2012 |
Jan
(65) |
Feb
(85) |
Mar
(129) |
Apr
(84) |
May
(94) |
Jun
(83) |
Jul
(89) |
Aug
(85) |
Sep
(89) |
Oct
(73) |
Nov
(34) |
Dec
(38) |
| 2013 |
Jan
(89) |
Feb
(30) |
Mar
(25) |
Apr
(18) |
May
(20) |
Jun
(45) |
Jul
(74) |
Aug
(37) |
Sep
(72) |
Oct
(30) |
Nov
(67) |
Dec
(24) |
| 2014 |
Jan
(23) |
Feb
(16) |
Mar
(40) |
Apr
(37) |
May
(12) |
Jun
(18) |
Jul
(30) |
Aug
(26) |
Sep
(24) |
Oct
(32) |
Nov
(15) |
Dec
(33) |
| 2015 |
Jan
(15) |
Feb
(45) |
Mar
(21) |
Apr
(24) |
May
(22) |
Jun
(7) |
Jul
(57) |
Aug
(17) |
Sep
(16) |
Oct
(3) |
Nov
(8) |
Dec
(13) |
| 2016 |
Jan
(7) |
Feb
(14) |
Mar
(40) |
Apr
(8) |
May
(10) |
Jun
(6) |
Jul
(8) |
Aug
(10) |
Sep
(19) |
Oct
(20) |
Nov
(45) |
Dec
(10) |
| 2017 |
Jan
(10) |
Feb
(12) |
Mar
(3) |
Apr
(17) |
May
(41) |
Jun
(21) |
Jul
(13) |
Aug
(13) |
Sep
(7) |
Oct
(23) |
Nov
(10) |
Dec
(23) |
| 2018 |
Jan
(45) |
Feb
(3) |
Mar
(57) |
Apr
(107) |
May
(173) |
Jun
(47) |
Jul
(28) |
Aug
(26) |
Sep
(38) |
Oct
(56) |
Nov
(22) |
Dec
(11) |
| 2019 |
Jan
(37) |
Feb
(8) |
Mar
(7) |
Apr
(29) |
May
(32) |
Jun
(5) |
Jul
(21) |
Aug
(31) |
Sep
(38) |
Oct
(8) |
Nov
(13) |
Dec
(10) |
| 2020 |
Jan
(9) |
Feb
(33) |
Mar
(14) |
Apr
(4) |
May
(16) |
Jun
(11) |
Jul
(14) |
Aug
(50) |
Sep
(24) |
Oct
(3) |
Nov
(14) |
Dec
(13) |
| 2021 |
Jan
(18) |
Feb
(15) |
Mar
(12) |
Apr
(9) |
May
(9) |
Jun
(8) |
Jul
(6) |
Aug
(7) |
Sep
(26) |
Oct
(17) |
Nov
(6) |
Dec
(2) |
| 2022 |
Jan
(3) |
Feb
(11) |
Mar
(7) |
Apr
(15) |
May
(5) |
Jun
(4) |
Jul
(29) |
Aug
(6) |
Sep
(7) |
Oct
|
Nov
(4) |
Dec
(1) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
(10) |
May
(3) |
Jun
(5) |
Jul
(3) |
Aug
(10) |
Sep
(10) |
Oct
(7) |
Nov
(2) |
Dec
(4) |
| 2024 |
Jan
(22) |
Feb
(5) |
Mar
(11) |
Apr
(20) |
May
(16) |
Jun
(9) |
Jul
(14) |
Aug
(5) |
Sep
(7) |
Oct
(4) |
Nov
(3) |
Dec
|
| 2025 |
Jan
(6) |
Feb
(6) |
Mar
(14) |
Apr
(2) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ed F. <qua...@gm...> - 2021-01-05 14:21:10
|
I'm trying to understand the extended session API, as documented in snmp_api.h. These three functions require an netsnmp_transport_s*. How can I initialize this structure? |
|
From: Ed F. <qua...@gm...> - 2021-01-02 01:31:50
|
I'm trying to write an SNMP manager using the net-snmp API. The manager will use UDP in IPv4 and IPv6, and will be sending get-requests (and getbulk, and getnext) to 10000 agents (arbitrary number, but you get the idea - a relatively large number). Is there any way to do this using just a single session? I've compiled and experimented with the demo apps, they seem to use one session per agent. Creating 10000 separate sessions seems excessive (as I understand, this would consume 10000 sockets and 10000 distinct SRC PORTS from my host). Creating/using/closing 10000 sessions seems excessive as well. The reason I'm going here: my manager must interact with a firewall before sending any requests to any agents; a single firewall interaction identifying a single UDP source port would be much more desirable than 10000 firewall interactions identifying 10000 different UDP source ports. Thanks in advance for your comments. |
|
From: Wes H. <har...@us...> - 2020-12-15 14:29:25
|
chandrasekharreddy chinnapareddygari <cha...@ho...> writes: > I'm using net-snmp 5.8 version .My requirement is conf files should updtae > without restarting snmpd . > > I'm sending SIGHUP signal to update SNMP data with out restarting snmpd . > snmpv3 details are not updating . > Please help me how to proceed further. I'm confused about how you're going about adding and deleting users? Are you doing it by putting users into a configuration file? If so, which one? Are you doing it using the snmpusm command to create new users? Once they're created, are you editing the files to remove the user or using snmpusm to delete them? -- Wes Hardaker Please mail all replies to net...@li... |
|
From: chandrasekharreddy c. <cha...@ho...> - 2020-12-15 03:19:32
|
Thanks Larry Hayes , I too have same question as Joan Landry has Thanks, Chandra Get Outlook for Android<https://aka.ms/ghei36> ________________________________ From: Joan Landry <JoL...@ad...> Sent: Monday, 14 December, 2020, 21:26 To: Larry Hayes; chandrasekharreddy chinnapareddygari Cc: net...@li...; net...@li... Subject: RE: Snmpv3 users details are not deleting from /var/net-snmp/snmpd.conf file Thanks – but my question was regarding actually being the master agent and internally updating the net-snmp library with data received via a CLI. I believe the only way to do this is via the snmpd.conf file. So any info on this would be greatly appreciated. Thanks, From: Larry Hayes <lh...@gm...> Sent: Monday, December 14, 2020 10:48 AM To: chandrasekharreddy chinnapareddygari <cha...@ho...> Cc: net...@li...; net...@li... Subject: Re: Snmpv3 users details are not deleting from /var/net-snmp/snmpd.conf file External email: [net...@li...] ________________________________ I am no expert, but do deal with creating and deleting SNMP v3 users in my job. You may have to use the tool, snmpuser to remove V3 users without restarting the snmpd daemon. >From the man page: " snmpusm is an SNMP application that can be used to do simple maintenance on the users known to an SNMP agent, by manipulating the agent's User-based Security Module (USM) table. The user needs write access to the usmUserTable MIB table. This tool can be used to create, delete, clone, and change the passphrase of users configured on a running SNMP agent." On Sat, Dec 12, 2020 at 9:55 PM chandrasekharreddy chinnapareddygari <cha...@ho...<mailto:cha...@ho...>> wrote: Hi team, I'm using net-snmp 5.8 version .My requirement is conf files should updtae without restarting snmpd . I'm sending SIGHUP signal to update SNMP data with out restarting snmpd . snmpv3 details are not updating . Please help me how to proceed further. Thanks, Chandra. Get Outlook for Android<https://urldefense.com/v3/__https:/aka.ms/ghei36__;!!PIqRGrUndTen!UrokTSk2NGdWBofBJMrtgwyJgDXs2KLNFXTPV2uqeTZbuPHnNln2NRUjUybRdg$> _______________________________________________ Net-snmp-coders mailing list Net...@li...<mailto:Net...@li...> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/net-snmp-coders__;!!PIqRGrUndTen!UrokTSk2NGdWBofBJMrtgwyJgDXs2KLNFXTPV2uqeTZbuPHnNln2NRV5PZweqA$> Please see our privacy statement at https://www.adva.com/en/about-us/legal/privacy-statement for details of how ADVA processes personal information. |
|
From: Joan L. <JoL...@ad...> - 2020-12-14 15:56:42
|
Thanks – but my question was regarding actually being the master agent and internally updating the net-snmp library with data received via a CLI. I believe the only way to do this is via the snmpd.conf file. So any info on this would be greatly appreciated. Thanks, From: Larry Hayes <lh...@gm...> Sent: Monday, December 14, 2020 10:48 AM To: chandrasekharreddy chinnapareddygari <cha...@ho...> Cc: net...@li...; net...@li... Subject: Re: Snmpv3 users details are not deleting from /var/net-snmp/snmpd.conf file External email: [net...@li...] ________________________________ I am no expert, but do deal with creating and deleting SNMP v3 users in my job. You may have to use the tool, snmpuser to remove V3 users without restarting the snmpd daemon. From the man page: " snmpusm is an SNMP application that can be used to do simple maintenance on the users known to an SNMP agent, by manipulating the agent's User-based Security Module (USM) table. The user needs write access to the usmUserTable MIB table. This tool can be used to create, delete, clone, and change the passphrase of users configured on a running SNMP agent." On Sat, Dec 12, 2020 at 9:55 PM chandrasekharreddy chinnapareddygari <cha...@ho...<mailto:cha...@ho...>> wrote: Hi team, I'm using net-snmp 5.8 version .My requirement is conf files should updtae without restarting snmpd . I'm sending SIGHUP signal to update SNMP data with out restarting snmpd . snmpv3 details are not updating . Please help me how to proceed further. Thanks, Chandra. Get Outlook for Android<https://urldefense.com/v3/__https:/aka.ms/ghei36__;!!PIqRGrUndTen!UrokTSk2NGdWBofBJMrtgwyJgDXs2KLNFXTPV2uqeTZbuPHnNln2NRUjUybRdg$> _______________________________________________ Net-snmp-coders mailing list Net...@li...<mailto:Net...@li...> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders<https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/net-snmp-coders__;!!PIqRGrUndTen!UrokTSk2NGdWBofBJMrtgwyJgDXs2KLNFXTPV2uqeTZbuPHnNln2NRV5PZweqA$> Please see our privacy statement at https://www.adva.com/en/about-us/legal/privacy-statement for details of how ADVA processes personal information. |
|
From: Larry H. <lh...@gm...> - 2020-12-14 15:48:46
|
I am no expert, but do deal with creating and deleting SNMP v3 users in my job. You may have to use the tool, snmpuser to remove V3 users without restarting the snmpd daemon. >From the man page: " *snmpusm* is an SNMP application that can be used to do simple maintenance on the users known to an SNMP agent, by manipulating the agent's User-based Security Module (USM) table. The user needs write access to the usmUserTable MIB table. This tool can be used to create, delete, clone, and change the passphrase of users configured on a running SNMP agent." On Sat, Dec 12, 2020 at 9:55 PM chandrasekharreddy chinnapareddygari < cha...@ho...> wrote: > Hi team, > I'm using net-snmp 5.8 version .My requirement is conf files should updtae > without restarting snmpd . > > I'm sending SIGHUP signal to update SNMP data with out restarting snmpd . > snmpv3 details are not updating . > Please help me how to proceed further. > > > Thanks, > Chandra. > > > > Get Outlook for Android <https://aka.ms/ghei36> > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > |
|
From: chandrasekharreddy c. <cha...@ho...> - 2020-12-13 03:54:16
|
Hi team, I'm using net-snmp 5.8 version .My requirement is conf files should updtae without restarting snmpd . I'm sending SIGHUP signal to update SNMP data with out restarting snmpd . snmpv3 details are not updating . Please help me how to proceed further. Thanks, Chandra. Get Outlook for Android<https://aka.ms/ghei36> |
|
From: chandrasekharreddy c <cha...@ho...> - 2020-12-13 03:51:00
|
Hi team, I'm using net-snmp 5.8 version .My requirement is conf files should updtae without restarting snmpd . I'm sending SIGHUP signal to update SNMP data with out restarting snmpd . snmpv3 details are not updating . Please help me how to proceed further. Thanks, Chandra. Get Outlook for Android<https://aka.ms/ghei36> |
|
From: SURYA T S <sur...@gm...> - 2020-12-09 08:57:57
|
Hi Team,
I am getting snmpd crash with below trace, during a system boot, or
snmp restart with config changes.
I am having netsnm version 5.7.2 running in my box.
Trace 1.
==========
Core was generated by `/usr/sbin/snmpd -Lo0-6d -f -x
/var/agentx/master_VRF_1 -p /var/run/openvswitch/'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007efc9524cf41 in snmp_sess_read2
(sessp=sessp@entry=0x7efc93cd2040, fdset=fdset@entry=0x7ffd4e23ef00)
at /usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:6200
6200 if (rc && pss->s_snmp_errno) {
(gdb) bt full
#0 0x00007efc9524cf41 in snmp_sess_read2
(sessp=sessp@entry=0x7efc93cd2040, fdset=fdset@entry=0x7ffd4e23ef00)
at /usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:6200
psl = 0x7efc93cd2040
pss = 0x0
rc = -1
#1 0x00007efc9524cf8b in snmp_read2 (fdset=0x7ffd4e23ef00) at
/usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:5799
slp = 0x7efc93cd2040
#2 0x0000000000403ff5 in ?? ()
No symbol table info available.
#3 0x00007efc94e88740 in __libc_start_main (main=0x402600, argc=7,
argv=0x7ffd4e23f1c8, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>,
stack_end=0x7ffd4e23f1b8) at
/usr/src/debug/glibc/2.23-r0/git/csu/libc-start.c:289
self = <optimized out>
result = <optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0,
-9062587388492096986, 4210992, 140725914431936, 0, 0,
9061704306574383654, 9205939935531391526},
mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x4043f0,
0x7ffd4e23f1c8}, data = {prev = 0x0, cleanup = 0x0, canceltype =
4211696}}}
not_first_call = <optimized out>
#4 0x0000000000404159 in ?? ()
No symbol table info available.
Trace 2:
=======
Core was generated by `/usr/sbin/snmpd -Lo0-6d -f -x
/var/agentx/master_swns -p /var/run/openvswitch/s'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 _sess_read (sessp=sessp@entry=0xa1,
fdset=fdset@entry=0xffffe9265ea0) at
/usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:5825
5825 netsnmp_transport *transport = slp ? slp->transport : NULL;
(gdb) bt
#0 _sess_read (sessp=sessp@entry=0xa1,
fdset=fdset@entry=0xffffe9265ea0) at
/usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:5825
#1 0x0000ffff9ee3769c in snmp_sess_read2 (sessp=sessp@entry=0xa1,
fdset=fdset@entry=0xffffe9265ea0) at
/usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:6206
#2 0x0000ffff9ee376f4 in snmp_read2 (fdset=0xffffe9265ea0) at
/usr/src/debug/net-snmp/5.7.2-r1/net-snmp-5.7.2/snmplib/snmp_api.c:5808
#3 0x0000000000404584 in ?? ()
This issue is not continously reproducible but seeing intermittently,
when snmp agent/subagent restarts, and snmpwalk happens in the
background.
Please help me understand the issue further and help me with the
patch/ if this issue is already taken care in the upstream.
Thanks,
Surya
|
|
From: Feroz <fer...@gm...> - 2020-12-08 07:13:28
|
Hi,
Im using net-snmp 5.7.2.
I want to forward V3 INFORM's from VM1 to VM2.
snmptrapd crashed while forwarding V3 INFORM.
For my user case I have to run snmptrapd on both VM1 and VM2.
VM1 will receive INFORM/TRAP and forward it to VM2.
>From VM1 when I send link-up INFORM to localhost, snmptrapd crashes on VM1.
(Refer failure logs below)
I guess I'm missing some thing in the snmptrapd.conf file's. Tried adding
"enginID" on VM2, but that didnt worked.
Note: Forwardnig V3 TRAP's works with out any issue.
Here is my configuration:
**VM1:**
root@Ubuntu3323:~# cat /tmp/snmptrapd.conf
authCommunity log,net public
snmpTrapdAddr udp:162,udp6:162
forward default 2.2.2.2:162
createUser feroz SHA feroz123 DES feroz123
authUser log,net feroz priv
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:50:56:96:61:75
inet addr:2.2.2.3 Bcast:2.2.2.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fe96:6175/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:311 errors:0 dropped:72 overruns:0 frame:0
TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:23507 (23.5 KB) TX bytes:12265 (12.2 KB)
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~# snmptrapd -v
NET-SNMP Version: 5.7.2
Web: http://www.net-snmp.org/
Email: net...@li...
root@Ubuntu3323:~# /usr/sbin/snmptrapd -f -C -c /tmp/snmptrapd.conf -Lo -d
-Dusm,snmptrapd,sess_async_send &
root@Ubuntu3323:~# snmpinform -Ci -v 3 -a SHA -A feroz123 -x DES -X
feroz123 -l authPriv -u feroz localhost 0 IF-MIB::linkUp
**VM2**
root@Ubuntu3322:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:50:56:96:ba:0c
inet addr:2.2.2.2 Bcast:2.2.2.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fe96:ba0c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:546 errors:0 dropped:92 overruns:0 frame:0
TX packets:227 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:51478 (51.4 KB) TX bytes:27986 (27.9 KB)
root@Ubuntu3322:~#
root@Ubuntu3322:~# cat /tmp/snmptrapd.conf
createUser feroz SHA feroz123 DES feroz123
authUser log feroz priv
root@Ubuntu3322:~#
root@Ubuntu3322:~#
root@Ubuntu3322:~# /usr/sbin/snmptrapd -f -C -c /tmp/snmptrapd.conf -d -Lo
-Dusm,snmptrapd
registered debug token usm, 1
**CRASH LOGS**
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~# /usr/sbin/snmptrapd -f -C -c /tmp/snmptrapd.conf -Lo -d
-Dusm,snmptrapd,sess_async_send &
[1] 5065
root@Ubuntu3323:~# registered debug token usm, 1
registered debug token snmptrapd, 1
registered debug token sess_async_send, 1
snmptrapd: Freeing trap handler lists
usmUser: created a new user feroz at 80 00 1F 88 80 D9 2A E1 43 83 55 CE 5F
00 00 00
00
NET-SNMP version 5.7.2
root@Ubuntu3323:~# snmpinform -Ci -v 3 -a SHA -A feroz123 -x DES -X
feroz123 -l authPriv -u feroz localhost 0 IF-MIB::linkUp
Received 81 byte packet from UDP: [127.0.0.1]:37270->[127.0.0.1]:162
0000: 30 4F 02 01 03 30 11 02 04 1C 3E BC 53 02 03 00 0O...0....>.S...
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 25 04 11 80 00 ..........0%....
0048: 1F 88 80 F5 3B 97 25 4D FE CD 5F 00 00 00 00 04 ....;.%M.._.....
0064: 00 A0 0E 02 04 06 5C 6E 91 02 01 00 02 01 00 30 ......\n.......0
0080: 00 .
usm: USM processing begun...
usm: Unknown Engine ID.
usm: USM processing has begun (offset 56)
usm: getting user
usm: USM processing completed.
Sending 115 bytes to UDP: [127.0.0.1]:37270->[127.0.0.1]:162
0000: 30 71 02 01 03 30 11 02 04 1C 3E BC 53 02 03 00 0q...0....>.S...
0016: FF E3 04 01 00 02 01 03 04 21 30 1F 04 11 80 00 .........!0.....
0032: 1F 88 80 D9 2A E1 43 83 55 CE 5F 00 00 00 00 02 ....*.C.U._.....
0048: 01 01 02 01 04 04 00 04 00 04 00 30 36 04 11 80 ...........06...
0064: 00 1F 88 80 D9 2A E1 43 83 55 CE 5F 00 00 00 00 .....*.C.U._....
0080: 04 00 A8 1F 02 04 06 5C 6E 91 02 01 00 02 01 00 .......\n.......
0096: 30 11 30 0F 06 0A 2B 06 01 06 03 0F 01 01 04 00 0.0...+.........
0112: 41 01 01 A..
Received 167 byte packet from UDP: [127.0.0.1]:37270->[127.0.0.1]:162
0000: 30 81 A4 02 01 03 30 11 02 04 1C 3E BC 52 02 03 0.....0....>.R..
0016: 00 FF E3 04 01 07 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 D9 2A E1 43 83 55 CE 5F 00 00 00 00 .....*.C.U._....
0048: 02 01 01 02 01 04 04 05 66 65 72 6F 7A 04 0C C4 ........feroz...
0064: B8 BB A8 04 02 A2 CA E7 68 89 AB 04 08 00 00 00 ........h.......
0080: 18 EA B6 F8 AF 04 50 00 32 68 04 1D 36 24 54 29 ......P.2h..6$T)
0096: 0A 84 B9 A8 A8 BE D4 0E D0 29 A6 9E 2C DD 85 54 .........)..,..T
0112: D5 2A D4 64 B8 03 12 5B 3E 89 AC 1D 4A 04 09 B4 .*.d...[>...J...
0128: 5B B2 74 FA F2 3C 1C CA 22 E5 27 A9 AF F1 7E 42 [.t..<..".'...~B
0144: 66 2E A9 3D 6F 82 71 F8 8C 92 A9 9A C2 25 97 0B f..=o.q......%..
0160: 3C 00 FD B3 CD A4 D9 <......
usm: USM processing begun...
usm: match on user feroz
usm: Verification succeeded.
usm: USM processing completed.
snmptrapd: input: a6
snmptrapd: Trap OID: IF-MIB::linkUp
snmptrapd: Running auth trap handlers
snmptrapd:auth: Comparing auth types: result=0, request=0, result=1
snmptrapd:auth: Calling VACM for checking phase 0:read
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 1:write
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 2:notify
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 3:log
snmptrapd:auth: result: authorized
snmptrapd:auth: Calling VACM for checking phase 4:execute
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 5:net
snmptrapd:auth: result: authorized
snmptrapd:auth: Calling VACM for checking phase 6:(null)
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 7:(null)
snmptrapd:auth: result: not authorized
snmptrapd:auth: Final bitmask auth: 28
snmptrapd: Running pre-global trap handlers
snmptrapd:auth: Comparing auth types: result=40, request=8, result=1
snmptrapd: print_handler
snmptrapd: v2/3 format
2020-12-07 08:17:11 localhost [UDP: [127.0.0.1]:37270->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp
snmptrapd: Running trap specific handlers
snmptrapd:lookup: Looking up Trap OID: IF-MIB::linkUp
snmptrapd:lookup: get_traphandler default (0x2002b00)
snmptrapd:auth: Comparing auth types: result=40, request=32, result=1
snmptrapd: forward_handler (2.2.2.2:162)
usm: potentially bootstrapping the USM table from session data
usm: getting user
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 21 B3 06 28 02 03 00 0>...0...!..(...
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 09 79 67 C3 02 01 00 02 01 00 30 00 .....yg.......0.
Received 115 byte packet from UDP: [2.2.2.2]:162->[0.0.0.0]:54017
0000: 30 71 02 01 03 30 11 02 04 21 B3 06 28 02 03 00 0q...0...!..(...
0016: FF E3 04 01 00 02 01 03 04 21 30 1F 04 11 80 00 .........!0.....
0032: 1F 88 80 83 3E 1C 6F 6C 55 CE 5F 00 00 00 00 02 ....>.olU._.....
0048: 01 01 02 01 26 04 00 04 00 04 00 30 36 04 11 80 ....&......06...
0064: 00 1F 88 80 83 3E 1C 6F 6C 55 CE 5F 00 00 00 00 .....>.olU._....
0080: 04 00 A8 1F 02 04 09 79 67 C3 02 01 00 02 01 00 .......yg.......
0096: 30 11 30 0F 06 0A 2B 06 01 06 03 0F 01 01 04 00 0.0...+.........
0112: 41 01 03 A..
usm: USM processing begun...
usm: USM processing completed.
usm: potentially bootstrapping the USM table from session data
usm: USM processing has begun (offset 79)
usm: Encryption successful.
usm: USM processing completed.
Sending 167 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 81 A4 02 01 03 30 11 02 04 1C 3E BC 52 02 03 0.....0....>.R..
0016: 00 FF E3 04 01 07 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 D9 2A E1 43 83 55 CE 5F 00 00 00 00 .....*.C.U._....
0048: 02 01 01 02 01 04 04 05 66 65 72 6F 7A 04 0C 90 ........feroz...
0064: AF AB 6D D8 B1 AE C9 14 97 A8 AD 04 08 00 00 00 ..m.............
0080: 01 1B A4 5C BF 04 50 AC 89 91 EC DE 90 46 4D 20 ...\..P......FM
0096: 05 86 A8 5A 6E D3 24 DE 22 D2 8E 6E 6D DD AD 51 ...Zn.$."..nm..Q
0112: F6 CC F8 06 10 AA 05 C4 2A E3 B2 BF 69 92 E2 9B ........*...i...
0128: BC 6D 75 40 71 6C 60 B2 E5 48 2A E4 18 A9 DD D8 .mu@ql`..H*.....
0144: 0C 2F C8 9C BB 94 9F FD DA B8 63 5C 62 8B 8C 47 ./........c\b..G
0160: 5C AA 0A FF 96 85 42 \.....B
snmptrapd: Running global handlers
snmptrapd:auth: Comparing auth types: result=40, request=8, result=1
snmptrapd: notification_handler
usm: USM processing has begun (offset 79)
snmpinform: Timeout
[1]+ Segmentation fault (core dumped) /usr/sbin/snmptrapd -f -C -c
/tmp/snmptrapd.conf -Lo -d -Dusm,snmptrapd,sess_async_send
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~#
Sending 167 bytes to UDP: [127.0.0.1]:35038->[127.0.0.1]:162
0000: 30 81 A4 02 01 03 30 11 02 04 66 67 CF 5C 02 03 0.....0...fg.\..
0016: 00 FF E3 04 01 03 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 10 B1 C3 57 AE 4E CE 5F 00 00 00 00 .......W.N._....
0048: 02 01 01 02 01 23 04 05 66 65 72 6F 7A 04 0C 0A .....#..feroz...
0064: D3 35 8E 3E 0C 12 50 07 A4 8B 51 04 08 00 00 00 .5.>..P...Q.....
0080: 01 64 2C B4 A3 04 50 B7 7B 7F 09 F5 4D F1 2B 82 .d,...P.{...M.+.
0096: 77 96 E2 34 7C 73 DC 18 1F 03 31 5D 19 12 E7 08 w..4|s....1]....
0112: D8 F5 18 11 86 79 4B E5 21 06 92 CF 84 E3 2C 58 .....yK.!.....,X
0128: 1C F2 24 E2 6D E0 BA 2B 3A 40 52 0E C3 F3 E1 56 ..$.m..+:@R....V
0144: 05 24 E1 72 7E C7 F8 C9 68 5A 64 1A E3 1D 03 E1 .$.r~...hZd.....
0160: 3D 08 FF 5C B5 0D 85 =..\...
Received 167 byte packet from UDP: [127.0.0.1]:35038->[127.0.0.1]:162
0000: 30 81 A4 02 01 03 30 11 02 04 66 67 CF 5D 02 03 0.....0...fg.]..
0016: 00 FF E3 04 01 07 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 10 B1 C3 57 AE 4E CE 5F 00 00 00 00 .......W.N._....
0048: 02 01 01 02 01 0F 04 05 66 65 72 6F 7A 04 0C AB ........feroz...
0064: 1B DD F6 25 0E DE E1 FB B4 63 7B 04 08 00 00 00 ...%.....c{.....
0080: 13 61 87 59 E8 04 50 6D D2 4D 66 16 DF E9 62 A0 .a.Y..Pm.Mf...b.
0096: 94 D2 E5 4C 40 39 AD 07 1D F4 E6 BA AB E0 82 11 ...L@9..........
0112: 44 9C AF BD EC A5 47 DE 15 8F 16 1C E0 0B AE 52 D.....G........R
0128: B7 82 F3 FF F6 D8 51 AF B9 BD FF 90 51 A5 AA 20 ......Q.....Q..
0144: 9D 16 C8 8A 61 7A 98 4F 52 9A 2A 6D F7 4B 2E CA ....az.OR.*m.K..
0160: CC E6 F9 9D A4 5F 1A ....._.
usm: USM processing begun...
usm: match on user feroz
usm: Verification succeeded.
usm: USM processing completed.
snmptrapd: input: a6
snmptrapd: Trap OID: IF-MIB::linkUp
snmptrapd: Running auth trap handlers
snmptrapd:auth: Comparing auth types: result=40, request=0, result=1
snmptrapd:auth: Calling VACM for checking phase 0:read
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 1:write
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 2:notify
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 3:log
snmptrapd:auth: result: authorized
snmptrapd:auth: Calling VACM for checking phase 4:execute
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 5:net
snmptrapd:auth: result: authorized
snmptrapd:auth: Calling VACM for checking phase 6:(null)
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 7:(null)
snmptrapd:auth: result: not authorized
snmptrapd:auth: Final bitmask auth: 28
snmptrapd: Running pre-global trap handlers
snmptrapd:auth: Comparing auth types: result=40, request=8, result=1
snmptrapd: print_handler
snmptrapd: v2/3 format
2020-12-07 07:48:32 localhost [UDP: [127.0.0.1]:35038->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp
snmptrapd: Running trap specific handlers
snmptrapd:lookup: Looking up Trap OID: IF-MIB::linkUp
snmptrapd:lookup: get_traphandler default (0x10b4b00)
snmptrapd:auth: Comparing auth types: result=40, request=32, result=1
snmptrapd: forward_handler (2.2.2.2:162)
usm: potentially bootstrapping the USM table from session data
usm: getting user
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 99 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AB 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 9A 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AB 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 9B 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AB 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 9C 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AB 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 9D 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AB 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 9E 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AB 02 01 00 02 01 00 30 00 ...._.^.......0.
Forward failed: Timeout
snmptrapd: Running global handlers
snmptrapd:auth: Comparing auth types: result=40, request=8, result=1
snmptrapd: notification_handler
usm: USM processing has begun (offset 79)
usm: Encryption successful.
usm: USM processing completed.
Sending 167 bytes to UDP: [127.0.0.1]:35038->[127.0.0.1]:162
0000: 30 81 A4 02 01 03 30 11 02 04 66 67 CF 5D 02 03 0.....0...fg.]..
0016: 00 FF E3 04 01 03 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 10 B1 C3 57 AE 4E CE 5F 00 00 00 00 .......W.N._....
0048: 02 01 01 02 01 29 04 05 66 65 72 6F 7A 04 0C BC .....)..feroz...
0064: 8B 54 35 C1 F3 3F 79 FA FC 0D 35 04 08 00 00 00 .T5..?y...5.....
0080: 01 64 2C B4 A4 04 50 EA BD A9 AF 5F 55 3A D3 F3 .d,...P...._U:..
0096: BC 37 FC B1 E1 D3 89 C4 EC AB 19 BC 6F 57 64 8F .7..........oWd.
0112: FC 87 7D B8 BB 78 C4 50 78 0F F2 F4 7C A6 BE 57 ..}..x.Px...|..W
0128: E3 3D A6 53 F2 CC 9B 94 B9 CA 09 15 16 64 B5 59 .=.S.........d.Y
0144: DA 44 58 AE AB 8B 57 70 56 FB 72 C3 88 17 35 AC .DX...WpV.r...5.
0160: 11 D4 0C C9 5A 95 C3 ....Z..
Received 167 byte packet from UDP: [127.0.0.1]:35038->[127.0.0.1]:162
0000: 30 81 A4 02 01 03 30 11 02 04 66 67 CF 5E 02 03 0.....0...fg.^..
0016: 00 FF E3 04 01 07 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 10 B1 C3 57 AE 4E CE 5F 00 00 00 00 .......W.N._....
0048: 02 01 01 02 01 10 04 05 66 65 72 6F 7A 04 0C 33 ........feroz..3
0064: C2 D0 2E EF 34 C9 98 3D 47 47 14 04 08 00 00 00 ....4..=GG......
0080: 13 61 87 59 E9 04 50 6B C0 0F 46 6C B4 A3 48 91 .a.Y..Pk..Fl..H.
0096: 70 AE 75 A6 7C 74 1D 66 12 C3 65 59 8B E6 CB 7E p.u.|t.f..eY...~
0112: 78 1B B9 E7 B0 02 44 39 46 11 76 08 A5 69 79 77 x.....D9F.v..iyw
0128: 17 7D 8C BB 9D B9 E0 3E BC 8D 05 69 67 C8 2B A4 .}.....>...ig.+.
0144: DB 1D 78 B1 41 6E DE 52 96 F8 BB 65 D2 1A E8 0A ..x.An.R...e....
0160: 3D 3C 60 F7 3C CB 86 =<`.<..
usm: USM processing begun...
usm: match on user feroz
usm: Verification succeeded.
usm: USM processing completed.
snmptrapd: input: a6
snmptrapd: Trap OID: IF-MIB::linkUp
snmptrapd: Running auth trap handlers
snmptrapd:auth: Comparing auth types: result=40, request=0, result=1
snmptrapd:auth: Calling VACM for checking phase 0:read
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 1:write
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 2:notify
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 3:log
snmptrapd:auth: result: authorized
snmptrapd:auth: Calling VACM for checking phase 4:execute
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 5:net
snmptrapd:auth: result: authorized
snmptrapd:auth: Calling VACM for checking phase 6:(null)
snmptrapd:auth: result: not authorized
snmptrapd:auth: Calling VACM for checking phase 7:(null)
snmptrapd:auth: result: not authorized
snmptrapd:auth: Final bitmask auth: 28
snmptrapd: Running pre-global trap handlers
snmptrapd:auth: Comparing auth types: result=40, request=8, result=1
snmptrapd: print_handler
snmptrapd: v2/3 format
2020-12-07 07:48:38 localhost [UDP: [127.0.0.1]:35038->[127.0.0.1]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (0) 0:00:00.00
SNMPv2-MIB::snmpTrapOID.0 = OID: IF-MIB::linkUp
snmptrapd: Running trap specific handlers
snmptrapd:lookup: Looking up Trap OID: IF-MIB::linkUp
snmptrapd:lookup: get_traphandler default (0x10b4b00)
snmptrapd:auth: Comparing auth types: result=40, request=32, result=1
snmptrapd: forward_handler (2.2.2.2:162)
usm: potentially bootstrapping the USM table from session data
usm: getting user
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 9F 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AC 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 A0 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AC 02 01 00 02 01 00 30 00 ...._.^.......0.
usm: USM processing has begun (offset 22)
usm: getting user
usm: Failed to find engine data.
usm: USM processing completed.
Sending 64 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 3E 02 01 03 30 11 02 04 0B C8 44 A1 02 03 00 0>...0.....D....
0016: FF E3 04 01 04 02 01 03 04 10 30 0E 04 00 02 01 ..........0.....
0032: 00 02 01 00 04 00 04 00 04 00 30 14 04 00 04 00 ..........0.....
0048: A0 0E 02 04 5F 1C 5E AC 02 01 00 02 01 00 30 00 ...._.^.......0.
Received 115 byte packet from UDP: [2.2.2.2]:162->[0.0.0.0]:32924
0000: 30 71 02 01 03 30 11 02 04 0B C8 44 A1 02 03 00 0q...0.....D....
0016: FF E3 04 01 00 02 01 03 04 21 30 1F 04 11 80 00 .........!0.....
0032: 1F 88 80 7D B4 C8 4B E2 4E CE 5F 00 00 00 00 02 ...}..K.N._.....
0048: 01 01 02 01 00 04 00 04 00 04 00 30 36 04 11 80 ...........06...
0064: 00 1F 88 80 7D B4 C8 4B E2 4E CE 5F 00 00 00 00 ....}..K.N._....
0080: 04 00 A8 1F 02 04 5F 1C 5E AC 02 01 00 02 01 00 ......_.^.......
0096: 30 11 30 0F 06 0A 2B 06 01 06 03 0F 01 01 04 00 0.0...+.........
0112: 41 01 01 A..
usm: USM processing begun...
usm: USM processing completed.
usm: potentially bootstrapping the USM table from session data
usm: USM processing has begun (offset 79)
usm: Encryption successful.
usm: USM processing completed.
Sending 167 bytes to UDP: [2.2.2.2]:162->[0.0.0.0]:0
0000: 30 81 A4 02 01 03 30 11 02 04 66 67 CF 5E 02 03 0.....0...fg.^..
0016: 00 FF E3 04 01 07 02 01 03 04 3A 30 38 04 11 80 ..........:08...
0032: 00 1F 88 80 10 B1 C3 57 AE 4E CE 5F 00 00 00 00 .......W.N._....
0048: 02 01 01 02 01 2B 04 05 66 65 72 6F 7A 04 0C 6B .....+..feroz..k
0064: 96 6B 77 09 CA 14 0D BD 3F 44 4E 04 08 00 00 00 .kw.....?DN.....
0080: 01 64 2C B4 A5 04 50 A0 36 6F 33 46 4B C4 A7 3D .d,...P.6o3FK..=
0096: 93 40 CA 77 A5 6B 3E 98 66 FC 4B D1 5A 65 69 68 .@.w.k>.f.K.Zeih
0112: 25 EB B8 C2 50 66 3B D4 FB 24 56 C7 1F 48 F0 70 %...Pf;..$V..H.p
0128: 60 61 B1 7D B1 6A 18 F2 DE 93 83 65 61 C2 60 CE `a.}.j.....ea.`.
0144: 07 75 E3 9D B2 8A AC 15 5F C7 62 6E E0 E5 96 6C .u......_.bn...l
0160: 30 FE A2 55 6A DA BB 0..Uj..
snmptrapd: Running global handlers
snmptrapd:auth: Comparing auth types: result=40, request=8, result=1
snmptrapd: notification_handler
usm: USM processing has begun (offset 79)
usm: Failed to find engine data.
[1]+ Segmentation fault (core dumped) /usr/sbin/snmptrapd -f -C -c
/tmp/snmptrapd.conf -Lo -d -Dusm,snmptrapd,sess_async_send
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~#
root@Ubuntu3323:~#
--
Regards,
Feroz Ahmed
|
|
From: Oezer, J. K (J. C. U. (USA) <jos...@na...> - 2020-12-02 20:59:28
|
Craig, Thank you for the detailed response. This does help out a lot. Regards, Josh Oezer PMA-290 P-8 EWSP Deputy Team Lead PMA-290 P-8 Acting MCDS Team Lead PMA-290 P-8 MCDS Lead Engineer SIPR: <mailto:jos...@na...> jos...@na... (advise email delivery on NIPR) (219) 241-2750 (cell) From: Craig Small <csmall@dropbear.xyz> Sent: Tuesday, December 1, 2020 5:43 PM To: Oezer, Joshua K (Josh) CTR USN (USA) <jos...@na...> Cc: net...@li...; Kirkwood, Robert D CIV USN COMNAVAIRSYSCOM PAX (USA) <Rob...@na...>; Higgins, Dorothy A CIV USN NAS PAX MD (USA) <dor...@na...> Subject: [Non-DoD Source] Re: net-snmp-5.5.0-2.x64.exe Questions Hello Josh, I am only the Debian packager of net-snmp not the "owner" of the software. In fact it would be difficult to get one voice on the "owner" as there are many including several organisations. So, this is coming from a non-US citizen who hasn't written a line of net-snmp but has written other open source for a few decades and was around when DFSG (which OSI definition is based upon) was being formed. net-snmp is licensed with multiple different types of licenses, as seen in the COPYING file[1]. The licenses can be broken down into several types: BSD-LIKE - Very close to a standard BSD 3-clause BSD 3 Clause - Your standard BSD 3 Clause[2] The perl directory uses Artistic-1.0[3] or GPL-2.0+[4] All of these licenses are OSI approved which means they follow the open source definition[5]. The item you are probably most interested in is item 6 "The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research." Software could restrict its use from certain organisations (such as the US government) or it could be open source. It cannot be both at the same time. So, as net-snmp is open-source, it is permitted to be used by anyone. Finally the classification. Again this is difficult because there isn't really the concept of a data owner here. Most places have the concept of taking in public data and then classifying it, such as downloading a PDF off a public website. I'm surprised the USN hasn't a policy on this; or perhaps it does and the trick is finding it. As much as my opinion means anything, all data on the net-snmp website is UNCLASSIFIED. It really cannot be anything else! - Craig 1: https://github.com/net-snmp/net-snmp/blob/master/COPYING <https://no-click.mil/?https://github.com/net-snmp/net-snmp/blob/master/COPYING> 2: https://opensource.org/licenses/BSD-3-Clause <https://no-click.mil/?https://opensource.org/licenses/BSD-3-Clause> 3: https://opensource.org/licenses/Artistic-1.0 <https://no-click.mil/?https://opensource.org/licenses/Artistic-1.0> 4: https://opensource.org/licenses/GPL-2.0 <https://no-click.mil/?https://opensource.org/licenses/GPL-2.0> 5: https://opensource.org/osd-annotated <https://no-click.mil/?https://opensource.org/osd-annotated> On Wed, 2 Dec 2020 at 02:23, Oezer, Joshua K (Josh) CTR USN (USA) <jos...@na... <mailto:jos...@na...> > wrote: Good afternoon, I am following up on the below email. Has your organization had time to review the below questions? Thank you. Regards, Josh Oezer PMA-290 P-8 EWSP Deputy Team Lead PMA-290 P-8 Acting MCDS Team Lead PMA-290 P-8 MCDS Lead Engineer SIPR: <mailto:jos...@na...> jos...@na... (advise email delivery on NIPR) (219) 241-2750 (cell) From: Oezer, Joshua K (Josh) CTR USN (USA) Sent: Monday, October 26, 2020 9:29 AM To: net...@li... <mailto:net...@li...> Cc: Higgins, Dorothy A CIV USN NAS PAX MD (USA) <dor...@na... <mailto:dor...@na...> >; Kirkwood, Robert D CIV USN COMNAVAIRSYSCOM PAX (USA) <Rob...@na... <mailto:Rob...@na...> > Subject: net-snmp-5.5.0-2.x64.exe Questions Good morning, My name is Josh Oezer, I am the team lead and lead engineer on the Mission Computing and Display Systems team for the U.S. Navy with PMA-290. The USN requires net-snmp-5.5.0-2.x64.exe binary installation on its maintenance laptops to communicate with certain equipment. Reading the license agreements, I did not see anything that did not permit use of net-SNMP by the US Government. However, I would like to request approval for use from net-SNMP to ensure we are not crossing any legal boundaries with your software. In addition to the requested approval for use, can you please verify that the software is UNCALSSIFIED (for our documentation)? Thank you for your assistance. Regards, Josh Oezer PMA-290 P-8 EWSP Deputy Team Lead PMA-290 P-8 Acting MCDS Team Lead PMA-290 P-8 MCDS Lead Engineer SIPR: jos...@na... <mailto:jos...@na...> (advise email delivery on NIPR) (219) 241-2750 (cell) _______________________________________________ Net-snmp-coders mailing list Net...@li... <mailto:Net...@li...> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders <https://no-click.mil/?https://lists.sourceforge.net/lists/listinfo/net-snmp-coders> On Wed, 2 Dec 2020 at 02:23, Oezer, Joshua K (Josh) CTR USN (USA) <jos...@na... <mailto:jos...@na...> > wrote: Good afternoon, I am following up on the below email. Has your organization had time to review the below questions? Thank you. Regards, Josh Oezer PMA-290 P-8 EWSP Deputy Team Lead PMA-290 P-8 Acting MCDS Team Lead PMA-290 P-8 MCDS Lead Engineer SIPR: <mailto:jos...@na...> jos...@na... (advise email delivery on NIPR) (219) 241-2750 (cell) From: Oezer, Joshua K (Josh) CTR USN (USA) Sent: Monday, October 26, 2020 9:29 AM To: net...@li... <mailto:net...@li...> Cc: Higgins, Dorothy A CIV USN NAS PAX MD (USA) <dor...@na... <mailto:dor...@na...> >; Kirkwood, Robert D CIV USN COMNAVAIRSYSCOM PAX (USA) <Rob...@na... <mailto:Rob...@na...> > Subject: net-snmp-5.5.0-2.x64.exe Questions Good morning, My name is Josh Oezer, I am the team lead and lead engineer on the Mission Computing and Display Systems team for the U.S. Navy with PMA-290. The USN requires net-snmp-5.5.0-2.x64.exe binary installation on its maintenance laptops to communicate with certain equipment. Reading the license agreements, I did not see anything that did not permit use of net-SNMP by the US Government. However, I would like to request approval for use from net-SNMP to ensure we are not crossing any legal boundaries with your software. In addition to the requested approval for use, can you please verify that the software is UNCALSSIFIED (for our documentation)? Thank you for your assistance. Regards, Josh Oezer PMA-290 P-8 EWSP Deputy Team Lead PMA-290 P-8 Acting MCDS Team Lead PMA-290 P-8 MCDS Lead Engineer SIPR: jos...@na... <mailto:jos...@na...> (advise email delivery on NIPR) (219) 241-2750 (cell) _______________________________________________ Net-snmp-coders mailing list Net...@li... <mailto:Net...@li...> https://lists.sourceforge.net/lists/listinfo/net-snmp-coders <https://no-click.mil/?https://lists.sourceforge.net/lists/listinfo/net-snmp-coders> |
|
From: Wes H. <har...@us...> - 2020-12-02 18:47:48
|
Deepak Sachan <sac...@gm...> writes: > But when i run one snmpset for all oids e.g > snmpset oid1 value1 oid2 value2 oid3 value3 oid4 value4 > i received repeated (4 to 5 times)set request for each oid. The snmp implementation and agentx protocols work by sending multiple SET "phases" to ensure that the entire transaction can be successfully handled or all reverted if not. Thus there are two reservation steps indicated by the action being performed at the time (RESERVE1 and RESERVE2) that are passed to your code to ensure you can actually do something. You should read this page that describes some of the states and how processing is done: http://www.net-snmp.org/wiki/index.php/Agent_Modes -- Wes Hardaker Please mail all replies to net...@li... |
|
From: Wes H. <har...@us...> - 2020-12-02 18:37:21
|
Hi Josh, I'm the original founder of the Net-SNMP project, but I'm not a lawyer. Craig pretty much nailed the analysis perfectly in my opinion: > net-snmp is licensed with multiple different types of licenses, as seen in the > COPYING file[1]. The licenses can be broken down into several types: > BSD-LIKE - Very close to a standard BSD 3-clause > BSD 3 Clause - Your standard BSD 3 Clause[2] > The perl directory uses Artistic-1.0[3] or GPL-2.0+[4] Open source projects can be difficult to analyze fully because they're contributed to by a large number of people. We've required that all contributions to the project fall within the BSD license, as pointed at above. Some perl code is included that falls under the perl license, as Craig pointed out. > Reading the license agreements, I did not see anything that did > not permit use of net-SNMP by the US Government. However, I would > like to request approval for use from net-SNMP to ensure we are > not crossing any legal boundaries with your software. I can solidly verify that Net-SNMP is used in multiple places by multiple governments, including the U.S. government. In fact, some of the features within Net-SNMP came from government funded research contracts. > In addition to the requested approval for use, can you please > verify that the software is UNCALSSIFIED (for our documentation)? Nothing in Net-SNMP's documentation or code has ever been classified by any government. -- Wes Hardaker Please mail all replies to net...@li... |
|
From: Craig S. <cs...@dr...> - 2020-12-01 23:09:07
|
Hello Josh, I am only the Debian packager of net-snmp not the "owner" of the software. In fact it would be difficult to get one voice on the "owner" as there are many including several organisations. So, this is coming from a non-US citizen who hasn't written a line of net-snmp but has written other open source for a few decades and was around when DFSG (which OSI definition is based upon) was being formed. net-snmp is licensed with multiple different types of licenses, as seen in the COPYING file[1]. The licenses can be broken down into several types: BSD-LIKE - Very close to a standard BSD 3-clause BSD 3 Clause - Your standard BSD 3 Clause[2] The perl directory uses Artistic-1.0[3] or GPL-2.0+[4] All of these licenses are OSI approved which means they follow the open source definition[5]. The item you are probably most interested in is item 6 "The license must not restrict anyone from making use of the program in a specific field of endeavor. For example, it may not restrict the program from being used in a business, or from being used for genetic research." Software could restrict its use from certain organisations (such as the US government) or it could be open source. It cannot be both at the same time. So, as net-snmp is open-source, it is permitted to be used by anyone. Finally the classification. Again this is difficult because there isn't really the concept of a data owner here. Most places have the concept of taking in public data and then classifying it, such as downloading a PDF off a public website. I'm surprised the USN hasn't a policy on this; or perhaps it does and the trick is finding it. As much as my opinion means anything, all data on the net-snmp website is UNCLASSIFIED. It really cannot be anything else! - Craig 1: https://github.com/net-snmp/net-snmp/blob/master/COPYING 2: https://opensource.org/licenses/BSD-3-Clause 3: https://opensource.org/licenses/Artistic-1.0 4: https://opensource.org/licenses/GPL-2.0 5: https://opensource.org/osd-annotated On Wed, 2 Dec 2020 at 02:23, Oezer, Joshua K (Josh) CTR USN (USA) < jos...@na...> wrote: > Good afternoon, > > I am following up on the below email. Has your organization had time to > review the below questions? > > Thank you. > > > > Regards, > > Josh Oezer > > PMA-290 P-8 EWSP Deputy Team Lead > > PMA-290 P-8 Acting MCDS Team Lead > > PMA-290 P-8 MCDS Lead Engineer > > SIPR: jos...@na... (advise email delivery on NIPR) > > (219) 241-2750 (cell) > > > > *From:* Oezer, Joshua K (Josh) CTR USN (USA) > *Sent:* Monday, October 26, 2020 9:29 AM > *To:* net...@li... > *Cc:* Higgins, Dorothy A CIV USN NAS PAX MD (USA) < > dor...@na...>; Kirkwood, Robert D CIV USN COMNAVAIRSYSCOM PAX > (USA) <Rob...@na...> > *Subject:* net-snmp-5.5.0-2.x64.exe Questions > > > > Good morning, > > My name is Josh Oezer, I am the team lead and lead engineer on the Mission > Computing and Display Systems team for the U.S. Navy with PMA-290. > > The USN requires net-snmp-5.5.0-2.x64.exe binary installation on its > maintenance laptops to communicate with certain equipment. > > Reading the license agreements, I did not see anything that did not permit > use of net-SNMP by the US Government. However, I would like to request > approval for use from net-SNMP to ensure we are not crossing any legal > boundaries with your software. > > In addition to the requested approval for use, can you please verify that > the software is UNCALSSIFIED (for our documentation)? > > Thank you for your assistance. > > > > Regards, > > Josh Oezer > > PMA-290 P-8 EWSP Deputy Team Lead > > PMA-290 P-8 Acting MCDS Team Lead > > PMA-290 P-8 MCDS Lead Engineer > > SIPR: jos...@na... (advise email delivery on NIPR) > > (219) 241-2750 (cell) > > > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > On Wed, 2 Dec 2020 at 02:23, Oezer, Joshua K (Josh) CTR USN (USA) < jos...@na...> wrote: > Good afternoon, > > I am following up on the below email. Has your organization had time to > review the below questions? > > Thank you. > > > > Regards, > > Josh Oezer > > PMA-290 P-8 EWSP Deputy Team Lead > > PMA-290 P-8 Acting MCDS Team Lead > > PMA-290 P-8 MCDS Lead Engineer > > SIPR: jos...@na... (advise email delivery on NIPR) > > (219) 241-2750 (cell) > > > > *From:* Oezer, Joshua K (Josh) CTR USN (USA) > *Sent:* Monday, October 26, 2020 9:29 AM > *To:* net...@li... > *Cc:* Higgins, Dorothy A CIV USN NAS PAX MD (USA) < > dor...@na...>; Kirkwood, Robert D CIV USN COMNAVAIRSYSCOM PAX > (USA) <Rob...@na...> > *Subject:* net-snmp-5.5.0-2.x64.exe Questions > > > > Good morning, > > My name is Josh Oezer, I am the team lead and lead engineer on the Mission > Computing and Display Systems team for the U.S. Navy with PMA-290. > > The USN requires net-snmp-5.5.0-2.x64.exe binary installation on its > maintenance laptops to communicate with certain equipment. > > Reading the license agreements, I did not see anything that did not permit > use of net-SNMP by the US Government. However, I would like to request > approval for use from net-SNMP to ensure we are not crossing any legal > boundaries with your software. > > In addition to the requested approval for use, can you please verify that > the software is UNCALSSIFIED (for our documentation)? > > Thank you for your assistance. > > > > Regards, > > Josh Oezer > > PMA-290 P-8 EWSP Deputy Team Lead > > PMA-290 P-8 Acting MCDS Team Lead > > PMA-290 P-8 MCDS Lead Engineer > > SIPR: jos...@na... (advise email delivery on NIPR) > > (219) 241-2750 (cell) > > > _______________________________________________ > Net-snmp-coders mailing list > Net...@li... > https://lists.sourceforge.net/lists/listinfo/net-snmp-coders > |
|
From: SURYA T S <sur...@gm...> - 2020-12-01 06:15:27
|
Hi Team I am trying snmp trap and inform with the V3 version. snmpv3 trap is working for me when I configured agent[switch] local engine id[0x80000b8503e0071bc9413c], in snmptrapd.conf of my workstation/vm(host) [switch]agent-netsnmp 5.8 ---------------------- [vm]host-netsnmp 5.7.2 SNMP TRAP (working) ============ [switch] cat /var/net-snmp/snmptrapd-swns.conf authCommunity log,net public snmpTrapdAddr udp:162,udp6:162 forward default 10.1.1.2:162 createUser -e 0x80000b8503e0071bc9413c abc process running /usr/sbin/snmptrapd -f -C -c /var/net-snmp/snmptrapd-swns.conf -Lo -d -Dusm,snmptrapd -p /var/run/openvswitch/snmptrapd-swns.pid [vm] cat snmptrapd.conf createUser -e 0x80000b8503e0071bc9413c authUser log,net abc process running (sudo snmptrapd -f -Lo -c snmptrapd.conf) snmp inform:(not working) =============== When i tried inform with remote-engine-id, I am getting error as below 2020-11-27T09:43:33.938004+00:00 usm: USM processing begun... 2020-11-27T09:43:33.938159+00:00 usm: Unknown Engine ID. 2020-11-27T09:43:33.938261+00:00 usm: USM processing has begun (offset 53) 2020-11-27T09:43:33.938357+00:00 usm: getting user abc 2020-11-27T09:43:33.938480+00:00 usm: match on user abc 2020-11-27T09:43:33.938610+00:00 usm: no match on engineID (80 00 1F 88 80 96 7F B4 57 30 CA C0 5F 00 00 00 2020-11-27T09:43:33.938732+00:00 : 00 ) what should be the remote-engineid configured in agent? How to make netsnmp to take remote-engine-id from snmptrapd.conf than the one its autogenerating. how should i modify snmptrapd.conf in agent and host to make snmp inform working [switch] cat /var/net-snmp/snmptrapd-swns.conf authCommunity log,net public snmpTrapdAddr udp:162,udp6:162 forward default 10.1.1.2:162 createUser -e 0x121314151617 authuser log,net abc /usr/sbin/snmptrapd -f -C -c /var/net-snmp/snmptrapd-swns.conf -Lo -d -Dusm,snmptrapd -p /var/run/openvswitch/snmptrapd-swns.pid User created logs: 2020-11-27T09:43:33.938610+00:00 usmUser: created a new user abc at 12 13 14 15 16 17 Error logs: 2020-11-27T09:43:33.938610+00:00 usm: no match on engineID (80 00 1F 88 80 C5 B4 89 01 0B DC C0 5F 00 00 00: 00 ) [vm] root@Ubuntu3325:~# cat snmptrapd.conf engineId 0x121314151617 createUser -e 0x121314151617 abc authUser log,net abc sudo snmptrapd -f -Lo -c snmptrapd.conf -d -Dusm,snmptrapd sudo: unable to resolve host Ubuntu3325 registered debug token usm, 1 registered debug token snmptrapd, 1 snmptrapd: Freeing trap handler lists usmUser: created a new user abc at 12 13 14 15 16 17 NET-SNMP version 5.7.2 Please help me on how to use remote-engine-id in snmptrapd.conf and snmpd.conf, to send snmpv3 informs successfully, Thanks, Surya |
|
From: SURYA T S <sur...@gm...> - 2020-11-27 16:40:25
|
I am trying snmp trap and inform with the V3 version. snmpv3 trap is working for me when I configured agent local engine id[0x80000b8503e0071bc9413c], in snmptrapd.conf of my workstation/vm(host) [switch]agent-netsnmp 5.8 ---------------------- [vm]host-netsnmp 5.7.2 SNMP TRAP >>>> working ============ [switch] cat /var/net-snmp/snmptrapd-swns.conf authCommunity log,net public snmpTrapdAddr udp:162,udp6:162 forward default 10.1.1.2:162 createUser -e 0x80000b8503e0071bc9413c abc process running /usr/sbin/snmptrapd -f -C -c /var/net-snmp/snmptrapd-swns.conf -Lo -d -Dusm,snmptrapd -p /var/run/openvswitch/snmptrapd-swns.pid [vm] cat snmptrapd.conf createUser -e 0x80000b8503e0071bc9413c authUser log,net abc process running (sudo snmptrapd -f -Lo -c snmptrapd.conf) snmp inform:>>>>>not working =============== When i tried inform with remote-engine-id, I am getting error as below 2020-11-27T09:43:33.938004+00:00 usm: USM processing begun... 2020-11-27T09:43:33.938159+00:00 usm: Unknown Engine ID. 2020-11-27T09:43:33.938261+00:00 usm: USM processing has begun (offset 53) 2020-11-27T09:43:33.938357+00:00 usm: getting user abc 2020-11-27T09:43:33.938480+00:00 usm: match on user abc 2020-11-27T09:43:33.938610+00:00 usm: no match on engineID (80 00 1F 88 80 96 7F B4 57 30 CA C0 5F 00 00 00 2020-11-27T09:43:33.938732+00:00 : 00 ) what should be the remote-engineid configured in agent? How to get remote-engine-id? how should i modify snmptrapd.conf in agent and host to make snmp inform working [switch] cat /var/net-snmp/snmptrapd-swns.conf authCommunity log,net public snmpTrapdAddr udp:162,udp6:162 forward default 10.1.1.2:162 createUser -e 0x121314151617 authuser log,net abc /usr/sbin/snmptrapd -f -C -c /var/net-snmp/snmptrapd-swns.conf -Lo -d -Dusm,snmptrapd -p /var/run/openvswitch/snmptrapd-swns.pid User created logs: 2020-11-27T09:43:33.938610+00:00 usmUser: created a new user abc at 12 13 14 15 16 17 Error logs: 2020-11-27T09:43:33.938610+00:00 usm: no match on engineID (80 00 1F 88 80 C5 B4 89 01 0B DC C0 5F 00 00 00: 00 ) [vm] root@Ubuntu3325:~# cat snmptrapd.conf engineId 0x121314151617 createUser -e 0x121314151617 abc authUser log,net abc sudo snmptrapd -f -Lo -c snmptrapd.conf -d -Dusm,snmptrapd sudo: unable to resolve host Ubuntu3325 registered debug token usm, 1 registered debug token snmptrapd, 1 snmptrapd: Freeing trap handler lists usmUser: created a new user abc at 12 13 14 15 16 17 NET-SNMP version 5.7.2 Please help me on how to get remote-engine-id, and snmptrapd.conf file creation, to send snmpv3 informs successfully, Thanks, Surya |
|
From: SURYA T S <sur...@gm...> - 2020-11-27 11:13:40
|
SURYA T S has sent you an email via Gmail confidential mode: [image: Gmail logo]snmpv3 inform remote-engine-id and snmptrapd.conf <https://confidential-mail.google.com/msg/AF-DAF219uxZUHyR3O1Yft843cAG70bLD2bhIK2YPgl82fsVdDWn-CfkTv4I95zu1L2zN12tsm-5F7TU8g9RyuAyrqhRbKDACtjVFk5sRkcc8J91NHMqU6rqUwwV7Ph5YlxHdIov9JLzXv6257_0znCeCsd9Pt5hUpl-a-08os8=> This message was sent on Nov 27, 2020 at 3:13:29 AM PST You can open it by clicking the link below. This link will only work for net...@li.... View the email <https://confidential-mail.google.com/msg/AF-DAF219uxZUHyR3O1Yft843cAG70bLD2bhIK2YPgl82fsVdDWn-CfkTv4I95zu1L2zN12tsm-5F7TU8g9RyuAyrqhRbKDACtjVFk5sRkcc8J91NHMqU6rqUwwV7Ph5YlxHdIov9JLzXv6257_0znCeCsd9Pt5hUpl-a-08os8=> Gmail confidential mode gives you more control over the messages you send. The sender may have chosen to set an expiration time, disable printing or forwarding, or track access to this message. Learn more <https://support.google.com/mail/answer/7674059> Gmail: Email by Google Use is subject to the Google Privacy Policy <https://myaccount.google.com/privacypolicy?hl=en> Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA You have received this message because someone sent you an email via Gmail confidential mode. [image: Google logo] |
|
From: Wes H. <har...@us...> - 2020-11-17 23:56:51
|
chandrasekharreddy chinnapareddygari <cha...@ho...> writes: > I want to include/ use external library is n net-snmp 5.8. > Please help me to use external library. Use the --with-libs configure script option. -- Wes Hardaker Please mail all replies to net...@li... |
|
From: chandrasekharreddy c. <cha...@ho...> - 2020-11-17 15:31:26
|
Hi all, I want to include/ use external library is n net-snmp 5.8. Please help me to use external library. Get Outlook for Android<https://aka.ms/ghei36> |
|
From: Philippe G. <phi...@6w...> - 2020-11-17 09:32:48
|
Hi Wes, Thanks a lot for reply, The design proposal does not change the single threading model put in place on subagent Agentx side. As I read your email and the RFC deeper, you may refer to transaction ID that is self to a single SNMP management request, and that may not be somehow "interrupted". I assume that those locks do not deal with separate MIB contexts on the same session. What about adding some restrictions in the use case I depicted earlier ? - A registered MIB entity should not be shared across more than one connection. I think this would mean that a SNMP management request would never be "interrupted" by an other SNMP management request on the same context. This check could be done when parsing the configuration. agentxsocket unix:/var/run/netns/test/agentx_snmpd name1,name2,name3 agentxsocket unix:/var/run/netns/test2/agentx_snmpd name1 <--- would be refused because name1 already previously attached agentxsocket unix:/var/run/netns/test3/agentx_snmpd name4,name5,name6 <--- would be accepted In fact, in proposed model, I assume I have multiple agentx connections sharing the same process memory, but not sharing same objects, sessions. Regards, Philippe On Fri, Nov 13, 2020 at 12:51 AM Wes Hardaker < har...@us...> wrote: > Philippe Guibert <phi...@6w...> writes: > > > Thanks for letting me know if that approach should be considered or > > not, > > Personally, I'll have to think a lot about it. But in general, agentx > was designed (and if you haven't read the RFC for it, you probably > should to get a better understanding of the protocol's design). > > Specifically, there needs to be locking issues in the subagent to > consider when attached to multiple upstream parent agents. SNMP SETs, > in particular, go through a multi-phase transition to ensure you can > safely perform and/or undo a SET. Right now, that handling is done in > the parent agent to ensure that only one SET is handled at a time. > > > I suspect there are some other issues to think about too. > > -- > Wes Hardaker > Please mail all replies to net...@li... > |
|
From: Wes H. <har...@us...> - 2020-11-12 23:52:04
|
Philippe Guibert <phi...@6w...> writes: > Thanks for letting me know if that approach should be considered or > not, Personally, I'll have to think a lot about it. But in general, agentx was designed (and if you haven't read the RFC for it, you probably should to get a better understanding of the protocol's design). Specifically, there needs to be locking issues in the subagent to consider when attached to multiple upstream parent agents. SNMP SETs, in particular, go through a multi-phase transition to ensure you can safely perform and/or undo a SET. Right now, that handling is done in the parent agent to ensure that only one SET is handled at a time. I suspect there are some other issues to think about too. -- Wes Hardaker Please mail all replies to net...@li... |
|
From: Philippe G. <phi...@6w...> - 2020-11-09 16:23:30
|
Hi all, adding some clarifications on the proposed design I would like to propose: The use case should cover two cases. Each case is exclusive of the other. a- stick one MIB to one connection. use case with multiple connections. b- stick several MIB in one connection. use case with single connection. The following is proposed: - extend agentx subagent code to multiple sessions a linked list of config sessions is created indexed by agentxsocket path the sub agent code is modified accordingly. at registration/unregistration of the session, a reference is done between netsnmp_session and config_netsnmp_session. at shutdown, the config session can be flushed based on the agentxsocket path too. example of config file: agentxsocket unix:/var/run/netns/test/agentx_snmpd [..] agentxsocket unix:/var/run/netns/test2/agentx_snmpd - add a linked list to the config sessions. that contains the list of mib contexts names. example of config file that could be applied for a) case: agentxsocket unix:/var/run/netns/test/agentx_snmpd name1 example of config file that could be applied for b) case: agentxsocket unix:/var/run/netns/test/agentx_snmpd name1,name2,name3 The advantage of using the config session list, is that there is no need to modify netsnmp_session. MIB (un)registration would be filtered by comparing the MIB registration name with the list of MIB names configured. The same would be done to check if a trap is eligible or not to a netsnmp_session or not. Thanks for letting me know if that approach should be considered or not, Thanks & Regards, Philippe On Fri, Nov 6, 2020 at 11:52 AM Philippe Guibert <phi...@6w...> wrote: > Hi all, > > I am in progress of implementing more than one parent agent for one agentX. > The problem I try to solve is that I have multiple MIB with same OID but > different vrfs. > > Do you have any proposals on how to stick MIBs to one dedicated parent > connection ? > From the sub agent trap code, I can see that a trap is supposed to be sent > to all pending connections, but I think this is not what should be done by > default ? > Thanks, > > Regards, > Philippe > > > On Tue, Oct 13, 2020 at 5:49 PM Wes Hardaker < > har...@us...> wrote: > >> Philippe Guibert <phi...@6w...> writes: >> >> > Instead of using agentX, I wonder if it could be possible to link the >> > application with a master agent library Somehow, the agent would be >> > configured as a proxy, and session would convey information over an >> > unixSocket to the real snmpAgent. Could it be possible ? >> >> Yes, certainly you can have multiple "real" snmp daemons query to a >> sub-process via a proxy like mechanism. There is no reason that >> shouldn't work to allow multiple upstreams query to your internal agent. >> >> The net-snmp package's snmpd actually supports that through the use of >> the "proxy" directive ; see the snmpd.conf manual page in the "Proxy >> Support" section. >> >> -- >> Wes Hardaker >> Please mail all replies to net...@li... >> > |
|
From: Philippe G. <phi...@6w...> - 2020-11-06 10:59:48
|
Hi all, I am in progress of implementing more than one parent agent for one agentX. The problem I try to solve is that I have multiple MIB with same OID but different vrfs. Do you have any proposals on how to stick MIBs to one dedicated parent connection ? >From the sub agent trap code, I can see that a trap is supposed to be sent to all pending connections, but I think this is not what should be done by default ? Thanks, Regards, Philippe On Tue, Oct 13, 2020 at 5:49 PM Wes Hardaker <har...@us...> wrote: > Philippe Guibert <phi...@6w...> writes: > > > Instead of using agentX, I wonder if it could be possible to link the > > application with a master agent library Somehow, the agent would be > > configured as a proxy, and session would convey information over an > > unixSocket to the real snmpAgent. Could it be possible ? > > Yes, certainly you can have multiple "real" snmp daemons query to a > sub-process via a proxy like mechanism. There is no reason that > shouldn't work to allow multiple upstreams query to your internal agent. > > The net-snmp package's snmpd actually supports that through the use of > the "proxy" directive ; see the snmpd.conf manual page in the "Proxy > Support" section. > > -- > Wes Hardaker > Please mail all replies to net...@li... > |
|
From: Wes H. <har...@us...> - 2020-11-04 01:04:31
|
Sanjay Kumar <san...@gm...> writes: > Can I assume without this configuration netsnmp is using the OpenSSL > library? It only uses the internal implementation (for just sha1/md5/etc support really) with that flag. You should be able to run ./net-snmp-config --external-libs If it returns -lcrypto in the results then you're linking to an external library. -- Wes Hardaker Please mail all replies to net...@li... |
|
From: Bill F. <fe...@gm...> - 2020-11-03 22:11:25
|
On Mon, Nov 2, 2020 at 9:37 AM Bill Fenner <fe...@gm...> wrote:
> I imagined writing a test that exercises all of the output options (-Of,
> -On, -Os, -OS, -Ou) for both netSnmpExampleAnonymousIntermediateNode
> and netSnmpExamples.42.1. Does anyone have any other suggestions of what
> to test?
>
I accidentally stumbled across this bug in my proposed change with -OX
output: if a late index element translates to a string (e.g., a
PhysicalAddress), and an earlier element is a TimeTicks (or its
representation otherwise has a period in it), the output would be
MODULE-NAME::00][string] (the "00" is the part of [0.00] after the dot..)
- I'm looking for brainstorming about other crazy corner cases like this.
(Concretely, this was
snmptranslate -OX
ARISTA-BRIDGE-EXT-MIB::aristaDot1qTpFdbNumMoves.1.42.40.41.42.43.44.45
ARISTA-BRIDGE-EXT-MIB::01][42][STRING: 28:29:2a:2b:2c:2d]
where the right output was
ARISTA-BRIDGE-EXT-MIB::aristaDot1qTpFdbNumMoves[0:00:00.01][42][STRING:
28:29:2a:2b:2c:2d]
where the INDEX was { aristaDot1qTpFdbTimeMark, dot1qFdbId,
dot1qTpFdbAddress } )
(This doesn't *require* -OX, once I identified the bug, it required "the
representation of the index contained a period followed by a letter",
so Q-BRIDGE-MIB::dot1qTpFdbAddress.42.40.41.42.43.46.66 => Q-BRIDGE-MIB::B'
instead of Q-BRIDGE-MIB::dot1qTpFdbAddress.42.'()*+.B'...)
Bill
|
475 messages has been excluded from this view by a project administrator.
