YouTube Instagram TikTok How it works FAQ

The fastest way to turn talking videos into clean, searchable text. Free, private and no account required.

About

Built by Rishav Raj with one goal: free transcripts for everyone.

rishav@yttotranscript.com

Transcribe

YouTube to text
YouTube with timestamps
Instagram Reels
TikTok videos

Learn

How it works
FAQ
YouTube transcripts guide

More

Chrome extension
Contact
Privacy policy
Terms of service

© 2026 YTtoTranscript. Made for creators & researchers.

Not affiliated with YouTube, Instagram or TikTok. Respect creators’ copyright.

How to Capture Traffic in Wireshark — Transcript · YTtoTranscript

Home/Transcripts/YouTube

YouTube Transcript

How to Capture Traffic in Wireshark

Plaintext Packets · 2,296 words · 11 min read · EN-ORIG

Watch on YouTube

Share X LinkedIn WhatsApp

Below is the complete, readable transcript of How to Capture Traffic in Wireshark by Plaintext Packets on YouTube. Read the full text, copy any part you need, or generate a transcript for any video with our free tool.

Network troubleshooting using wire shark all right so today we're going to cover something really simple and straight forward for anyone there who's new to Wi shark in packet analysis and that's how to actually perform a data capture in wire shark now uh wi has two main functionalities one is to actually analyze existing capture files and two

is to actually take captures meaning from a PC or a server to actually allow you to capture the traffic coming in and out of an interface so to keep things simple we're going to go through just two things one is how to select the right interface to capture from and how to start the

capture and two what is the difference between a capture filter and a display filter because when I was learning wi shark no one really explained this really well and I just want to take a minute to explain that so in our scenario here let's say that I want to capture all the traffic on this PC now

what does that mean um every computer that is networked has at least one interface which it uses to connect to that Network so let's say for example this PC has a physical ethernet connection to the local router at home okay um and let's say this PC has a connection to this router here now if I

want to do a capture from this PC right the first thing I need to know is what interface uh do I want to capture from because some computers will only have one interface say it's like this interface here uh and some computers will have multiple you know a computer can have a physical interface can also

have a wireless interface to connect to Wi-Fi right um but what you're capturing when you do that is all traffic going in and out of that interface right um when it's not capturing for example if I capture on this PC I'm not going to get the traffic that is destined to this PC

Transcribe another video

Paste any YouTube, Instagram or TikTok link to get a free transcript.

Free · No sign-up · Unlimited

Add to Chrome — transcribe in one click

um I'm only get the traffic that's going to and from this one up here and it seems like an obvious thing but I get this question a lot in the comments of like well how do I capture traffic from someone else well this tutorial is not going to show you that this is just

going to show you uh a scenario where you have access to this PC and you're going to capture traffic from it so say you're troubleshooting an issue at work or at home uh from your PC and you need to take the capture so you can analyze it later or send it to someone this is

how you would do it okay so interface selection is is number one now um this router likely has a connection to the Internet so the traffic you'll see coming out of say the physical interface here will be uh traffic to the router to the Internet so anything going to the internet and if

this PC is communicating with other PCS on the network you'll see that as well okay so that's the first point I want to make so we're over here in wire shark now and you'll realize really quickly why I mentioned men the importance of selecting the right interface the PC I'm doing this video from has multiple

interfaces including uh looks like four ethernet Connections three local a connections an ethernet connection it's got a Bluetooth adapter on there and it's got an adapter for loop back which is a kind of more advanced topic now I know for a fact that uh my computer is connected via Ethernet cable to the

router right I like to connect over ethernet via Wi-Fi so I know from before this video that that's the case if you didn't know that was the case there's a couple of ways that you can figure that out um the first and probably the most easiest way is that wi shark has this

little traffic graph here that shows you the status of how much traffic is going in and out of that interface at any given time right so if I wanted to say um uh figure out okay okay I got traffic here and I got traffic here which one of these is actually one that is generating

the traffic for me what I can do is run a uh like download like I go to the internet and download some traffic and you'll see that the graph starts to pick up um for now I know that this is ethernet but there's a couple of ways that you can do that worst case scenario

do trial and error and capture from multiples um you could also do a shift select and capture multiple interfaces at once this is only really useful if you're actually using those interfaces in my scenario I'm not actually using Bluetooth and these connections here are all logic IC interfaces um which is a more advanced

topic but they're not really used so the only one that actually sends data in and out right now is this ethernet adapter so the first step select the interface that you want to capture traffic from it's simple enough um the second thing is and I'm actually going to bleed into my second point about capture filters

and display filters is this thing up here called a capture filter now before I get to that what I'm going to do is I'm not going to do anything else I'm going to select ethernet I'm going to hit go the shark icon and right away what I'm going to see is a whole bunch of traffic even if

