search

WebReflection / benja

Bootable Electron Node JS Application
https://archibold.io/benja/
194 stars 32 forks source link

Only wifi when ethernet connected on rpi3 #18

Closed bohnmedia closed 7 years ago

bohnmedia commented 7 years ago

I am no expert in netctl but there seems to be an issue with wifi on the raspberry pi 3. After creating the profile with wifi-menu and enabling it with netctl enable wifi-name on a clean installation I got two IP addresses.

One for the local area network and one for the wifi.

I can only connect to the wifi IP when the ethernet cable is attached. Otherwise I am getting a timeout.

[benja@benja ~]$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.100.34  netmask 255.255.255.0  broadcast 192.168.100.255
        inet6 fe80::ba27:ebff:fe06:6f39  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:06:6f:39  txqueuelen 1000  (Ethernet)
        RX packets 386  bytes 59562 (58.1 KiB)
        RX errors 0  dropped 44  overruns 0  frame 0
        TX packets 208  bytes 49231 (48.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 345  bytes 28399 (27.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 345  bytes 28399 (27.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.100.30  netmask 255.255.255.0  broadcast 192.168.100.255
        inet6 fe80::136e:5ad:b8d6:35f3  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:53:3a:6c  txqueuelen 1000  (Ethernet)
        RX packets 446  bytes 78787 (76.9 KiB)
        RX errors 0  dropped 119  overruns 0  frame 0
        TX packets 71  bytes 11149 (10.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I can ping google.com from the raspberry pi in both cases. When the cable is attached and when its not attached. But connections to the raspberry pi over ssh or by opening the url still only work when the ethernet cable is attached.

bohnmedia commented 7 years ago

Ok, seems to be a local problem. Tried another system and can connect without cable attached.

Please delete and thanks for the great work. :)