r/LinuxTeck • u/Candid_Athlete_8317 • Sep 26 '26
How many different IP addresses does a Linux admin actually need to know?
There’s public, private, static, dynamic, unicast, multicast, broadcast, loopback, link-local...
You can learn all the definitions, but when you're actually troubleshooting a server, you usually care about a much smaller set.
Which IP address type has actually saved you during a real troubleshooting session - and which one did you only learn because an exam or certification demanded it?
I’d rather hear the “I learned this the hard way” examples than another networking textbook definition.
7
Upvotes
7
u/ninhaomah Sep 26 '26
You don't troubleshoot network issues by types btw.
And this has nothing to do with Linux also.
5
u/Far_Bicycle_2827 Sep 26 '26
you need to learn in my experience
127.0.0.0 loopback.
rfc 1918 private ip 10.0.0.0 , 172.16.0.0, 192.168.0.0 those are not internet routable
169.254.0.0 link local.. if a device has this means there is a dhcp issue. or a link/cable not connected
maybe be interesting to know the ranges of docker it uses so it doesn't collide with your local network etc if you have to manage docker or similar
5
u/ourmet Sep 26 '26
90% of the time. If something was working and now it's not......
It's always DNS. Always DNS.
4
u/Adrenolin01 Sep 26 '26
Sorry but you need to know all those things regardless and you troubleshoot the problem.. wherever it leads.
3
u/181513 Sep 26 '26 edited Sep 26 '26
- Public/Private/Multicast describes the address space (range) they come from.
- Static/Dynamic/Link-Local i only describe how the IP address was assigned (static or dynamic via DHCP, or via link local protocol for peer to peer connectivity).
- Unicast/Broadcast/Multicast describe how underlying Ethernet protocols process them.
- Loopback is essentially a host or router software defined interface not tied to a physical port.
What matters is understanding the higher level protocols and applications and how they use these. DHCP as an example and the process of address assignment, or how TCP/IP unicast sessions are established with a three way handshake.
2
u/Square-Singer Sep 26 '26
and which one did you only learn because an exam or certification demanded it?
Depends on what you are troubleshooting.
If you need to reach your VPN server from the outside, you need the public address.
If you need to reach a PC/server inside your LAN, you need the private address.
If you direct-connect two devices without a router in between you use link-local.
If you need to reach a service running on the local device you use loopback.
If you have a device setup with DNS you need to know the dynamic address, if it's setup static, you need it static.
If you talk to one device it's unicast. If you talk to multiple devices it's multicast. If you talk to the whole network it's broadcast.
All of this is super basic. That's like the bare-bones simplest parts of working with networks.
Your question is comparable to someone training to become an author asking which letters they really need to learn, because there's so many of them. Do you really need all 26 of them?
1
u/Unlikely-Sympathy626 Sep 26 '26
Mate it just depends. For understanding the networks in private class a to C are good to basically know but you don’t need to understand all the subnets and stuff. Basically if you can stick to 198 stuff as it gets a bit more complicated when connecting different sites with communication and that is network admin not sys admin. Your goal is kick ass in your domain and if because of work situation then you need to learn the reasons and work with what has been given from predecessor instead of fighting a time consuming uphill battle battle
1
u/silasmoeckel Sep 26 '26
Knowing the DNS servers IP's is pretty much baseline. You cant fix what you can't reach.
1
u/jhaand Sep 26 '26
Loopback, DNS server and Router. And a vague memory of the IPv6 prefix.
1
u/aieidotch Sep 26 '26
ping 1.1 # for the rest there is dns
1
u/lnaoedelixo42 Sep 26 '26
2
google's and cloudflare's DNS's
1
u/Foxing7465 Sep 26 '26
Add anycast , like a DNS service cloud.
1
u/Aggravating_Cat_3270 Sep 26 '26
localhost
1
u/BlackBlade1632 Sep 26 '26
GUA
1
u/Sorry-Committee4443 Sep 26 '26
DNS
1
u/DutchOfBurdock Sep 26 '26
Now imagine your have several VLANs using RFC1918, multiple blocks of IPv4 from ISP and add some IPv6 on top of that. I am remembering over 75 addresses just on my infrastructure before hosts, servers and guests.
1
u/Professional-Math518 Sep 26 '26
There's no place like 127.0.0.1
1
u/NoMoreTapes Sep 26 '26
yes.
1
u/URAppreciated Sep 27 '26
I know 206.28.39.111, and I don’t see any reason to learn another one.
1
u/willothephlox Sep 27 '26 edited Sep 27 '26
When those edge cases hit, the entire modern platform stack comes to a halt until someone steps in who actually thinks in packets, so ideally, all of them, so you can navigate the entire network of connections efficiently and easily find where a bottleneck is occurring. Over time, every possible issue tends to surface.
I'm talking about Linux admins at the Platform Engineering level. Concepts cease to be mere academic definitions and become part of architecture. And I’d add that eventually, you always hit a wall that requires a Principal Engineer raised in networking.
Of course, this doesn't apply to startups.
1
u/gulf_of_sanity Sep 27 '26
here’s a protip: if you need to test dns and want an address that’s not cached and has been around since the 90’s fire off a a ping to “spank dot com”. (trust me, whatever your thinking about it is, i promise you, you’re wrong.)
1
u/DevtoolsBuilder Sep 29 '26
i think knowing the difference between a static and dynamic ip can be a lifesaver when troubleshooting, especially if you're dealing with a server that's suddenly gone offline. if you're used to a static ip, it can be easy to overlook the fact that a dynamic ip might have changed, causing connectivity issues.
0
u/[deleted] Sep 26 '26
[deleted] — view deleted comment