Interstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 5 months agothanks lain (rule)lemmy.blahaj.zoneexternal-linkmessage-square86fedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1external-linkthanks lain (rule)lemmy.blahaj.zoneInterstellar_1@lemmy.blahaj.zone to 196@lemmy.blahaj.zone · 5 months agomessage-square86fedilinkfile-text
minus-squarecerement@slrpnk.netlinkfedilinkarrow-up0·5 months agoreally start to worry when it’s 169.254.0.x …
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up0·5 months agoThat just means the DNS is disabled.
minus-squarecerement@slrpnk.netlinkfedilinkarrow-up0·5 months ago “The hotel’s free WiFi is really fast” “the DNS is disabled”
minus-squareOsaErisXero@kbin.runlinkfedilinkarrow-up0·5 months agoThat is not what that means, it means there’s no dhcp on that network segment.
minus-squareNeato@ttrpg.networklinkfedilinkEnglisharrow-up0·5 months agoIf there isn’t DHCP and you device isn’t set for a static IP, would it even connect?
minus-squareunalivejoy@lemm.eelinkfedilinkEnglisharrow-up0·5 months agoIn my defense, whenever there’s a networking issue, it’s always DNS related.
minus-squareOsaErisXero@kbin.runlinkfedilinkarrow-up0·5 months agoDNS being down is why the DHCP server didn’t start ;)
minus-squaredustycups@aussie.zonelinkfedilinkarrow-up0·4 months agoI can totally see dnsmasq causing this sort of thing.
minus-square4am@lemm.eelinkfedilinkarrow-up0·5 months agoThe three stages of grief: It can’t be DNS There’s no way it could be DNS It was DNS
really start to worry when it’s
169.254.0.x…That just means the DNS is disabled.
That is not what that means, it means there’s no dhcp on that network segment.
If there isn’t DHCP and you device isn’t set for a static IP, would it even connect?
In my defense, whenever there’s a networking issue, it’s always DNS related.
DNS being down is why the DHCP server didn’t start ;)
I can totally see dnsmasq causing this sort of thing.
The three stages of grief: