Protocol Analysis, Data Recorder, CALEA, Lawful Intercept, Application Performance, User Experience, Industrial Ethernet, Data Loss Prevention, Deep Packet Inspection, NetFlow, SOX, HIPAA and PCI Compliance, Switching and Routing, Forensics, VoIP, IPTV ... etc.
I get occasional emails and messages requesting that I produce some updated Wireshark quickstart videos. Topics suggested ranged from basic navigation, to how I configure Wireshark and of course troubleshooting scenarios.
I went back and was surprised that some of my Wireshark quickstart tutorials are 2 – 4 years old.
So time to refresh some of the basics and provide some tips and tricks along the way.
When it comes to processing performance, buffering or storage capacity, a Laptop is a very cost effective solution. Limitations are mainly caused by its integrated network card. For a 1G NIC, monitoring a 2Gbps in-line gigabit is already a problem, by deciding for a full duplex TAP or an aggregation TAP, you are choosing between visibility and packet losses. Of course, you may add second USB NIC, but in such case the Rx and Tx would be in two separated files, with a probable time difference. This can be very painful, for example, for TCP analysis.
With up to 1.5 Million packets per second, 1Gbps capture is a real challenge for the processor. The NIC driver has to parse the stream in single packets, then the capture driver timestamps each frame and finally the protocol analyzer generates the capture headers and decodes the frames. In this scenario, the CPU is quickly overloaded resulting in packet losses. This loss often occurs at the NIC driver or at the Protocol analyzer. The latter may show a drop counter, while the NIC driver not always count nor report the losses. Packets can simply disappear from your stream without you knowing it.
The wear and tear on your USB port and storage drive can cause it to break down over time. So what do you do to combat this? What can you do to combat this? Yes, we will be showing you an option to resolve this issue. The catch twenty two is we can for see a double edged sword coming out of what you are about to see and read about.
You have to feel sorry for small Data. Big Data is getting all the love. Success is about big cars, big houses and big waistlines, so it’s not surprising that Big Data is all the rage.
Back in simpler times, before small became passé, all those precious family pictures were in a shoebox in the hall closet. They were faded, tattered, and some of the great ones you remembered fondly and swore were in there somewhere, were not. Along came Big Data, and now all those freeze-frame moments from the ebb and flow of life are captured and digitally preserved with multi-megapixel perfection. Every single, immaculate one of them is in there, somewhere.
Big Data kind of snuck up on us, as Edward Snowden pointed out while leaving for an extended vacation in Russia. Just because our voicemails, text messages, emails, photos, videos, shopping habits, medical records, travel patterns – pretty much everything about us - was stored digitally somewhere didn’t automatically imply that someone was accessing it and using it. Just because you found your teenager’s diary doesn’t necessarily mean you’ll open it and read it. That would be wrong.
I love using the words WiFi Surveyand WiFi Troubleshooting interchangeably because as far as I’m concerned, the only difference between the two is spelling.
When I get involved with WiFi troubleshooting, the typical exercise involves recording the following items; location, signal statistics, throughput, packet loss and jitter. I have showed you some tools that automate or make this reporting methodology easier in previous videos.
The real work happens after you gather this data and attempt to transform it to meaningful information. For example, can I stream multimedia on my WiFi network? What kind of throughput can I expect in the conference room?
In many cases, the tools you use may use proprietary protocols or traffic generation that makes it tricky to predict how the real client’s application will actually perform.
John is the CTO and co-Founder and his role is to develop the technical vision, strategies, and relationships to drive product development to meet customer needs for his company. LiveAction was previously named ActionPacked Networks and is headquartered in Honolulu, Hawaii. It is also the name of their primary product which is a network performance management tool that helps simplify the complexity of monitoring, analyzing, and configuring technology areas such as: QoS, NetFlow, LAN, WAN, Routing, and IP SLA. It was lots of fun interviewing a fellow technologist and entrepreneur.
This event was broadcasted live. Thank you for joining us.
WebRTC has been all of the rage of late, and it’s high-time to explain what exactly the product offers in the way of telecommunications.
WebRTC was originally conceptualized by Google, who open-sourced the initiative in 2011, allowing developers access and the ability to modify. The goal of WebRTC is for web browsers to have real-time voice, text messaging, and video communications available for users, without having to rely on the presence of any third-party software. Think of it like having a Skype button built into your browser. Because it is open sourced, companies can write their own WebRTC applications to save costs and take advantage of the dynamic features available.