Raspberry PI 3 wifi connection problems

[Alexandermarkussen]

Alexandermarkussen

12. Oktober 2017 at 1:50 #31869

Hi

I am trying to connect the Raspberry PI to the internet via wifi, using the built in wifi. I am now at a stage where I can connect via wifi to the PI and via the max2play web interface control it. But I am having problems. I am getting the error message: Internet: NO Connection, but I can see the PI on my Network Map. I can not seem to find what is causing the problem. The whole thing works when a LAN cable is connected.

Regards,
Alexander

[Heiner premium]

Heiner premium

12. Oktober 2017 at 15:17 #31876

Hi Alexander,

Please check your WiFi/LAN menu’s Access Point Autostart Mode and deactivate it if it’s active (remove the tick and click „save“).

Afterwards, you can check the Debug Info, whether your WiFi connection is properly established. If you still cannot access the internet (you can check by trying to update the system), please share the contents of the Debug Info here.

[Alexandermarkussen]

Alexandermarkussen

12. Oktober 2017 at 16:09 #31878

Hi Heiner

The Accesspoint autostart mode is already deactivated.

Here is the debug info from the Wifi/LAN menu:
eth0 Link encap:Ethernet HWaddr b8:27:eb:b7:ef:cb
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:162 errors:0 dropped:0 overruns:0 frame:0
TX packets:162 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:12052 (11.7 KiB) TX bytes:12052 (11.7 KiB)

wlan0 Link encap:Ethernet HWaddr b8:27:eb:e2:ba:9e
inet addr:192.168.1.39 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32 errors:0 dropped:0 overruns:0 frame:0
TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3557 (3.4 KiB) TX bytes:14676 (14.3 KiB)

[Heiner premium]

Heiner premium

13. Oktober 2017 at 10:08 #31884

Hi Alexander,

Could you try establishing the WiFi again, rebooting and removing the LAN cable immediately after clicking reboot in the web interface to make sure the Pi does not prioritize the ethernet connection while starting.

[Alexandermarkussen]

Alexandermarkussen

13. Oktober 2017 at 16:46 #31892

Hi Heiner

I have rebooted the system again but it still only connects to the router via wifi and not to the internet. Is there a command to make it prioritize wifi?

The Debug Info still says:
eth0 Link encap:Ethernet HWaddr b8:27:eb:b7:ef:cb
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:1993 errors:0 dropped:0 overruns:0 frame:0
TX packets:1993 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:145878 (142.4 KiB) TX bytes:145878 (142.4 KiB)

wlan0 Link encap:Ethernet HWaddr b8:27:eb:e2:ba:9e
inet addr:192.168.1.39 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:830 errors:0 dropped:0 overruns:0 frame:0
TX packets:1198 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:89494 (87.3 KiB) TX bytes:158621 (154.9 KiB)

[Heiner premium]

Heiner premium

17. Oktober 2017 at 11:04 #31921

Hi Alexander,

The WiFi should be the only possible connectivity and you should not be able to access Max2Play otherwise, if you disconnected the ethernet cable right after reboot.

Are you accessing it via HDMI, or did you revert back to ethernet?

Also, if you router is WPS compatible, please try using the WPS push button method with Max2Play: https://www.max2play.com/en/how-tos/how-to-wifi-configuration-with-wps-and-max2play/