849
thanks lain (rule) (lemmy.blahaj.zone)
you are viewing a single comment's thread
view the rest of the comments
[-] cerement@slrpnk.net 47 points 1 week ago

really start to worry when it’s 169.254.0.x

[-] joyjoy@lemm.ee 10 points 1 week ago* (last edited 1 week ago)

That just means the ~~DNS~~DHCP is disabled.

Edit: words

[-] OsaErisXero@kbin.run 23 points 1 week ago

That is not what that means, it means there's no dhcp on that network segment.

[-] joyjoy@lemm.ee 17 points 1 week ago

In my defense, whenever there's a networking issue, it's always DNS related.

[-] 4am@lemm.ee 44 points 1 week ago

The three stages of grief:

  1. It can’t be DNS
  2. There’s no way it could be DNS
  3. It was DNS
[-] OsaErisXero@kbin.run 4 points 1 week ago

DNS being down is why the DHCP server didn't start ;)

[-] prex@aussie.zone 2 points 1 week ago

I can totally see dnsmasq causing this sort of thing.

load more comments (4 replies)
load more comments (5 replies)
load more comments (5 replies)
this post was submitted on 06 Jul 2024
849 points (99.8% liked)

196

15754 readers
3465 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS