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