Wifi working but still "NOT CONECTED"
-
@Pepe mmm, no, i don't have static ip. I mean, i set a static internal ip for the raspberry in my dhcp router configuration, but my ISP doesn't have a static ip.
Should i change something in the configuration??
I setted only the wifi ssid and password -
@cagiraudo in a ssh session, what is the output of
cat /etc/resolv.conf
? -
@Pepe said in Wifi working but still "NOT CONECTED":
cat /etc/resolv.conf
nameserver 200.49.130.52 # wlan0
nameserver 200.42.4.207 # wlan0 -
@cagiraudo Seems to be caused by DNS config. As u can check in network tools sites like this, the name server configured in your /etc/resolv.conf are not solving names. This is output of nslookup for google.com through dns configured on your recalbox:
... here is the nslookup result for www.google.com from server 200.49.130.52, querytype=ANY : ;; connection timed out; no servers could be reached
... here is the nslookup result for www.google.com from server 200.42.4.207, querytype=ANY : ;; connection timed out; no servers could be reached
Try this to change dns config and solve the issue:
- https://github.com/recalbox/recalbox-os/wiki/Make-a-partition-writable-(EN)
- In Recalbox Wiki:
In order to get name resolution working, you will have to create a file names /etc/resolv.conf. By default, this files points to an auto-generated file located at /tmp/resolv.conf, so in order to do it once and for all, run the following commands:
rm /etc/resolv.conf
nano /etc/resolv.conf
Enter the following lines, which corresponds to DNS servers of the
OpenDNS project:nameserver 208.67.222.222
nameserver 208.67.220.220
Save the file.Now reload the settings with : ifdown eth0 && ifup eth0
THESE EDITS WILL BE OVERWRITTEN WITH EACH NEW UPDATE - You will have to repeat these tasks after each update.
-
@Pepe said in Wifi working but still "NOT CONECTED":
ifdown eth0 && ifup eth0
i did what you said (at least i think i did) but it's still not working
-
@cagiraudo in a ssh session, what is the output of
cat /etc/resolv.conf
now?
If the content of the file is the same as before then the changes have not been saved. Do it again and pay attention to any posible errors that appear when you save. Otherwise in the last command of wiki instruction, the one u blockquoted, changeeth0
bywlan0
or even better restart your recalbox. -
@Pepe nice and complete answer congratz !
-
@Pepe
Indeed, thanks for your time and complete answerscat /etc/resolv.conf
nameserver 208.67.222.222
nameserver 208.67.220.220I tried with ifdown wlan0 && ifup wlan0. Even restarting the raspberry, but still says "NOT CONNECTED"
-
@cagiraudo
Do you want me to paste some log? -
@Substring Thanks!
@cagiraudo Try ping google.com in shh, Is there an answer?, if so, try to undo what u mentioned here:
I did research a lot and tried the solution of changing the ping website to archive.recalbox.com like you describe here: https://forum.recalbox.com/topic/5039/can-t-connect/41
I think this solution don't work now i think is a old tip for a temporary issue.
If there is no answer from google to previous ping, i think i give up, something else fails on your system in addition to the DNS resolution but I can not think what.
-
No, no response when i ping google.com. Maybe there is something strange with my network, i will keep trying.
Thanks anyway
-
there is something strange, i found out i can't ping with any device connected in my network, i can browse internet without problem, but anytime i try to ping some site i don't get answers, i tried with notebook, cellphone, recalbox, etc.
I know this is beyond recalbox, but do you have any idea what could be happening??
Thanks
-
@cagiraudo Speculation: something related to ICMP protocol at router / firewall or even ISP level.
-
Just an upgrade, my ISP was blocking my ICMP packets.
I solved that issue and now the recalbox connects to internet without any problem
Thank you @Pepe for the help
-
@cagiraudo that was a very nasty network issue
-
Well, the important thing is that it has been solved and nobody has fallen in the way.
-
@Pepe and mostly that Recalbox is not the problem hahaha