I'm not actually doing anything on the internet even if I'm not downloading or uh playing games or whatever my computer is always in constant communication any computer is in this Modern Age with internet services with things like Microsoft with things like Google there's lots and lots of background processes on your machine that are

connect to the web and that's what's going on here right um I also have things like a webcam running on the server all that kind of stuff so this is your first indication that you got something right if you start seeing traffic come in like this right um I'm going to pause it I'm going to

stop and this has stopped all traffic or all captures or traffic being captured this hasn't stopped traffic to my server right traffic is still going on I just don't want to capture any more of it into a file and if I want want to I can go through now and just verify okay well

my IP address I know 10143 that sounds about right what I can do is open up a command prompt let's just move it over here and do a IP config and I can tell that 10143 is indeed the IP address of my adapter and I can actually make sure it's the ethernet adapter so I'm on the

right track this kind of capture is known as a wide open Capture a wide open Capture is a capture where you want all traffic coming in and out of the server to be captured into this file okay um whether it's ip4 IPv6 whether it's TCP or UDP regardless of the protocol everything coming in and out is going to be

captured now this is a really good uh technique when say you're investigating an issue and you really don't know where the issue is you don't know what port the issue is with like what protocol you don't know what application it's with you don't know um much about the details you just know there's some kind of

network issue or suspected Network issue so capturing wide open allows you to do things like you know I'm going to analyze um all the all the conversations let's Pok in and you can see you know things like um oh wow there's let's see there's a lot of pockets going to this IP what is that about it's more an

investigative mode now the downside of doing a wide open Capture give me a sec while I fix my screens the downside is that the file size can be huge because ultimately you're not stopping any of the traffic you're from the door you're laying it all in so if I was doing this say um on a file server that's like

actively providing a lot of uh downloads to users this this file would fill up you know in maybe a few minutes maybe a few seconds if it's a really busy server okay um so wide open is really good if you can do it remember that in wi shark if the file gets over I would say 4 to

500 megabytes even on a good computer wi shark is going to have a lot of difficulty actually displaying it and analyzing it so you want to make sure your your file size doesn't get too huge so that takes me to the second piece of this which is how to use a capture filter now I'm back to the wire shark

launch screen and I'm going to show you now how to do a capture filter now as I mentioned sometimes you have a scenario where you really want to filter down and only capture traffic of Interest like traffic as part of an investigation and that's really for the most part to preserve file size to do that you use a

capture filter which effectively says I only want to capture the traffic that matches this filter the benefit like I mentioned is you can reduce file size the downside is that all that other traffic that's going in and out of the server at this time you're going to miss and you need to do

another capture later to in order to get that that's wide open so you may need to figure out what's appropriate for the scenario but the capture filter syntax is pretty simple if you need to U wi.org has a great reference for this you could even use chat GPT and ask it how do I

filter traffic and wire shark for certain things with a cap capture filter but as a simple example I could do something like uh UDP Port 53 now for those of you who know UDP Port 53 is DNS so what I'm telling wi shark is that I only want to see the DNS traffic coming

in and out of my computer and I'm going to hit enter and right away you can tell the volume of packets that I'm actually capturing in this file is much less than before and in fact we can confirm that this is all DNS because wi strik is telling us it's DNS Okay so if you're

doing an investigation and you know for certain like say for example you're having an issue with your DNS server and you know for certain that the issue is a DNS protocol issue then you can start you can use a capture filter run this capture and actually run it for a lot longer than if you were capturing DNS

plus everything else on the machine right um some additional examples let's just close this out do one more example with you let's say TCP port uh 4 for3 uh that's https or TLS and same thing now we switch from DNS to TLS and TCP if you want it you can just pick a packet

confirm that in this case the destination ports 443 um but that's effectively it right you filter down to just what you need and that way you keep the file size at a reasonable size or at least less large than it would be if you did a wide open open okay my preference um especially when I'm troubleshooting

let me just pull up my diagram one more time my preference is if I'm starting an investigation from scratch U and I don't know anything about the network or about what's going on or what's causing something I start with a wi open Capture capture everything coming out of this pipe okay what I can do though is put limits on

the file size um or later on after I've downloaded the file I can actually cut it up which I'll do a video on that later but do it wide open and then poke around look at all the conversations look at what's going on and then once I know what the fault domain is like

what's actually at stake like say it's it is a DNS problem or say it's a problem connecting to the internet on Port 80 right uh on a certain application then I would then Implement a capture filter capture again and then let it run for a longer time so I have more data that's it for this video if you

have any questions about wi shark or networking feel free to post it in the comments we can chat about it there or you can always send me the capture file to take a look at I have a DropBox that I'll send you to send the file I've also got a Discord server now so you can

check it out that channel and join to do the same post questions about networking issues you're working on at work etc and as always please like And subscribe to support the channel until next time