Packet Header Breakdowns
crplhood
Member Posts: 42 ■■□□□□□□□□
in CCNA & CCENT
Over the next few days, I'll be updating this link to include different headers covering ethernet, routing, IPv6, etc. Can you guys tell me what you think of the format? Does the format look okay with the explanation inside the packet or should I move the field descriptions into normal page text?
https://steveinit.wordpress.com/networking-study-guides/packet-teardowns/
*Edited to say: Click IPv4 Packet Header. The link is the main page which I'll be expanding.
https://steveinit.wordpress.com/networking-study-guides/packet-teardowns/
*Edited to say: Click IPv4 Packet Header. The link is the main page which I'll be expanding.
CCNA R&S[X] CCENT[X] Sec+[X] A+[X] VMware Airwatch Associate[X] Steve's Blog Steve's Linkedin
Comments
-
wd40
Member Posts: 1,017 ■■■■□□□□□□
Small question, why are you masking the source and destination in the wireshark capture? -
crplhood
Member Posts: 42 ■■□□□□□□□□
I pulled these at work. It's policy. I know they are private IPs.CCNA R&S[X] CCENT[X] Sec+[X] A+[X] VMware Airwatch Associate[X] Steve's Blog Steve's Linkedin
-
Ismaeljrp
Member Posts: 480 ■■■□□□□□□□
Why not use GNS3 for this stuff?
The "look" is nice. No problems here. -
crplhood
Member Posts: 42 ■■□□□□□□□□
Bc I did it at work during some downtime. Now that I have some feedback on the format, I'll recap this stuff on my home rig. I figure I can build out a lab covering most of the packet types I want within a few hours while also getting some practice in.CCNA R&S[X] CCENT[X] Sec+[X] A+[X] VMware Airwatch Associate[X] Steve's Blog Steve's Linkedin