Wireshark Reviews

When we can see in the customer environment that traffic is getting blocked; suppose we have a VPN channel, and when the VPN channel is up but the traffic is not running through it, we use Wireshark to recapture the channel. We check whether the PPP handshake is ongoing or not. The acknowledgment team posts this packet, and after that, the PPP handshake is ongoing or not. 

So these are the things that we check by filtering out the things and based upon that, we get support. Because in five to six seconds, there are more than a thousand packets. So we have to filter out and check on which speed it is getting dropped. For that reason, we are using Wireshark. I am using it just for troubleshooting purposes.

Wireshark is pretty handy. It's especially useful for troubleshooting issues. However, the GUI interface is not that accurate. It can only show a limited amount of information, such as the source code, destination code, and services that are being blocked. If we want to know why a packet is being blocked by a particular policy, we need to check the packet capture.

We also use Wireshark to troubleshoot packet-level inspection issues, such as whether the payload is present, whether the packet size is too large for the receiver, and whether the DMTU (Dynamic Maximum Transmission Unit) is correct. We also use it to troubleshoot issues with fragmented packets.

In addition to the GUI, we also use the developer's tool and the command line to troubleshoot issues with Wireshark. For example, we use the cat and grep commands to filter out the information we need and to turn on debug mode. We also use the tail command to view the current history of logs.

I am currently working in a Linux environment, so I use the SysLog for configuration purposes on the Algo server. I use the TCP system command because Cisco uses port 514. So, I have to use the TCP system command to check whether we are receiving logs from the particular firewall or not.

Customers often tell us that they have open WDP 5144 traffic. They usually show us this in Splunk. For example, they might say, "We are forwarding the packet to the system, but we are not receiving the packet." This is usually because they need to test their end because they require some identity virus for the traffic to flow through our application.

Sometimes, the Algo server goes down, and we have to build it from scratch. Other times, the load distribution unit does not get synced with the primary. These are just some of the things we do on a daily basis with Wireshark.

While Wireshark is useful, the GUI interface is less accurate, showing only limited information.

I have been using Wireshark for three years. 

It is a stable product. I would rate the stability a ten out of ten. Every engineer in our organization uses this solution in our company. So, more than 22 users are using this solution. 

I would rate the scalability a nine out of ten. There is always room for improvement. 

It is easy to scale Wireshark. The GUI is very user-friendly. They have multiple videos online and on YouTube. Going through these resources provides a better understanding of Wireshark, its functionality, and how things operate within it. Essentially, it aligns with what we can learn from fundamental books or authoritative works.  

What we have analyzed on a theoretical basis, like the TCP handshake, SSL handshake, wireless controller handshake, SMTP handshake, and whatever we read in the books, we can technically see it in Wireshark each and every packet. For SSL, we can see multiple streams getting transmitted: server, client hello, client-server hello, then the client where Client Pre-shared. The client ciphers also send the TLS, TLS certificate SSL certificate. Then in the server, we can see the SSL certificate and the Cypress suite, which they want to negotiate on, and then their pre-master secret key, which is generated, and then the session keys are getting generated. So these are all the things that we read in our books; we can see it packet-wise, each and everything. The acknowledgment comes from their end, from the client or the server side. So we can see it is very much easy to use in Wireshark.

Gain practical knowledge of what we comprehend. Analogous to the basic mathematical concept of two plus two, this is a protocol-oriented understanding, similar to the alphabet in language. However, in the realm of networking, Wireshark proves highly beneficial. You can put into practice what you read in books by actively examining and validating it yourself.

Every engineer will always try to make things easy for the customer. S 

Positive

The initial setup depends upon the basics. You need to have a clear understanding of the basics. When you have a clear understanding, there's nothing more difficult for us.

We have deployed it both on the cloud and on-premises. We usually install agents from Google. Everyone cannot use it. At least we need to have a basic understanding of theoretical concepts. Once the theoretical concept is clear, then you can use the packet capture. So it is easy to do packet captures. You need to just check videos on YouTube.

