None of the several entries re: wifi and/or tethering not working relate nor fix my issues.
I have a working RPi3 with newest image OSMC/Kodi and updates and dist-upgrades applied via ethernet cable.
I want the built-in Wifi/wlan0 to be an access point, hotspot, tethered.
Using the GUI OSMC->Networks->Wireless shows Adapter disconnected (even though the checkbox is lit).
No clicking on enable makes it work.
iwconfig and iw are not in the image and there is not enough of a dev env to Make iw.
After adding the WiFi section to lib/connman/setting ifconfig now shows:
lo and eth0 (as static ip) as usual
wlan0 Link encap:Ethernet HWaddr b8:27:eb:0e:bd:30
UP BROADCAST MULTICAST DYNAMIC MTU:1500 Metric:1
RX packets:9 errors:0 dropped:9 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:588 (588.0 B) TX bytes:0 (0.0 B)
Connmanctl technologies shows:
/net/connman/technology/wifi
Name = WiFi
Type = wifi
Powered = True
Connected = False
Tethering = False
TetheringIdentifier = MyHotSpot
TetheringPassphrase = MySecretPhrase
(I have also tried Tethering = True)
Journal shows:
Jan 02 16:58:18 rpi-5-osmc connmand[297]: Adding interface wlan0 [ wifi ]
Jan 02 16:58:18 rpi-5-osmc connmand[297]: eth0 {update} flags 36867
Jan 02 16:58:18 rpi-5-osmc connmand[297]: eth0 {newlink} index 2 address B8:27:EB:5B:E8:67 mtu 1500
Jan 02 16:58:18 rpi-5-osmc connmand[297]: eth0 {newlink} index 2 operstate 2
Jan 02 16:58:18 rpi-5-osmc kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
Jan 02 16:58:18 rpi-5-osmc kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan 02 16:58:18 rpi-5-osmc dbus[275]: [system] Successfully activated service ‘fi.w1.wpa_supplicant1’
Jan 02 16:58:18 rpi-5-osmc wpa_supplicant[357]: Successfully initialized wpa_supplicant
Jan 02 16:58:18 rpi-5-osmc dbus[275]: [system] Successfully activated service ‘org.freedesktop.hostname1’
Jan 02 16:58:18 rpi-5-osmc systemd[1]: Started WPA supplicant.
Jan 02 16:58:18 rpi-5-osmc systemd[1]: Started Hostname Service.
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {update} flags 36931 <UP,RUNNING>
Jan 02 16:58:18 rpi-5-osmc kernel: brcmfmac: brcmf_add_if: ERROR: netdev:wlan0 already exists
Jan 02 16:58:18 rpi-5-osmc kernel: brcmfmac: brcmf_add_if: ignore IF event
Jan 02 16:58:18 rpi-5-osmc kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Jan 02 16:58:18 rpi-5-osmc kernel: brcmfmac: power management disabled
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {newlink} index 3 address B8:27:EB:0E:BD:32 mtu 1500
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {newlink} index 3 operstate 0
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {update} flags 36867
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {newlink} index 3 address B8:27:EB:0E:BD:32 mtu 1500
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {newlink} index 3 operstate 2
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {newlink} index 3 address B8:27:EB:0E:BD:32 mtu 1500
Jan 02 16:58:18 rpi-5-osmc connmand[297]: wlan0 {newlink} index 3 operstate 2
(is operstate DOWN a bad thing?)
Going back into Connmanctl:
connmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Scan completed for wifi
connmanctl> agent on
Agent registered
connmanctl> services
*AO Wired ethernet_b827eb5be867_cable
(note: there is no Wireless listed)
I have gotten further, but not the goal. I still want a working hotspot in that end of the house.
The GUI (wish I knew how to take a screen capture) shows Wireless as no connection. Tethering shows (grayed out) my SSID and passcode and a disable control.
The journal shows:
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listen normally on 2 lo 127.0.0.1 UDP 123
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listen normally on 3 eth0 10.0.0.105 UDP 123
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listen normally on 4 tether 192.168.0.1 UDP 123
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listen normally on 5 lo ::1 UDP 123
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listen normally on 6 wlan0 fe80::ba27:ebff:fe0e:bd32 UDP 123
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listen normally on 7 tether fe80::78f3:abff:fe9b:3f2a UDP 123
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: peers refreshed
Jan 09 14:36:43 rpi-5-osmc ntpd[460]: Listening on routing socket on fd #24 for interface updates
how do I change the 192.168.0.1 address?
the access point does not show up in a scan of wifis. It should be broadcasting its SSID?
connman still will not show wifi as a service
/var/lib/connman has no wifi_HASH_psk file created. it does have a settings file with wifi=true, Terhering=true, Terhering.Identifier=osmc and Tehering.Passphrase=mypass
I believe 192.168.0.x is hardcoded in our connection manager when tethering.
Yes. Have you checked if there is any SSID at al?
ConnMan will only show WiFi services if you run ‘scan wifi’ before ‘services’. I am not sure your tethered service would ever be displayed, as I believe ConnMan will only display services that your device can connect to.
Not sure about this.
I would suggest starting with tethering via connmanctl. It is your best chance to get it working and if you make progress with this, do let us know so we can improve My OSMC.
Tethering is largely untested on OSMC, mainly because many dongles (until Pi3) did not support this feature. It will be improved soon.
connman and settings show the value. Journal reports:
Jan 09 14:36:31 rpi-5-osmc wpa_supplicant[332]: Using interface wlan0 with hwaddr b8:27:eb:0e:bd:32 and ssid “osmc”
my phone, tablet, laptop and a wifi printer all do not see any “osmc” though they see the APs at 5 neighbor houses.
3.yes, I run technologies and scan wifi before services (most time agent on also)
that could be true that the tethered wifi is not a connect to device.
4. is ok, probably since it (re: #3) does not think it is a service.
I got what I got by using connmanctl (mostly). Will try some new combinations, but don’t know any hidden magic commands in it.
Riddle > Not a solution but for what it worth I simply enabled the wireless card and afterward enabled the tethering in the menu (with SSID etc), same HW as you. After these 2 steps the wifi was discoverable but the DNS was not passed to clients connected to this AP. I found the solution on the forum:
sudo nano /etc/connman.prefs
Change value of dnsproxy to yes (dnsproxy=yes)
No more issue afterward (reliability, connection, etc). I had to made this change on the 08/2016 image, I don’t know if anything has changed up to now so try without the value edition first.
