Hi!
I’ve recently upgraded my raspberry pi to 0.7.1 from my 0.6.0 setup using the OTA option. Everything was working fine.
Well, now i cannot get my wifi to work again.
The problem is that the DHCP client seems to fail everytime AND I cannot use manual mode because… there’s no option in system settings -> connection.
In “connection” I can see my wifi connection, but when i press enter on it I can only see “connect” and “refresh”, there’s no “edit” option and I didn’t find anywhere else to enter a manual ip address for wifi.
I’ve tried to connect via SSH and edit /etc/network/configuration, but openelec does not allow this, the folder “network” doesn’t exist (sometimes, like this one, I really hate openelec and hope you drop it in favour of a raspbian-based rasplex).
DHCP server works, I use it for every device with address reservation (this pc, three smartphones, a bananapi server, samsung smart tvs, mobile pc, media server…
there might be a way to turn on some logging… I would research that so that you can see what’s happening when an IP is requested. Alternatively, what about just setting the DHCP server to give a static address to the pi (maybe you are already doing that?) if you are doing that, maybe turn off the hard mapping (& back to dynamic) for a boot (or 2) to see what happens.
Are there available addresses in the pool assigned for the DHCP server to use?
I’ll try to find a way to get DHCP logs…
At first the DHCP server was set to give a static address to the pi… but i disabled that rule when I started noticing problems. Nothing changed.
There are plenty of addresses available. I’ve set DHCP pool from 192.168.1.2 to 192.168.1.250 and i’ve at most 10 devices connected, working flawlessly.
But, why there’s no way to set a static ip for wifi from raspbian?!? That is so stupid… I could have solved my issue in few seconds…
And what is most stupid is that you could set a static ip for cable connection… but not for wifi. Why??
I’m not familiar with the PI per se, but on most 'Nix’s you can set a static for wifi (I’m sure you know that). There is another person here having some issues with network connectivity to his rasberry pi & ras plex.
I wonder something got messed up with the latest software updates to the network stack on the PI’s OS? Worth a look into.
Problem is that rasplex is based on openelec, a very closed environment.
The first thing I’ve tried is edit /etc/network/interfaces… but it does not even exist.
Unfortunately this issue is a quirk of OpenELEC, the ‘Edit’ option is only accessible in System Settings->Connections after you have established a connection via WiFi.
I’m assuming that you have DHCP enabled in your router settings.
Some WiFi adapters require more power than others to function, if you have plugged the adapter directly into the RPi make sure you are using at least a 2A power supply or plug the adapter into a powered hub connected to the RPi. It sounds like this could be the issue.
Yes, DHCP is enabled in my router settings, and is working with all my other devices.
The power supply is a 2A one, but i’ll try to connect it to a powered hub.
EDIT:
I’ve tried, nothing changed.
I select my wifi connection, enter the wpa password and then I can see the “state” canged from “idle” to “association”. After few seconds it changes to “configuration” and it stays like this for about a minute and then it changes to “failure”.
Tried with two other wi-fi dongles, but nothing changed.
You could also use the last resort - reflash the SD card.
If you want to retain your settings copy the guisettings.xml file to your PC first and copy it back when you’ve reflashed and done the first boot (WiFi configuration on first boot is back in 0.7.1), then reboot.
From what you have said you have tried I can only conclude that this is an issue with your router, WiFi is certainly working fine on 0.7.1, sorry I can’t be of more help.
I discovered that the version of AMOD (a modified firmware for my DGN3500 router) I had installed, has a bug in the default dhcp server.
I upgraded the firmware to the latest version and switched to dnsmasq to handle dhcp. Now everything works like a charm.
Again, thanks a lot to everyone for the support and the help
.