My SSIDs are different for 2.4 and 5.
Perhaps, we should restart from a more clean point:
- check again dtoverlay=sdhost is set
- ssh and cd to
/var/lib/connman - list the directory using
ls -al - remove all directories starting with
ethernetorwifiusingrm -R ethernet*andrm -R wifi* reboot- now, try again connecting to your 5GHz wifi in MyOSMC
Thank you Jim. I’ve done as you’ve suggested. Here is what I observed
check again dtoverlay=sdhost is set
osmc@RPi3OSMC1:~$ cat /boot/config.txt
gpu_mem_1024=256
hdmi_ignore_cec_init=1
disable_overscan=1
start_x=1
dtoverlay=lirc-rpi
disable_splash=1
dtoverlay=sdhost
# NOOBS Auto-generated Settings:
hdmi_force_hotplug=1
arm_freq=850
core_freq=375
gpu_mem_256=112
decode_MPG2=0xfa63e509
decode_WVC1=0x6b2bbd4b
sdtv_aspect=1
dtparam=gpio_in_pin=18
gpu_mem_512=144
dtparam=gpio_out_pin=17
osmc@RPi3OSMC1:~$
ssh and cd to /var/lib/connman
list the directory using ls -al
osmc@RPi3OSMC1:~$ cd /var/lib/connman
osmc@RPi3OSMC1:/var/lib/connman$ ls -al
total 28
drwxr-xr-x 6 root root 4096 Mar 2 12:31 .
drwxr-xr-x 16 root root 4096 Feb 7 07:23 ..
drwx------ 2 root root 4096 Mar 2 12:29 ethernet_b827eb83727e_cable
-rw------- 1 root root 179 Mar 2 12:31 settings
drwx------ 2 root root 4096 Mar 2 14:28 wifi_000000000000_3239436f766552642d35 47_managed_psk
drwx------ 2 root root 4096 Mar 2 14:29 wifi_000000000000_3239436f76655264_man aged_psk
drwx------ 2 root root 4096 Mar 2 12:32 wifi_b827ebd6272b_3239436f76655264_man aged_psk
osmc@RPi3OSMC1:/var/lib/connman$ ^C
osmc@RPi3OSMC1:/var/lib/connman$
remove all directories starting with ethernet or wifiusing rm -R ethernet* and rm -R wifi*
osmc@RPi3OSMC1:/var/lib/connman$ sudo rm -R ethernet*
osmc@RPi3OSMC1:/var/lib/connman$ sudo rm -R wifi*
osmc@RPi3OSMC1:/var/lib/connman$
Reboot. Got a sad face before OSMC started. Not sure what that means, but eventually OSMC did start.
My OSMC > Network > Wireless
Select 5G network
Connect to SSID Yes
Enter password
Change configure network manually to config network using DHCP
IP address, subnet mask, default gateway, and primary DNS assigned to expected values.
Status: wlan0(No internet)
Option to Apply or Reset. Chose Apply. Status changed to No Internet. Option to Apply or Reset remained. Chose reset. Status remained No Interet by choice of Apply or reset disappeared
Reboot
No internet
No Live TV
Sounds like a fail? Time to start over with a fresh load?
Thanks again for your help. What do you think I should do next?
Run route -n again. ifconfig isn’t necessary.
Fresh logs would be useful. First add the default gateway again to try to get an external connection.
- Before you did this, have you disabled the wired adapter?
- the next in your post is hard to understand but if you see “configure network manually”, you have a DHCP config, if you change that and see “configure network using DHCP” you have static/manual ip setting
- can that be that you still have had your LAN cable connected while the reboot and having tried to configure wifi? Then you have both interfaces LAN and WiFi active in your network and only one can get the gateway config even it is getting DHCP config
Restart with deleting the wifi and ethernet directories?
I had about 7 rounds of sad faces before my Pi came to life.
My OSMC currently tells me I’m connected to the internet to my 2.4G network, but when I try to SSH, it takes forever and times out before I can type the default gateway. If I try to paste that route, I get a “software error” from puTTy. I can’t view Live TV.
I guess I can’t what you’re asking right now. I’ll try again later.
Yes, I’ve had the wired adapter disabled throughout this exercise.
I see that now. I think this may have been a misunderstanding on my part for some time. However, now when I see “configure network manually” I know the settings I’m looking at are DHCP. That’s what I’ve been doing most recently.
I think that might have happened, but I’ve had the adapter disabled, so I thought it wouldn’t matter if it remained plugged in. I’ll leave it unplugged and try again.
This is what I did before, right? I’ll do it again, making sure to keep the ethernet cable unplugged and the ethernet adapter disabled.
Again, I appreciate everyone’s help.
I think I’m reaching the end of the line before I start with a fresh install, but if you experts think there is more for me to do, please advise accordingly.
Here is my latest effort (results don’t look good):
Ethernet enabled, plugged in, and connected.
Wifi disabled. Dongle unplugged. Onboard wifi disabled via dtoverlay=sdhost.
Removed directories from /var/lib/connman as per Jim’s previous suggestion.
Ethernet cable still plugged in, Wifi dongle still unplugged
Reboot
Disable ethernet via My OSMC
Unplug ethernet cable
Plug in OSMC dongle
Enable wifi via My OSMC. Wifi SSIDs not visible, so need to back out of My OSMC and come back.
Back out of My OSMC
Go back to My OSMC > Networking > Wireless
Select 5G network
Enter password
Looking at “Configure Network Manually”, so the configuration I’m looking at is DHCP, including IP address, Subnet Mask, Default Gateway, and Primary DNS. Secondary DNS is blank
Status: wlan0 (No Internet)
I have the option of Selecting “Apply” or “Reset”
Any thoughts on what to do next? I’m just going to leave it sit until I hear back.
Thanks again very much for all the support.
Simply hit apply
Thank you, Jim. I just did that. When I did, OSMC backed me out to the My OSMC > Network screen without any feedback. I reselected Wireless and observed Status No Internet.
I’m tempted to try connecting to the 2.4G SSID but I’ll await your advice.
That should not happen, it should change to “Connected” after hit the apply field.
Oh dear, very hard nut. Perhaps, the delay was to long between the wifi connect and the apply action.
Are you able to ssh into the box?
No, not while “connected” to the 5G SSID
I tried again. I disconnected and forgot, then tried to reconnect. I entered the password and immediately selected “Apply”. Same result.
For grins, I next tried to connect to the 2.4G SSID (they are different SSIDs). So, I disconnected again from the 5G, then tried to connect at 2.4G. As soon as I entered the password, I chose apply. Once again, OSMC popped me up one level of the interface, but this time, when I returned, I observed
Status Connected.
When I tried to ssh into the box while “connected” to 2.4G, the connection timed out.
The only way I’ve been able to reliably ssh into the box in the last 8 hours or so was when the ethernet adapter was enabled and plugged in.
I’m getting the feeling your router tricks us … but I’ve no clue about this model.
Ok, lets see what we find:
- reconnect the LAN cable
- enable wired within MyOSMC
- ssh to the box using the ip of the wired connection
- go to /var/lib/connman
- ls -al and provide the output here
- go into each of the directories wifi* and ethernet* and give the output of “cat settings” here
- output of “ip addr”
- output of “ip route”
Some routers don’t establish a default route and I’m not sure why.
route add in rc.local is a quick and dirty hack that will work
Thanks Jim! Here is most of what you’re looking for, I think. I can’t figure out how to get the “cat settings” (see below). Please advise on that and I’ll do it.
Done
osmc@RPi3OSMC1:~$ cd /var/lib/connman
osmc@RPi3OSMC1:/var/lib/connman$ ls -al
total 24
drwxr-xr-x 5 root root 4096 Mar 2 19:21 .
drwxr-xr-x 16 root root 4096 Feb 7 07:23 ..
drwx------ 2 root root 4096 Mar 2 19:21 ethernet_b827eb83727e_cable
-rw------- 1 root root 179 Mar 2 19:21 settings
drwx------ 2 root root 4096 Mar 2 17:53 wifi_000000000000_3239436f766552642d35 47_managed_psk
drwx------ 2 root root 4096 Mar 2 17:56 wifi_000000000000_3239436f76655264_man aged_psk
osmc@RPi3OSMC1:/var/lib/connman$ ls
ethernet_b827eb83727e_cable settings wifi_000000000000_3239436f766552642d3547_managed_psk wifi_000000000000_3239436f76655264_managed_psk
I see there are three relevant directories and get “cat settings” from, but, unfortunately, I don’t know how to do that.
osmc@RPi3OSMC1:/var/lib/connman$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:83:72:7e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.96/24 brd 192.168.1.255 scope global eth0
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,DYNAMIC> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 7c:dd:90:b7:67:5b brd ff:ff:ff:ff:ff:ff
osmc@RPi3OSMC1:/var/lib/connman$ ^C
osmc@RPi3OSMC1:/var/lib/connman$ ip route
default via 192.168.1.254 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.96
192.168.1.254 dev eth0 scope link
osmc@RPi3OSMC1:/var/lib/connman$ ^C
osmc@RPi3OSMC1:/var/lib/connman$ ip route
default via 192.168.1.254 dev eth0
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.96
192.168.1.254 dev eth0 scope link
osmc@RPi3OSMC1:/var/lib/connman$ ^C
I think I figured out how to login as root and collect the rest of the information we’re looking for:
osmc@RPi3OSMC1:/var/lib/connman$ sudo su
root@RPi3OSMC1:/var/lib/connman# cd /ethernet_b827eb83727e_cable
bash: cd: /ethernet_b827eb83727e_cable: No such file or directory
root@RPi3OSMC1:/var/lib/connman# cd /var/lib/connman/ethernet_b827eb83727e_cable
root@RPi3OSMC1:/var/lib/connman/ethernet_b827eb83727e_cable# ls
data settings
root@RPi3OSMC1:/var/lib/connman/ethernet_b827eb83727e_cable# cat data
root@RPi3OSMC1:/var/lib/connman/ethernet_b827eb83727e_cable# cat settings
[ethernet_b827eb83727e_cable]
Name=Wired
AutoConnect=true
Modified=2018-03-03T01:21:42.025697Z
IPv4.method=dhcp
IPv4.DHCP.LastAddress=192.168.1.96
IPv6.method=off
IPv6.privacy=disabled
root@RPi3OSMC1:/var/lib/connman/ethernet_b827eb83727e_cable#
root@RPi3OSMC1:/var/lib/connman/ethernet_b827eb83727e_cable# cd /var/lib/connman/wifi_000000000000_3239436f766552642d3547_managed_psk
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f766552642d3547_managed_psk# ls
data settings
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f766552642d3547_managed_psk# cat settings
[wifi_000000000000_3239436f766552642d3547_managed_psk]
Name=29CoveRd-5G
SSID=3239436f766552642d3547
Frequency=5220
Favorite=false
AutoConnect=true
Modified=2018-03-02T23:51:49.824839Z
IPv4.method=dhcp
IPv6.method=off
IPv6.privacy=disabled
IPv4.DHCP.LastAddress=192.168.1.94
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f766552642d3547_managed_psk#
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f766552642d3547_managed_psk# cd /var/lib/connman/wifi_000000000000_3239436f76655264_managed_psk
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f76655264_managed_psk# ls
data settings
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f76655264_managed_psk# cat settings
[wifi_000000000000_3239436f76655264_managed_psk]
Name=29CoveRd
SSID=3239436f76655264
Frequency=2437
Favorite=true
AutoConnect=true
Modified=2018-03-02T23:56:08.250971Z
Passphrase=8174858821
IPv4.method=dhcp
IPv6.method=off
IPv6.privacy=disabled
IPv4.DHCP.LastAddress=192.168.1.94
root@RPi3OSMC1:/var/lib/connman/wifi_000000000000_3239436f76655264_managed_psk#Just in case anyone was wondering, I did a fresh install of OSMC, without NOOBS, and had exactly the same problems as described here: Connection with internet with the dongle at 2.4G, connection with no internet at 5G. Ethernet works fine.
If it’s not a defective dongle, then something must be up with the router. On that score, please note that I have about 10 devices connected wirelessly to the router at all times, some connections at 2.4G and others at 5G. The Pi running OSMC is the only device that is giving me problems.
So, back to our current diagnostic thread, I guess.
I think if you can confirm that it works with the OSMC dongle using static IP than I am pretty sure we can exclude a hardware failure and need to look into a conflict between the driver and your router.
Alternatively it would be interesting how the OSMC performs if you use it on your PC
Have you tried setting a default gateway in rc.local?