Solved Can't Connect

[Substring]

How did your pi get 192.168.25.5 ?

[seic]

Have the same problem, others too on the german forums. Use 4.0 (Yolo Changelog) on a Pi2, I have access to shared and monitoring via Edimax Wlan Stick but have "no connection". It happens the last mh 4 Days? Before I had no Problems.

[mazur]

@Substring

Thats the local IP (assigned by DHCP).. I think, maybe sobe ISP issue.. Still looking for a solution..

[Substring]

@mazur Do you have a DNS and a gateway set on your pi ? That's most probably an incomplete DHCP problem

[mazur]

@Substring Yes i tryed auto and static settings.. on PC i can't ping recalbox.com too.. maybe some router setting?

[Substring]

@mazur as i said : check your DNS and gateway on recalbox, and what happens on your router. If you set a static ip'on recalbox, you may have forgotten what i said

[mazur]

Already check everything.. dunno what to do

[Substring]

@mazur cdan you paste the result of ifconfig? and route or route print ?

[mazur]

@Substring , please check:

# ifconfig
eth0      Link encap:Ethernet  HWaddr B8:27:EB:79:9E:06
          inet addr:192.168.25.4  Bcast:192.168.25.255  Mask:255.255.255.0
          inet6 addr: fe80::ba27:ebff:fe79:9e06%1994427092/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:158 errors:0 dropped:0 overruns:0 frame:0
          TX packets:163 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:15499 (15.1 KiB)  TX bytes:24591 (24.0 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1%1994427092/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

#

# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.25.1    0.0.0.0         UG    0      0        0 eth0
192.168.25.0    *               255.255.255.0   U     0      0        0 eth0
#

# /etc/resolv.conf
search domain.name # eth0
nameserver 192.168.25.1 # eth0

# /etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

auto wlan0
iface wlan0 inet dhcp
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf


# ping recalbox.com
PING recalbox.com (217.70.184.38): 56 data bytes
--- recalbox.com ping statistics ---
75 packets transmitted, 0 packets received, 100% packet loss

I changed resolv.conf and interfaces but that files keeping returning to the default DHCP settings, already tryed to make them readonly, no sucess..

[Substring]

Have you tried pinging google rather ?

[mazur]

@Substring Yes, pinging any other site works..

[Substring]

@mazur ok can you try a traceroute to recalbox.com, archive.recalbox.com and www.recalbox.com ? Thank you

[CapFuture1975]

When i use my pc with firefox, i also get a timeout error to connect to recalbox.com sever.

[Substring]

recalbox.com itself means nothing, should try with www.recalbox.com. And as your are on the forum, i guess the DNS does work

ooops it does work for me :

# ping recalbox.com
PING recalbox.com (217.70.184.38): 56 data bytes
64 bytes from 217.70.184.38: seq=0 ttl=53 time=7.614 ms
64 bytes from 217.70.184.38: seq=1 ttl=53 time=7.370 ms
64 bytes from 217.70.184.38: seq=2 ttl=53 time=7.448 ms
64 bytes from 217.70.184.38: seq=3 ttl=53 time=7.336 ms
64 bytes from 217.70.184.38: seq=4 ttl=53 time=7.521 ms
64 bytes from 217.70.184.38: seq=5 ttl=53 time=7.438 ms
64 bytes from 217.70.184.38: seq=6 ttl=53 time=7.607 ms
64 bytes from 217.70.184.38: seq=7 ttl=53 time=7.504 ms
^C
--- recalbox.com ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max = 7.336/7.479/7.614 ms

[Substring]

try pinging www.recalbox.com instead please

[Substring]

Been searching : it pings recalbox.com to say if you're connected or not. I guess we'll change that in 4.1 as this DNS is not accurate and points to nothing special. So the message NOT CONNECTED is a mistake

[mazur]

@Substring Thanks very much!

[DannyOcean]

@Substring

Same problem.
Network settings show "not connected".
But connection via SSH is fine.

Strange thing is that scraping of ROMs works and tracking with retroachievements server also work as it should. But no updates possible.

Yes, w-lan settings are correct, also looked in the config.
I can ping WWW.recalbox.com but not recalbox.com - same with firefox via laptop.

recalbox pings recalbox.com to check if we're "connected".

The "www" has to be in the address.

So how do we update to 4.1 if we get no connection with 4.0?

[Substring]

@DannyOcean easy pal ...

4.1 is not here, we are taking care of that dns thing. We'd still have a few tricks up our sleeve anyway. I'd like to say it should be solved by the weekend as we're working on it, but it does not only depend on us

[DannyOcean]

@Substring always easy
Also wanted to say a big THANK YOU to you and your colleagues. Coders, forum admins, translators etc...