Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • The -s0 option is important too: it makes tcpdump grab the whole package and not just the protocol headers at the beginning of each package. Commented Apr 4, 2018 at 19:25
  • Thanks! I hurried with answer but I know about it. I will fixed it in answer. Commented Apr 4, 2018 at 19:34
  • I want to take/see that trap command(to reproduce) literally from wireshark trace. Can I see that with -s0? Commented Apr 4, 2018 at 21:41
  • With -s0 you will see all trace from wireshark. If you want to trace from Wireshark directly, you may use this filter on chosen interface: snmp and ((udp.dstport==162) or (udp.srcport==161) or (udp.dstport==161)) and (ip.addr==142.125.248.36). Commented Apr 4, 2018 at 21:59
  • Problem is, trap generated from device is not working but my validation trap with those varbinds, is working. Can the traces help me rebuild the exact snmp-trap command that device sends? Commented Apr 5, 2018 at 1:09