Foundation workshop: Hands-on, how does the Internet work?
From 35C3 Wiki
|Description||This workshop is for all who only have a vague idea or might not know at all what an "IP address" is. We'll learn how the Internet works by making Internet traffic visible. This is a beginner's workshop. If you toyed with Wireshark before, you will be bored to hell in this workshop.|
|Tags||foundation, wireshark, network|
|Processing assembly||Assembly:Curry Club Augsburg|
|Language||en - English |
en - English
(Click here to refresh this page.)
|Starts at||2018/12/29 17:20|
|Ends at||2018/12/29 18:10|
|Location||Room:Lecture room M2|
For reasons unknown, this session has evaporated from the calendar. This is to confirm that the session IS taking place, as announced here on the wiki.
Invisible to the casual user, lots of computers communicate and work together to deliver the kitten videos you're craving. In this workshop, we use the tool Wireshark (available for all operating systems) to make this communication visible. In lots of life demos, we'll learn that the domain names we're familiar with, like ccc.de or latein.at, are a thin layer around IP addresses, which are the real addresses computers use to identify themselves. We'll uncover which hidden information your browser sends along each request, and we'll see how easy it is to intercept traffic.
This workshop is for everybody who is interested in knowing how the Internet works, in which form computers talk to each other. It is intended as a companion workshop to the mainline talk with the same title. Absolutely no prerequisites are required, not even from that talk. People who are familiar with network stacks will be bored to hell.
Note to the infrastructure team: In the final part of the talk, we'll perform a standard ARP spoofing attack to intercept traffic from a volunteer. Of course we won't use the congress network for this. I'll open an own hotspot.
- Slides of the talk
- Commands which appeared in the talk: ifconfig, ip a, ping 126.96.36.199, echo 1 > /proc/sys/net/ipv4/ip_forward
- Questions by mail are welcome! firstname.lastname@example.org