Wifi Security service failing
Home › Forums › GeeXboX on ARM SoCs › Wifi Security service failing
This topic contains 2 replies, has 2 voices, and was last updated by
ajay.bhargav 6 days, 23 hours ago.
-
AuthorPosts
-
Hi there,
I am trying to get wifi working on my d2plug. I tried with onboard wifi chipset sd8787 and Asus N10 usb. both gives same error to me.
[FAILED] Failed to start Wi-Fi Security Service.
See ‘systemctl status wpa_supplicant.service’ for details.Details:
—-
wpa_supplicant.service – Wi-Fi Security Service
Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled)
Active: failed (Result: exit-code) since Thu 1970-01-01 01:00:10 BST; 47s ago
Process: 1453 ExecStart=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u (code=exited, status=1/FAILURE)
Main PID: 1453 (code=exited, status=1/FAILURE)Jan 01 01:00:10 geexbox systemd[1]: wpa_supplicant.service: main process exited, code=exited, status=1/FAILURE
Jan 01 01:00:10 geexbox systemd[1]: Failed to start Wi-Fi Security Service.
Jan 01 01:00:10 geexbox systemd[1]: Unit wpa_supplicant.service entered failed state.My configuration file is:
# Network configuration
# Backend software to use for network management (e.g. “connmann, networkmanager, udhcpc, none “)
NETWORK_BACKEND=”connman”# “LAN” or “WLAN” or “” (default is “” <-> “LAN”)
#NETWORK=”LAN”
NETWORK=”WLAN”# Network interface name or address (e.g. “eth0″ or “00:0d:56:ec:ba:0c”)
IFACE=”wlan0″# Static IP address (“” for DHCP) in CIDR format (e.g. “192.168.1.1/24″)
ADDRESS=””# Network gateway (e.g. “192.168.1.254”)
GATEWAY=””# List of DNS servers (e.g. “192.168.1.253 192.168.1.254″)
# This will override the DNS servers from DHCP
DNS_SERVER=””SSID=”****”
# “true” or “”
HIDDEN=””# “WEP” or “PSK” or “” or “RSN”
SECURITY=”PSK”PASSPHRASE=”****”
# set to “” to disable NTP
TIMESERVERS=”0.geexbox.pool.ntp.org 1.geexbox.pool.ntp.org 2.geexbox.pool.ntp.org 3.geexbox.pool.ntp.org”# Services to be started at boot time
TELNET_SERVER=”true”
FTP_SERVER=”true”
HTTP_SERVER=”false”
SAMBA_SERVER=”false”# Use Zeroconf service discovery
ZEROCONF=”true”WAIT_FOR_SLOW_DEVICE=”true”
# Static Samba shares can be defined as shown in the commented examples below,
# where <%>,<@>,<&>,<#> field separators must be present as shown (Note that
# the password cannot contain these special delimiters):
# Change static value to “true” to enable this#STATIC_SMB=”username<%>password<@>ip<&>myservername<#>share1<#>share2<#>share3″
#STATIC_SMB=”<%><@>ip<&>myservername<#>share1″
static=”false”# Dynamic Samba shares : use “SMB_USER” and “SMB_PWD” to automount all discovered shares
# Change dynamic value to “true” to enable this
#SMB_USER=””
#SMB_PWD=””
dynamic=”false”I am not able to get things working. Please help me out.
Regards,
AjayHmm, there is not much I can say about this. Does ‘journalctl’ show any more info? Did you switch to a recent version of Geexbox (CuBox “classic” binaries found here and sources from here) ?
I’m using an EdiMax 7811 on my CuBox. Note that we have patched a modified Realtek driver (the same as RaspberryPi uses) into our CuBox kernel tree. But I don’t think that is the problem here. Maybe it’s worth checking your kernel configuration for missing WiFi stuff…
ok, after some (3 hrs almost) investigation.. I found that libnl and libnl-gen got corrupted, don’t know how. so I took fresh libnl files from geexbox archive and wpa_supplicant started working.
But after that new problem came. D2plug has SD8787 module which can work in both as wifi or host-ap, so two interfaces are created for the same. iwconfig shows uap0 and mlan0. Now the problem is even though /etc/network mentions wlan device as mlan0, but wpa_supplicant still try setup uap0 which gives me error of IOCTL not supported. Is it a bug in connection manager?
If I do wpa_supplicant directly from command line then wifi works fine. I am able to connect to access point. dhcp client (udhcpc) get the lease from dhcp server but does not configure IP address of wifi interface (this is another issue).
-
AuthorPosts
You must be logged in to reply to this topic.