(have mercy on me networking nerds, I’m still learning)
See also: WHO HAS 192.168.3.1 TELL 192.168.3.100
Now now, there’s no need to ARP on and on about this…
ACK!
Holy fuck you guys are nerds
When you plug in a network cable, this is some next level shit…
No place like 127.0.0.1
Oh hi neighbor. Mine is 127.0.0.2
what about ::1?
Localhost is wherever you are, ~ is home.
Btw, you should replace 127.0.1.1 with a permanent address. It was just a workaround for Gnome.
Fun fact, ipv6 was designed to fix this. Everything is multicast and, in theory, a switch could snoop MLD and create a nice map so that “where is the router?” Would send only to routers, and “whose got this up address?” Would send to a small group, usually with only the correct target in it.
However, it’s almost always just blasted out to everyone, and every network I’ve seen that has the mld snooping actually trying to do something just breaks ipv6 in various ways.
flashbacks to when I had to figure out PXE boot
Flashbacks to this week learning about it and its nice big vulnerability.
67
4
neigh? ra!
Eli5?
When your computer connects to the network, it asks for it’s address on the network. As it does not know where to ask, it sends a broadcast message to all computers on the same network (address 255.255.255.255). The service it wants to read is the DHCP service located on the servers’ port 67, therefore the :67 after the address.
The address it gets in return is always only temporary. The server admin can define how long such lease lasts, and when a computer calls the DHCP again later (before the lease runs out) it gets the same address, and the lease timer starts again.
Some networks with high turnover (guest networks in a cafe, or similar) have rather fast lease expiries, therefor leading to regular requests.
All the cool kids are doing ICMPv6 router solicitation, DHCP discover is so last decade.
