Tagged: Pesky 169.254.x.x
September 26, 2017 at 4:33 pm #12119
When your wireless interface gets stuck negotiating a DHCP handshake with your wireless router there are times when the nuclear option of the shutdown buttons for everything does not work! You will know when it happens as ifconfig (or ipconfig for windows) keeps returning the pesky 169.254.x.x address meaning that the DHCP handshake has failed.
After half a day pfaffing around with a Raspberry Pi Zero (no wired option) I found a solution: try:
sudo dhclient -r wlan0
sudo dhclient wlan0
I have no idea why this problem started other than it coincided with an update – bah!
for some unknown reason the above worked while
sudo ifdown wlan0
sudo ifup wlan0
- This topic was modified 1 year, 1 month ago by Ed P.
September 26, 2017 at 6:55 pm #12134
Ed PParticipant@edpsForumite Points: 2,121
Edit, I think I identified a solution, and possible cause. The solution was to dial down my Hub to the ‘legacy’ setting. As things used to work just fine with the b/n/g setting it suggests either the Pi suffered a wifi driver regression or BT have regressed their driver in some way. The problem was evidenced as a dhcp link that kept dropping out.00
You must be logged in to reply to this topic.