Overall, I would rate the solution a nine out of ten. Just focus on the basics. Once they are clear, you can handle and master any of the products in the secure network market, whether it's switches, routers, firewalls, VPNs, load balancers, or whatever it is. Just focus on the basics of what you want to pursue in your career.

The primary purpose of Wireshark is to monitor network communications. For example, if we need to track our target in order to exploit it, or to understand our use cases, we can use Wireshark for both internal and external penetration testing. We can use Wireshark to capture communication from any IP, and if there is no encryption, we can also use it to retrieve client passwords. This is the main function of the solution.

Wireshark is very user-friendly; even someone with basic IT knowledge can use it. Wireshark has a large user interface and a good graphical user interface. Wireshark has all the features needed, such as sniffing the network, tracking packets, and sorting packets.

Previously, I have used Wireshark in some of the financial companies I have been involved with. For example, when I was employed at a bank, we used Wireshark. However, I have noticed that Wireshark is restricted when any sort of encryption is involved, such as XSL encryption or DLX. This means that Wireshark cannot be used to its full potential. Therefore, I think that Wireshark or the vendors should consider including features to penetrate firewalls and get the data, such as including any hash types.

I would like the ability to sniff user credentials, such as passwords, rather than clear text. Wireshark should be able to sniff basic encryption, such as 128 and 64-bit encryption, as other solutions do.

I have been using the solution for over ten years.

Wireshark is a stable solution.

I rarely need to contact technical support, as most issues can be resolved by looking at the Wireshark questions or FAQs. We can usually find solutions quickly.

Positive

The initial setup is very easy. We can send an executable file, we can just run the solution. Wireshark can be installed on a standalone workstation or if we want to create a server, we can also do that. The deployment takes around 30 minutes.

I give the solution a nine out of ten.

There is a purpose for using Wireshark. If we don't know the purpose or our agenda, then why are we using it? The solution would be useless for us in this case. If we are following an example and are a SOC person, we just need to sniff the communication and confirm that it is stable. However, if we are general IT people and do not know the purpose, then Wireshark would be useless.

Our primary use case of this solution is for wired or wireless sniffing.

I have found the most valuable feature you can design your sniffer the way you want to. As I said, by default it will have all the legacy features or legacy or advanced features. So apart from that in your device, if you have a particular feature that is enabled, then you can modify it by changing the source code. It provides you with the source code. It is an open source so you can get a source code, you just need to create a plugin or API and point it to that source and you compile it.

In the future, it would be nice to see color coding. It is just black and white. 

I have been using Wireshark for the past fifteen years.

The stability is excellent and reflected in the automation integration.

If you are a good programmer everything is available online. There is a community-based option to ask questions and you will get answers.

The initial setup is straightforward. You type in Google or Bing Wireshark download. Then you will be taken to the Wireshark webpage and there is a tab called download. Download the latest stable version that is available. It is an EXE file or an MSF file.

For the initial stages, I prefer Wireshark but after six months to a year, I like to use OmniPeek. Wireshark is very easy to use and I would rate it an eight out of ten.

We're using an internal Wi-Fi card in the laptop, so we configure that particular wireless interface into monitoring mode, configure the channel, and use Wireshark for that specific interface. We can capture the packets and activities on that channel, analyze the packets for poor connections, etc.

What's best about Wireshark is that it doesn't require installation. It supports cards and monitoring permissions and is sufficient for appending and capturing activities. You won't need to install other tools to use Wireshark, so this saves you time. You can capture packets at any time from your laptop through Wireshark.

Wireshark is similar to an OS defense tool, meaning that it runs on an OS such as Ubuntu and Fedora, but I'm unsure if it's compatible with Windows or if it's a straightforward process to run it on Windows. Right now, my team needs to run Wireshark from a dongle to use it, so it's an OS-dependable tool, and that's an area for improvement.

