In the crazy world of network troubleshooting, sifting through endless packet captures can feel like searching for a needle in a haystack. This clever video from The Technology Firm introduces a simple yet brilliant technique called the "Packet Bookmark." By creating a quick desktop shortcut that pings a reliable site like Google.com, you generate distinctive ICMP packets that act as visual anchors in your traces. This method shines especially when you lack time for detailed note-taking during live captures involving web forms, streaming media, or VoIP sessions.
The demonstration walks through the entire process in under three minutes: setting up the ping shortcut, starting a Wireshark capture on your wireless interface, performing key actions like submitting a contact form, and strategically placing pings before and after events.
This post follows on from my earlier Kafka Basics and Demo blog. This time we take a look at the packets. How does a Kafka producer send a message to a topic? How on earth does a Kafka consumer know that there is a message waiting to be fetched?
In this video, we look at the Kafka protocol basics with Wireshark.
I have reached that point in life where my doctor starts many of his comments with “At your age....”. I have come to realize this is more than a mere figure of speech. Like most of my contemporaries, I began by trying to figure out “what” I was going to be (first a physician, eventually an engineer). I gave little thought to when or how age might nudge me onto an off-ramp from the expressway to money and success. Who Do You Want to Be When You Grow Old? by Richard Leider and David Shapiro reminds us that sooner or later, our life-long model for living an accomplished life will fall apart. The book is not a list of answers or techniques, but rather a new perspective that will provoke thought and provide inspiration. Getting old is inevitable (provided you choose your parents carefully and take good care of yourself), but growing old, pursuing the “who” of your life, requires purpose.
I’m fairly confident everyone has used a speedtest site. They are handy and provide a pretty good idea of performance to your computer. Some of the more popular sites that I have used is www.speedtest.net and www.fast.com
In spite of their convenience, there are always caveats and general things to keep in mind when using these sites. External internet connection and related equipment as well as internet variables will affect your overall performance. For example, you might have a weak Wi-Fi signal or busy router that would impact your performance numbers.
QUIC is one of those networking technologies that can look complicated until you understand the problem it is trying to solve. Officially defined by RFC 9000, QUIC is a secure transport protocol that runs over UDP rather than TCP. That may sound like a small implementation detail, but it represents a major change in how modern Internet applications handle reliability, encryption, congestion control, and multiple data streams. QUIC was developed with the modern web in mind, and its design eventually became the foundation for HTTP/3.
One of the things that makes QUIC interesting to network engineers is that it takes functionality traditionally associated with TCP and moves much of it into the QUIC protocol itself. QUIC provides reliable delivery, flow control, congestion control, packet numbering, and loss recovery while using UDP as its underlying transport. It also integrates TLS 1.3 into the connection process, rather than treating encryption as something layered separately on top of the transport. The result is a transport protocol that can evolve without requiring changes to TCP or the underlying IP infrastructure.
Performance is another major reason QUIC attracted so much attention. A traditional HTTPS connection involves TCP connection establishment followed by TLS negotiation, while QUIC combines transport and cryptographic negotiation to reduce connection setup overhead. QUIC also supports multiple independent streams inside a single connection. If one stream experiences packet loss, data on other streams does not have to wait in the same way it can with TCP's single ordered byte stream. For applications such as web pages that load many objects simultaneously, this can make a noticeable difference in responsiveness.
Another feature worth watching is connection migration. A QUIC connection is not tied as tightly to a particular network path as a traditional TCP connection. QUIC connection identifiers allow a connection to survive certain changes in network addressing, such as a mobile device moving from Wi-Fi to cellular service. That is particularly useful today because users routinely move between networks while applications remain connected. For network troubleshooters, however, QUIC also changes the way traffic is analyzed: instead of looking for familiar TCP handshakes and retransmissions, engineers increasingly need to understand UDP-based QUIC traffic and its encrypted packet structure.
The arrival of RFC 9000 was therefore much more than another Internet standards milestone. It marked the point where QUIC became a standardized transport protocol capable of supporting the next generation of Internet applications. HTTP/3 subsequently defined how HTTP semantics operate over QUIC, taking advantage of its stream multiplexing, flow control, security, and lower-latency connection establishment. For network engineers, developers, and security professionals, understanding QUIC is becoming increasingly important because troubleshooting modern web traffic increasingly means understanding what is happening inside UDP-based transport rather than relying exclusively on traditional TCP analysis.
This means that every packet head, network engineer, developer, and security professional should get a handle on how QUIC works. Let's take a look at an intro to QUIC in this video.
RFC 9000, “QUIC: A UDP-Based Multiplexed and Secure Transport,” defines the core specification for QUIC, the modern transport protocol that underpins HTTP/3. One of its biggest highlights is that QUIC moves many functions traditionally associated with TCP into the protocol itself, while running over UDP. This gives QUIC much more flexibility without requiring changes to the underlying IP network. QUIC also integrates TLS 1.3 into the connection process, providing encryption and authentication as a fundamental part of establishing a connection rather than treating security as an optional add-on.
One of the most important benefits is reduced connection setup time. Traditional TCP connections require a handshake, followed by a separate TLS handshake before application data can be exchanged. QUIC combines these processes, allowing secure connections to be established with fewer round trips. QUIC also supports connection migration, meaning a connection can continue even when the client's network changes—for example, moving from Wi-Fi to a cellular connection. That is particularly useful for smartphones, laptops, and other mobile devices where network connectivity can change frequently.
RFC 9000 also addresses a long-standing TCP problem called head-of-line blocking. QUIC supports multiple independent streams within a single connection, so if packets belonging to one stream are delayed or lost, other streams can continue processing their data. This can make applications more responsive, especially when transferring multiple objects simultaneously. QUIC also provides mechanisms for acknowledgments, retransmissions, congestion control, flow control, and packet numbering, giving implementations the tools they need to efficiently manage network traffic while avoiding congestion.
From a network-engineering perspective, RFC 9000 is significant because it effectively creates a highly capable transport protocol without requiring a new IP protocol number. Because QUIC uses UDP, it can be deployed across existing Internet infrastructure while allowing protocol developers to evolve transport behavior much more rapidly than TCP. The combination of built-in TLS security, faster connection establishment, multiplexed streams, connection migration, and improved behavior on unreliable networks makes QUIC particularly well suited to today's Internet. For network administrators and troubleshooting teams, understanding RFC 9000 is increasingly important because QUIC traffic is becoming a major part of everyday web traffic, particularly through HTTP/3.
