Return to Question

Minor style fixes.

On redhat linux box, am I am trying to trace the snmpsnmp traps coming from IP a.b.c.dIP a.b.c.d, as shown below:

sudo /usr/sbin/tcpdump src host 142.125.248.36 and udp dst port 162 -w /home/user1/troubleshoot.pcap

sudo /usr/sbin/tcpdump src host 142.125.248.36 and udp dst port 162 -w /home/user1/troubleshoot.pcap

and store the traces in /home/user1/troubleshoot.pcap.

Can this syntax go better to get more details about those snmpsnmp traps?

On redhat linux box, am trying to trace the snmp traps coming from IP a.b.c.d, as shown below:

sudo /usr/sbin/tcpdump src host 142.125.248.36 and udp dst port 162 -w /home/user1/troubleshoot.pcap

and store the traces in /home/user1/troubleshoot.pcap.

Can this syntax go better to get more details about those snmp traps?

On redhat linux box, I am trying to trace the snmp traps coming from IP a.b.c.d, as shown below:

sudo /usr/sbin/tcpdump src host 142.125.248.36 and udp dst port 162 -w /home/user1/troubleshoot.pcap

and store the traces in /home/user1/troubleshoot.pcap.

Can this syntax go better to get more details about those snmp traps?

asked Apr 4, 2018 at 16:14

tcpdump tracing UDP packets

On redhat linux box, am trying to trace the snmp traps coming from IP a.b.c.d, as shown below:

sudo /usr/sbin/tcpdump src host 142.125.248.36 and udp dst port 162 -w /home/user1/troubleshoot.pcap

and store the traces in /home/user1/troubleshoot.pcap.

Can this syntax go better to get more details about those snmp traps?