Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-users: Re: [Wireshark-users] How to use a "wireshark sniffer PC" to capture ftp flows b

Date: Fri, 22 Feb 2013 14:25:48 +0000
There are lots of options for doing this, you might want to start by looking at this
http://wiki.wireshark.org/CaptureSetup/Ethernet#Switched_Ethernet

You could do the route option but that seems to add a lot of complexity and will change your packet flow which may work against why you are capturing in the first place.

Hope that helps


-----Original Message-----
From: wireshark-users-bounces@xxxxxxxxxxxxx [mailto:wireshark-users-bounces@xxxxxxxxxxxxx] On Behalf Of AMEAUME, ALAIN (ALAIN)** CTR **
Sent: Friday, February 22, 2013 8:55 AM
To: Community support list for Wireshark
Subject: [Wireshark-users] How to use a "wireshark sniffer PC" to capture ftp flows between 2 terminals located on 2 # sub-networks ?

Hi users,

I'm interesting to know how to insert my PC laptop with wireshark as a" PC sniffer" between 2 terminals to capture ftp flows between them:

terminal "A" in sub-network x.y.A.1
terminal "B" in sub-network x.y.B.1
my PC laptop "C" on sub-network x.y.A.2 or x.y.B.2

using this configuration, I do not need to install wireshark on A & B !

I suppose that on "A" terminal I need to create a route from A.1 to B.1 passing thru "C", the same relatively to "B", then I will need also to declare on my laptop "C" a kind of "gateway" function to re-route the ftp flow, after capture, to its original destination  Is it what we call the NAT function on "C": and how to do it on the "C" laptop windows xp sp3 ?

Thanks for your help.

Alain
___________________________________________________________________________
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