For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

amit_128525's avatar
amit_128525
Icon for Nimbostratus rankNimbostratus
Dec 17, 2013

tcpdump f5

hello , I was trying to understand below syntax on F5 10.2.4 if anyone can help please tcpdump -e -nnn -i and tcpdump -e -nni

 

7 Replies

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Amit,

     

    -e shows layer2 info (mac addresses etc.)

     

    -i is interface (tcpdump -i 0.0)

     

    -nnn means don't resolve hostnames or ports (makes tcpdump quicker)

     

    Hope this helps,

     

    N

     

  • i gave below command without -i it worked , i expected it should ask for -i if i am specifying interface eth0 ?

     

    tcpdump -e -s0 -nni eth0 host 1.1.1.1

     

  • nathe's avatar
    nathe
    Icon for Cirrocumulus rankCirrocumulus

    Nothing, you can use -nnni or -nnn -i as far as I understand.

     

  • i gave below command without -i it worked , i expected it should ask for -i if i am specifying interface eth0 ?

     

    tcpdump -e -s0 -nni eth0 host 1.1.1.1

     

  • what does "s0" in the syntax mean? I was looking for something like a filter (source and destination only). I think I need a decent step by step on how to dump to screen or ftp it off the device. thanks in advance
  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus

    From running "man tcpdump":

     

    ...

     

    -s Snarf snaplen bytes of data from each packet rather than the default of 68 (with SunOS’s NIT, the minimum is actually 96). 68 bytes is adequate for IP, ICMP, TCP and UDP but may truncate protocol information from name server and NFS packets (see below). Packets truncated because of a limited snapshot are indicated in the output with ‘‘[|proto]’’, where proto is the name of the protocol level at which the truncation has occurred. Note that taking larger snapshots both increases the amount of time it takes to process packets and, effectively, decreases the amount of packet buffering. This may cause packets to be lost. You should limit snaplen to the smallest number that will capture the protocol information you’re interested in. Setting snaplen to 0 means use the required length to catch whole packets.