I was unable to use Wireshark on Windows, and I couldn't capture it, as I'm unsure how to configure the wireless card into monitoring mode on Windows. The process was straightforward on Linux, but it wasn't the case on Windows OS. It seems Wireshark isn't compatible with all OS. For example, you can analyze the log, and you can analyze it on the Windows server, but you can't do a capture in Windows. Configuring Wireshark for Windows isn't as easy as configuring it for Linux.

What I'd like to see in the next release of Wireshark is the capability to capture packets from the ethernet.

I started using Wireshark six or seven years ago.

Wireshark is a stable product.

Wireshark is a scalable product.

I never needed to contact technical support for Wireshark.

My company uses Wireshark and has not tried a different solution. The biggest factor on why it decided to use Wireshark is because it's open-source software that doesn't require installation and a license, so anyone can use it.

Wireshark is pretty easy to set up. Its deployment doesn't take much time. It only takes ten to twenty minutes max to complete Wireshark deployment.

Wireshark is an open-source product, so it's free to use.

All people within my company use Wireshark, so that's two hundred users.

My advice to anyone looking into using Wireshark is that you should know how to configure the interface and the internal Wi-Fi card into monitoring mode, so you can capture via Wireshark. As Wireshark is a good tool, I'd recommend it to others, but you should have some knowledge of how to use it and how to configure it. Before implementing Wireshark, you need to know your objectives, working scenarios, what type of features you'd want to implement, and what changes you need to make.

I'd rate Wireshark eight out of ten because for you to configure and use it requires proper knowledge. It's straightforward to use if you have some knowledge of configuring it for monitoring.

I'm a customer of Wireshark.

It's a tool that we use to capture the network and if there is any lag or if there are packet drops.

It's a very useful tool. We are using it to monitor any network depreciation. For example, suppose there's a call going on between two IP phones and one person says that I cannot hear you. There's definitely something wrong. The RTP is getting dropped, and the packets are getting dropped. We need to capture the live call or if there are any prerecord calls for this particular time period. We go ahead and use this tool to find out whether the packets dropped when a packet is dropped and what caused the audio issue or video issue. We actually use it to understand any network issues.

I've been using it for quite some time, and I find that it's very user-friendly. The interface is good. 

The options that are required to get the details for the packet drops are good. All the options are available for whatever is required. I can choose any of them and search easily, and I can also pull the report and publish it to the team or whoever requires it. 

It's easy to set up.

I can't suggest anything as of now regarding Wireshark. I have never found any issues or had any difficulty using it. Be it connecting the system to the network directly and capturing the data through Wireshark, or for a specific time, it's been flawless. I have got the results every time I've needed them. 

You need good network connectivity to download during the setup, otherwise, it might take a while.

I have been using Wireshark for almost six years. I've used it for a while at this point.

The solution is stable. It's reliable. It offers good performance There are no bugs or glitches. It doesn't crash or freeze. 

Almost everybody in our company is using the product. That's likely around 1,000 people. Here, we always work on the network devices, and we need to use this tool to understand if there is any issue with that network or if there is any issue with the calls. Therefore, almost everyone uses it within the network team.

In terms of scalability, if you look at it, there's no limit. There's no restriction on how many users can use it. However, it depends on the organization. If you need any approval to download it usually needs special permission. 

I never had to reach out to technical support regarding Wireshark. Whenever I've had to use it, it worked properly and there was no issue to complain about.

It is easy to set up. We just need to download it and choose the options while setting it up. That's it. After that, it should be done.

The download itself doesn't take a lot of time. It depends on the bandwidth of your network. If you're using a good network connection, then it hardly takes a minute to download.

It is open-source. Anyone can download and use it. 

I use the solution to support my customer's environment. I am not a partner or reseller. 

I'd rate the solution ten out of ten.

Wireshark is more of a packet capture tool. If you are in a network environment, where you are supporting the customer and looking after the issues with network drop, network devices, or IP calls, you must have a Wireshark on your PC. This is a tool that gives you a clear-cut idea about where the issue is, and where the packs are dropping. It's an excellent tool. Everyone should start using it.

