196

16504 readers

2294 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

founded 1 year ago

MODERATORS

762

thanks lain (rule) (lemmy.blahaj.zone)

submitted 4 months ago by [email protected] to c/[email protected]

87 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 48 points 4 months ago (1 children)

really start to worry when it’s 169.254.0.x …

[–] [email protected] 9 points 4 months ago* (last edited 4 months ago) (2 children)

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

Edit: words

[–] [email protected] 23 points 4 months ago (2 children)

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

[–] [email protected] 16 points 4 months ago (2 children)

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

[–] [email protected] 43 points 4 months ago (1 children)

The three stages of grief:

[–] [email protected] 13 points 4 months ago

[–] [email protected] 4 points 4 months ago (1 children)

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

[–] [email protected] 2 points 4 months ago

I can totally see dnsmasq causing this sort of thing.

[–] [email protected] 1 points 4 months ago

If there isn't DHCP and you device isn't set for a static IP, would it even connect?

[–] [email protected] 22 points 4 months ago