Wow, what a whirlwind that was.
But we've successfully made it through the packet analysis of both TCP and UDP,
and now we're ready to jump into our next section,
Troubleshooting TCP and UDP‑related Issues.
But before we hop into our next section,
let's take a minute to discuss everything that we've learned.
First,
we received a primer on our TCP HTTP web session
analysis by learning about the GET command,
which is exactly as it sounds, it's a request for a
resource, and the 200 OK signal,
which means that the file was successfully transferred. After a quick
primer, we jumped into an actual session analysis. During our analysis
of Wired Brain Coffee's new internet site, we saw firsthand how multiple
sessions were created. During our analysis, we could also see the
cohesive relationship that sequence and acknowledgement numbers have
between each other.
We also discovered how acknowledgement and sequence numbers
could change based on the TCP segment link.
Finally,
we closed our TCP session analysis figuratively and literally with a FIN/ACK
analysis during which we learned about the graceful closure of TCP sessions.
During our UDP session, we first discussed a primer on UDP and how it's a best
effort protocol and that it doesn't use flags.
But it does use something similar called options,
especially when utilizing DHCP.
We also learned how DHCP uses hard‑coded ports of 67 and 68.
After our primer was successfully covered,
we jumped into our DHCP session analysis.
During our analysis,
we discovered just how small our UDP sessions actually
are when compared to its TCP brother.
During our session analysis, we could see how the hard‑coded
ports of 67 and 68 work throughout the request.
During our analysis,
we also discovered the process in which a DHCP request goes
through to successfully retrieve an address.
Alright,
everyone. It's time to jump into our last section,
Troubleshooting TCP and UDP‑related Issues.
Let's learn about the pitfalls that have befallen so many of us and how to recover.