Riverbed Cascade Pilot Personal Edition: Take Wireshark to the Next Level - Advanced Triggers and Alerts; Web and VoIP Analytics; Long-Term Trending and Forensics; Deep Packet Analysis with Wireshark

Wireshark-users: Re: [Wireshark-users] tcpdump command

Date Index Thread Index Other Months All Mailing Lists

Date Prev Date Next Thread Prev Thread Next

From: M Holt <m.iostreams@xxxxxxxxx>
Date: Thu, 5 Mar 2009 12:30:37 -0800

Specifying port 8080 twice is redundant, you need only add this once time.
Other than that, it should work fine. Usually, I specify a file extension, but you don't have to:

tcpdump -w /var/tmp/mydump.dmp -i eth0 -s0 host 172.20.0.14 and host 172.20.0.15 and port 8080

Hope that helps.
Mike

On Thu, Mar 5, 2009 at 4:11 AM, Kaushal Shriyan <kaushalshriyan@xxxxxxxxx> wrote:

Hi,

is this below command correct ?

tcpdump -i eth0 -s 0 -w noroutehostdump host 172.20.0.14 and port 8080 and host 172.20.0.15 and port 8080

Actually i want to capture packets originating from host 172.20.0.14 through 8080 and destination host 172.20.0.15 to port 8080

Please suggest

Expecting your earnest reply

Thanks and Regards

Kaushal

___________________________________________________________________________
Sent via: Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives: http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe

References:
- [Wireshark-users] tcpdump command
  - From: Kaushal Shriyan

Prev by Date: [Wireshark-users] tcpdump command
Next by Date: [Wireshark-users] How to compile Wireshark for 64-bit Windows Vista Home Premium and 64-bit Windows 7 beta
Previous by thread: [Wireshark-users] tcpdump command
Next by thread: [Wireshark-users] How to compile Wireshark for 64-bit Windows Vista Home Premium and 64-bit Windows 7 beta
Index(es):
- Date
- Thread