Wireshark is a network analyzer used to capture traffic. It's used to analyze patterns in the network to check for any malicious traffic generated from devices or endpoints.

Wireshark is a good tool to start with network analyzing and packet capturing. The solution provides good performance and stability.

The solution’s user interface could be improved.

I have been using Wireshark since 2019.

Wireshark is a stable solution.

Wireshark is not a scalable solution. The tool's purpose is not to scale, and there is no use case to scale it.

The solution’s initial setup is straightforward.

I have deployed Wireshark on my laptop. You need to download the software from the web and then run it. It's free of charge, and there's no license involved. We need to enable the solution and run it to capture the traffic.

Wireshark is free of charge, and there's no license involved.

I would recommend the solution to other users. Wireshark is a good tool to start with network analyzing and packet capturing. You can use Wireshark for packet capturing to find the root cause of any issues in the network.

Overall, I rate the solution an eight out of ten.

I have been using Wireshark for the packet tracing, and it has helped me to find out whatever site, et cetera. It is useful, basically capturing packets of data on the network.

It helps us to identify the source the packet is originating from and it also helps us to know about the return time of the packet from when the packet is going from our computer to when it reaches the destination IP address. It helps diagnose internet connectivity problems and also helps us to know what the website data consists of and how much data is in the website.

And it also helps us to know about the various protocols which are being utilized when we are connecting to the internet. We also get to know what bites, et cetera, are present in our data or if there is any malicious packet that is not supposed to come in. Based on it, we can configure our firewall. 

It's helping me to get to know about the packet data. I'm getting to know about the source destination IP, for example. That's quite useful to me. 

Overall, it's a great product. 

The initial setup is simple. 

It is stable. 

Whenever we select one of the packets, in terms of the number of bytes, for example, there are three planes, and in the detailed plane, I have to count the number of bytes manually. 

Also, sometimes when I'm trying to select the number of bytes, the selection does not go properly. If we were to go on selecting it, the number of bytes also showed up as to how many bytes have been selected in the detailed plane.

I've been using the solution for four months.

It's quite stable. I don't have any issues with Wireshark while running it. There are no bugs or glitches. It doesn't crash or freeze. 

Scalability is good. I can capture as few or as many packets as I want. There's no issue at all. 

That said, I haven't worked on it professionally, so I cannot comment much on that right now from an organizational perspective.

I've never called technical support. I can't speak to how helpful or responsive they are. 

I did not use another similar product before. 

The implementation process is not complex at all. You just have to click on the interface, and your Wireshark starts capturing the packets. 

I'm not aware of the exact pricing. 

I'm an end-user. I'm using it at my college.

I would recommend Wireshark for various network diagnostic purposes.

I'd rate the solution nine out of ten.

We use Wireshark to check the network traffic, and if there's any network problem or issue, we can check it through the tool. We also use Wireshark during analysis, to check if there's any network connectivity or attempts from the malware to communicate with the C&C server. We use the tool for further analysis and investigation.

I find Wireshark a very useful tool. Its best feature is that it allows me to deeply understand what's going on at the packet level, as well as any adverse signatures that I can analyze. When I need to create an IPS rule, I need to check the traffic deeply to get more insights about the actual traffic, what's the name of certain flags, etc., and I'm able to do all that through Wireshark.

The tool is also user-friendly.

A room for improvement in Wireshark is its ease of use for beginners. It could be better. Another room for improvement in the tool is for it to provide more details about the traffic load.

At the moment, Wireshark is adequate for me, so there isn't anything I'd like added to it in its next version.

I've been using Wireshark for a long time, so I can't remember the exact number of years I've been using it.

Wireshark is a stable tool. I didn't see any issues with its stability.

Wireshark is a scalable tool.

We never raised an issue or ticket with the Wireshark technical support team.

The setup process for Wireshark was very simple.

We're using the free version of Wireshark.

We didn't try to use other solutions apart from Wireshark.

Two hundred people use Wireshark within the company.

My rating for Wireshark is a nine out of ten because I like it and I use it so much.

I'm only a user of Wireshark.