Re: NetworkManager WiFi AP Mode

From: Ali Nematollahi <alirezan1 gmail com>
To: Dan Williams <dcbw redhat com>
Cc: networkmanager-list gnome org
Subject: Re: NetworkManager WiFi AP Mode
Date: Tue, 7 Jun 2016 12:01:26 -0700

Hey Dan

Yup I forgot to start wpa_supplicant in my earlier logs but this time I did it and I get pretty much the same thing, but with a little bit more detailed logs...

root beaglebone:~# NetworkManager --debug &

[2] 2902

root beaglebone:~#

(NetworkManager:2902): NetworkManager-WARNING **: <warn> glib-version: cannot handle SIGUSR1 and SIGUSR2 signals. Consider upgrading glib to 2.36.0 or newer

NetworkManager[2902]: <info> NetworkManager (version 1.0.10) is starting...

NetworkManager[2902]: <info> Read config: /etc/NetworkManager/NetworkManager.conf

NetworkManager[2902]: <info> init!

NetworkManager[2902]: <info> update_system_hostname

NetworkManager[2902]: <info> interface-parser: parsing file /etc/network/interfaces

NetworkManager[2902]: <info> interface-parser: finished parsing file /etc/network/interfaces

NetworkManager[2902]: <info> guessed connection type (eth0) = 802-3-ethernet

NetworkManager[2902]: <info> update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e

NetworkManager[2902]: <info> adding eth0 to connections

NetworkManager[2902]: <info> adding iface eth0 to eni_ifaces

NetworkManager[2902]: <info> autoconnect

NetworkManager[2902]: <info> management mode: unmanaged

NetworkManager[2902]: <info> devices added (path: /sys/devices/ocp.2/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx.2.auto/net/wlan0, iface: wlan0)

NetworkManager[2902]: <info> device added (path: /sys/devices/ocp.2/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx.2.auto/net/wlan0, iface: wlan0): no ifupdown configuration found.

NetworkManager[2902]: <info> devices added (path: /sys/devices/ocp.2/481cc000.d_can/net/can0, iface: can0)

NetworkManager[2902]: <info> device added (path: /sys/devices/ocp.2/481cc000.d_can/net/can0, iface: can0): no ifupdown configuration found.

NetworkManager[2902]: <info> devices added (path: /sys/devices/ocp.2/481d0000.d_can/net/can1, iface: can1)

NetworkManager[2902]: <info> device added (path: /sys/devices/ocp.2/481d0000.d_can/net/can1, iface: can1): no ifupdown configuration found.

NetworkManager[2902]: <info> devices added (path: /sys/devices/ocp.2/4a100000.ethernet/net/eth0, iface: eth0)

NetworkManager[2902]: <info> locking wired connection setting

NetworkManager[2902]: <info> devices added (path: /sys/devices/virtual/net/lo, iface: lo)

NetworkManager[2902]: <info> device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.

NetworkManager[2902]: <info> end _init.

NetworkManager[2902]: <info> Loaded settings plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. (/usr/lib/NetworkManager/libnm-settings-plugin-ifupdown.so)

NetworkManager[2902]: <info> (1416752) ... get_connections.

NetworkManager[2902]: <info> (1416752) ... get_connections (managed=false): return empty list.

NetworkManager[2902]: <info> keyfile: new connection /etc/NetworkManager/system-connections/Hotspot (3e13073d-6d7a-440d-ab2b-4f42c9fdacaf,"Hotspot")

NetworkManager[2902]: <info> keyfile: new connection /etc/NetworkManager/system-connections/modem0 (084cef7e-d695-4677-bca8-8ac435c6f754,"modem0")

NetworkManager[2902]: <info> get unmanaged devices count: 1

NetworkManager[2902]: <info> monitoring kernel firmware directory '/lib/firmware'.

NetworkManager[2902]: <info> rfkill0: found WiFi radio killswitch (at /sys/devices/ocp.2/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx.2.auto/ieee80211/phy0/rfkill0) (driver wl18xx_driver)

NetworkManager[2902]: <info> WiFi hardware radio set enabled

NetworkManager[2902]: <info> WWAN hardware radio set enabled

NetworkManager[2902]: <info> Loaded device plugin: NMVxlanFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMVlanFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMVethFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMTunFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMMacvlanFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMInfinibandFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMGreFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMEthernetFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMBridgeFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMBondFactory (internal)

NetworkManager[2902]: <info> Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/libnm-device-plugin-wifi.so)

NetworkManager[2902]: <warn> (/libnm-device-plugin-bluetooth.so): failed to load plugin: /usr/lib/NetworkManager/libnm-device-plugin-bluetooth.so: undefined symbol: g_clear_pointer

NetworkManager[2902]: <info> Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/libnm-device-plugin-wwan.so)

NetworkManager[2902]: <info> Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/libnm-device-plugin-adsl.so)

NetworkManager[2902]: <info> WiFi enabled by radio killswitch; enabled by state file

NetworkManager[2902]: <info> WWAN enabled by radio killswitch; enabled by state file

NetworkManager[2902]: <info> WiMAX enabled by radio killswitch; enabled by state file

NetworkManager[2902]: <info> Networking is enabled by state file

NetworkManager[2902]: <info> (eth0): new Ethernet device (carrier: OFF, driver: 'cpsw', ifindex: 4)

NetworkManager[2902]: <info> (lo): link connected

NetworkManager[2902]: <info> (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1)

NetworkManager[2902]: <info> (wlan0): using nl80211 for WiFi device control

NetworkManager[2902]: <info> (wlan0): driver supports Access Point (AP) mode

NetworkManager[2902]: <info> (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'wl18xx_driver', ifindex: 5)

NetworkManager[2902]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]

[ 107.592112] wlcore: PHY firmware version: Rev 8.2.0.0.195

[ 107.682702] wlcore: firmware booted (Rev 8.8.0.0.13)

NetworkManager[2902]: <info> (can0): new Generic device (carrier: UNKNOWN, driver: 'c_can_platform', ifindex: 2)

NetworkManager[2902]: <info> (can1): new Generic device (carrier: UNKNOWN, driver: 'c_can_platform', ifindex: 3)

NetworkManager[2902]: <info> wpa_supplicant running

NetworkManager[2902]: <info> (wlan0) supports 1 scan SSIDs

NetworkManager[2902]: <info> (wlan0): supplicant interface state: starting -> ready

NetworkManager[2902]: <info> startup complete

NetworkManager[2902]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]

NetworkManager[2902]: <info> Auto-activating connection 'Hotspot'.

NetworkManager[2902]: <info> (wlan0): Activation: starting connection 'Hotspot' (3e13073d-6d7a-440d-ab2b-4f42c9fdacaf)

NetworkManager[2902]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]

NetworkManager[2902]: <info> NetworkManager state is now CONNECTING

NetworkManager[2902]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]

NetworkManager[2902]: <info> (wlan0): Activation: (wifi) connection 'Hotspot' has security, and secrets exist. No new secrets needed.

NetworkManager[2902]: <warn> (wlan0): Supplicant may not support AP mode; connection may time out.

NetworkManager[2902]: <info> Config: added 'ssid' value 'AliAP'

NetworkManager[2902]: <info> Config: added 'mode' value '2'

NetworkManager[2902]: <info> Config: added 'frequency' value '2412'

NetworkManager[2902]: <info> Config: added 'key_mgmt' value 'WPA-PSK'

NetworkManager[2902]: <info> Config: added 'psk' value '<omitted>'

NetworkManager[2902]: <info> Config: set interface ap_scan to 2

wlan0: AP mode support not included in the build

NetworkManager[2902]: <info> (wlan0): supplicant interface state: ready -> scanning

root beaglebone:~# ifconfig

eth0 Link encap:Ethernet HWaddr ec:24:b8:cf:e0:be

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)

Interrupt:56

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:1 errors:0 dropped:0 overruns:0 frame:0

TX packets:1 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:112 (112.0 B) TX bytes:112 (112.0 B)

wlan0 Link encap:Ethernet HWaddr 5c:31:3e:ce:be:5b

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)

In my set up prior to using NM, I use ifconfig to assign a static IP address of 10.4.30.34 to the wlan0 interface myself. I'd rather use the same IP here and I'm not sure how. and the interface itself isn't getting an IP anyway, so there's still a sticky point :(

On Tue, Jun 7, 2016 at 11:03 AM, Dan Williams <dcbw redhat com> wrote:

On Mon, 2016-06-06 at 15:06 -0700, Ali Nematollahi wrote:
> Hi Dan
>
> Here are the outputs:
>
> root beaglebone:~# nmcli radio
> WIFI-HW  WIFI     WWAN-HW  WWAN
> enabled  enabled  enabled  enabled
>
> root beaglebone:~# rfkill list
> 0: phy0: Wireless LAN
>         Soft blocked: no
>         Hard blocked: no

Ok, that's not the problem then... In an earlier log you had:

NetworkManager[2845]: <info>  (wlan0) supports 1 scan SSIDs
NetworkManager[2845]: <info>  (wlan0): supplicant interface state:
starting -> ready
NetworkManager[2845]: <info>  (wlan0): device state change: unavailable
-> disconnected (reason 'supplicant-available') [20 30 42]

Do you see that "unavailable -> disconnected" in the logs now? When
the supplicant gets started, the device should move to the
'disconnected' state (your latest logs here show the device in
'unavailable' state). Can you make sure the supplicant is running
again?

Dan

> ifconfig
> eth0      Link encap:Ethernet  HWaddr ec:24:b8:cf:e0:be
>           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)
>           Interrupt:56
>
> 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:1 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:112 (112.0 B)  TX bytes:112 (112.0 B)
>
> wlan0     Link encap:Ethernet  HWaddr 5c:31:3e:ce:be:5b
>           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)
>
>
> On Mon, Jun 6, 2016 at 2:28 PM, Dan Williams <dcbw redhat com> wrote:
>
> >
> > On Mon, 2016-06-06 at 13:22 -0700, Ali Nematollahi wrote:
> > >
> > > Hi Dan
> > > root beaglebone:~# nmcli -f all dev show wlan0
> > > GENERAL.DEVICE:                         wlan0
> > > GENERAL.TYPE:                           wifi
> > > GENERAL.NM-TYPE:                        NMDeviceWifi
> > > GENERAL.VENDOR:
> > > GENERAL.PRODUCT:
> > > GENERAL.DRIVER:                         wl18xx_driver
> > > GENERAL.DRIVER-VERSION:                 3.12.10-svn34
> > > GENERAL.FIRMWARE-VERSION:               N/A
> > > GENERAL.HWADDR:                         5C:31:3E:CE:BE:5B
> > > GENERAL.MTU:                            1500
> > > GENERAL.STATE:                          20 (unavailable)
> > So here's why: the device is listed as unavailable.  Let's check
> > rfkill
> > to make sure NM isn't being told to put wlan0 into airplane mode:
> >
> > nmcli radio
> >
> > and you should see something like this:
> >
> > WIFI-HW  WIFI     WWAN-HW  WWAN
> > enabled  enabled  enabled  enabled
> >
> > In this case, my WiFi is enabled; if one of those two is 'disabled'
> > for
> > you, then we can dig deeper into that.  Also, grab:
> >
> > rfkill list
> >
> > Dan
> >
> > >
> > > GENERAL.REASON:                         2 (Device is now managed)
> > > GENERAL.UDI:
> > > /sys/devices/ocp.2/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:000
> > > 1:2/
> > > wl18xx.2.auto/net/wlan0
> > > GENERAL.IP-IFACE:
> > > GENERAL.IS-SOFTWARE:                    no
> > > GENERAL.NM-MANAGED:                     yes
> > > GENERAL.AUTOCONNECT:                    yes
> > > GENERAL.FIRMWARE-MISSING:               no
> > > GENERAL.PHYS-PORT-ID:                   --
> > > GENERAL.CONNECTION:                     --
> > > GENERAL.CON-UUID:                       --
> > > GENERAL.CON-PATH:                       --
> > > GENERAL.METERED:                        unknown
> > > CAPABILITIES.CARRIER-DETECT:            no
> > > CAPABILITIES.SPEED:                     unknown
> > > CAPABILITIES.IS-SOFTWARE:               no
> > > WIFI-PROPERTIES.WEP:                    yes
> > > WIFI-PROPERTIES.WPA:                    yes
> > > WIFI-PROPERTIES.WPA2:                   yes
> > > WIFI-PROPERTIES.TKIP:                   yes
> > > WIFI-PROPERTIES.CCMP:                   yes
> > > WIFI-PROPERTIES.AP:                     yes
> > > WIFI-PROPERTIES.ADHOC:                  yes
> > > WIFI-PROPERTIES.2GHZ:                   yes
> > > WIFI-PROPERTIES.5GHZ:                   yes
> > > CONNECTIONS.AVAILABLE-CONNECTION-PATHS:
> > >
> > > nmcli con up Hotspot
> > > Error: Connection activation failed: No suitable device found for
> > > this
> > > connection.
> > >
> > >
> > > Thanks!
> > >
> > >
> > > On Mon, Jun 6, 2016 at 9:17 AM, Dan Williams <dcbw redhat com>
> > > wrote:
> > >
> > > >
> > > >
> > > > On Fri, 2016-06-03 at 13:49 -0700, Ali Nematollahi wrote:
> > > > >
> > > > >
> > > > > That was a great point Dan. It went one step forward:
> > > > >
> > > > > ....
> > > > > [ 2299.953517] [sched_delayed] sched: RT throttling activated
> > > > > [ 2300.344384] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM
> > > > > 0x11)
> > > > > NetworkManager[2845]: <info>  (wlan0): using nl80211 for WiFi
> > > > > device
> > > > > control
> > > > > [ 2300.379934] wlcore: loaded
> > > > > [ 2300.382856] wlcore: driver version:
> > > > > NetworkManager[2845]: <info>  (wlan0): driver supports Access
> > > > > Point
> > > > > (AP)
> > > > > mode
> > > > > NetworkManager[2845]: <info>  (wlan0): new 802.11 WiFi device
> > > > > (carrier:
> > > > > UNKNOWN, driver: 'wl18xx_driver', ifindex: 5)
> > > > > NetworkManager[2845]: <info>  rfkill0: found WiFi radio
> > > > > killswitch
> > > > > (at
> > > > > /sys/devices/ocp.2[ 2300.415536] wlcore: compilation time:
> > > > > Thu
> > > > > Jun 26
> > > > > 11:35:53 2014
> > > > > /47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:0001:2/wl18xx.2.au
> > > > > to/i
> > > > > eee8
> > > > > 0211/phy0/rfkill0)
> > > > > (driver wl18xx_driver)
> > > > > NetworkManager[2845]: <info>  devices added (path:
> > > > > /sys/devices/ocp.2/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:
> > > > > 0001
> > > > > :2/w
> > > > > l18xx.2.auto/net/wlan0,
> > > > > iface: wlan0)
> > > > > NetworkManager[2845]: <info>  device added (path:
> > > > > /sys/devices/ocp.2/47810000.mmc/mmc_host/mmc2/mmc2:0001/mmc2:
> > > > > 0001
> > > > > :2/w
> > > > > l18xx.2.auto/net/wlan0,
> > > > > iface: wlan0): no ifupdown configuration found.
> > > > > NetworkManager[2845]: <info>  wpa_supplicant running
> > > > > NetworkManager[2845]: <info>  (wlan0): device state change:
> > > > > unmanaged
> > > > > ->
> > > > > unavailable (reason 'managed') [10 20 2]
> > > > > [ 2300.952925] wlcore: PHY firmware version: Rev 8.2.0.0.195
> > > > > [ 2301.042483] wlcore: firmware booted (Rev 8.8.0.0.13)
> > > > > NetworkManager[2845]: <info>  (wlan0) supports 1 scan SSIDs
> > > > > NetworkManager[2845]: <info>  (wlan0): supplicant interface
> > > > > state:
> > > > > starting
> > > > > -> ready
> > > > > NetworkManager[2845]: <info>  (wlan0): device state change:
> > > > > unavailable ->
> > > > > disconnected (reason 'supplicant-available') [20 30 42]
> > > > >
> > > > > root beaglebone:/etc/NetworkManager/system-connections#
> > > > > ifconfig
> > > > > eth0      Link encap:Ethernet  HWaddr ec:24:b8:cf:e0:be
> > > > >           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)
> > > > >           Interrupt:56
> > > > >
> > > > > 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:0 errors:0 dropped:0 overruns:0 frame:0
> > > > >           TX packets:0 errors:0 dropped:0 overruns:0
> > > > > carrier:0
> > > > >           collisions:0 txqueuelen:0
> > > > >           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
> > > > >
> > > > > wlan0     Link encap:Ethernet  HWaddr 5c:31:3e:ce:be:5b
> > > > >           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)
> > > > >
> > > > >
> > > > >
> > > > > I see the supplicant-available message and wlan0 comes up as
> > > > > it
> > > > > did
> > > > > before
> > > > > but still there's no IP address nor SSID is broadcast. Should
> > > > > I
> > > > > do an
> > > > > ipconfig to assign an IP to the interface manually? What
> > > > > about
> > > > > SSID
> > > > > broadcast?
> > > > No, you shouldn't need to do that.  It looks like NM isn't
> > > > starting
> > > > the
> > > > AP connection at all.  Could you run:
> > > >
> > > > nmcli -f all dev show wlan0 | grep AVAIL
> > > >
> > > > and let's see what connections/profiles NM things the wifi
> > > > interface
> > > > can activate.  Next, try:
> > > >
> > > > nmcli con up Hotspot
> > > >
> > > > and lets see what NM says to that.
> > > >
> > > > Dan
> > > >
> > > > >
> > > > >
> > > > > Thanks!
> > > > >
> > > > > On Fri, Jun 3, 2016 at 8:25 AM, Dan Williams <dcbw redhat com
> > > > > >
> > > > > wrote:
> > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Thu, 2016-06-02 at 15:03 -0700, Ali Nematollahi wrote:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hi guys
> > > > > > >
> > > > > > > I'm trying to use NM to start a WiFi AP mode. I've had
> > > > > > > some
> > > > > > > success
> > > > > > > but a
> > > > > > > big portion of the process is very unclear to me and I'm
> > > > > > > hoping
> > > > > > > to
> > > > > > > get some
> > > > > > > help.
> > > > > > >
> > > > > > > So I have this NM configuration:
> > > > > > >
> > > > > > > # cat Hotspot
> > > > > > > [connection]
> > > > > > > id=Hotspot
> > > > > > > uuid=3e13073d-6d7a-440d-ab2b-4f42c9fdacaf
> > > > > > > type=802-11-wireless
> > > > > > > autoconnect=true
> > > > > > >
> > > > > > > [802-11-wireless]
> > > > > > > ssid=AliAP
> > > > > > > mode=ap
> > > > > > > security=802-11-wireless-security
> > > > > > >
> > > > > > > [802-11-wireless-security]
> > > > > > > key-mgmt=wpa-psk
> > > > > > > psk=alisecurepassword984364 234@
> > > > > > >
> > > > > > > [ipv4]
> > > > > > > method=shared
> > > > > > >
> > > > > > > [ipv6]
> > > > > > > method=auto
> > > > > > Looks good so far.
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > With this, the NM starts up and does what it needs to do
> > > > > > > (I
> > > > > > > think):
> > > > > > > (NetworkManager:2989): NetworkManager-WARNING **:
> > > > > > > <warn>  glib-
> > > > > > > version:
> > > > > > > cannot handle SIGUSR1 and SIGUSR2 signals. Consider
> > > > > > > upgrading
> > > > > > > glib to
> > > > > > > 2.36.0 or newer
> > > > > > > NetworkManager[2989]: <info>  NetworkManager (version
> > > > > > > 1.0.10)
> > > > > > > is
> > > > > > > starting...
> > > > > > > NetworkManager[2989]: <info>  Read config:
> > > > > > > /etc/NetworkManager/NetworkManager.conf
> > > > > > > NetworkManager[2989]: <info>  init!
> > > > > > > NetworkManager[2989]: <info>  update_system_hostname
> > > > > > <snip>
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > NetworkManager[2989]: <info>  (wlan0): new 802.11 WiFi
> > > > > > > device
> > > > > > > (carrier:
> > > > > > > UNKNOWN, driver: 'wl18xx_driver', ifindex: 5)
> > > > > > > NetworkManager[2989]: <info>  (wlan0): device state
> > > > > > > change:
> > > > > > > unmanaged
> > > > > > > ->
> > > > > > > unavailable (reason 'managed') [10 20 2]
> > > > > > > [ 1424.134834] wlcore: PHY firmware version: Rev
> > > > > > > 8.2.0.0.195
> > > > > > > [ 1424.222506] wlcore: firmware booted (Rev 8.8.0.0.13)
> > > > > > > [ 1424.244537] wlcore: down
> > > > > > > [ 1424.664565] wlcore: PHY firmware version: Rev
> > > > > > > 8.2.0.0.195
> > > > > > > [ 1424.752521] wlcore: firmware booted (Rev 8.8.0.0.13)
> > > > > > > NetworkManager[2989]: <info>  (can0): new Generic device
> > > > > > > (carrier:
> > > > > > > UNKNOWN,
> > > > > > > driver: 'c_can_platform', ifindex: 2)
> > > > > > > NetworkManager[2989]: <info>  (can1): new Generic device
> > > > > > > (carrier:
> > > > > > > UNKNOWN,
> > > > > > > driver: 'c_can_platform', ifindex: 3)
> > > > > > > NetworkManager[2989]: <info>  wpa_supplicant stopped
> > > > > > > NetworkManager[2989]: <info>  (wlan0): supplicant
> > > > > > > interface
> > > > > > > state:
> > > > > > > starting
> > > > > > > -> init
> > > > > > Looking at the code, I don't think NM is able to talk to
> > > > > > wpa_supplicant.  This line (starting -> init) will only get
> > > > > > printed
> > > > > > if
> > > > > > D-Bus failed to service activate the supplicant.  There's
> > > > > > two
> > > > > > fixes
> > > > > > there:
> > > > > >
> > > > > > 1) fix whatever problem is wrong with D-Bus service
> > > > > > activation;
> > > > > > this
> > > > > > requires that D-Bus is built with the same --datadir as
> > > > > > wpa_supplicant,
> > > > > > and that the /usr/share/dbus-1/system-
> > > > > > services/fi.w1.wpa_supplicant1.service file exists and
> > > > > > points
> > > > > > to
> > > > > > the
> > > > > > wpa_supplicant binary.
> > > > > >
> > > > > > 2) run the supplicant at system startup with the "-u"
> > > > > > (enable
> > > > > > D-Bus
> > > > > > interface) option; either as a system service via your
> > > > > > normal
> > > > > > service
> > > > > > framework (sysvinit, openrc, systemd, etc) or just launch
> > > > > > it
> > > > > > manually
> > > > > > somehow.
> > > > > >
> > > > > > Once NM can talk to wpa_supplicant, it should start your AP
> > > > > > connection
> > > > > > and actually enable the AP on wlan0.
> > > > > >
> > > > > > Dan
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > # ifconfig
> > > > > > > eth0      Link encap:Ethernet  HWaddr ec:24:b8:cf:e0:be
> > > > > > >           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)
> > > > > > >           Interrupt:56
> > > > > > >
> > > > > > > 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:4 errors:0 dropped:0 overruns:0
> > > > > > > frame:0
> > > > > > >           TX packets:4 errors:0 dropped:0 overruns:0
> > > > > > > carrier:0
> > > > > > >           collisions:0 txqueuelen:0
> > > > > > >           RX bytes:448 (448.0 B)  TX bytes:448 (448.0 B)
> > > > > > >
> > > > > > > wlan0     Link encap:Ethernet  HWaddr 5c:31:3e:ce:be:5b
> > > > > > >           UP BROADCAST MULTICAST  MTU:1500  Metric:1
> > > > > > >           RX packets:49 errors:0 dropped:21 overruns:0
> > > > > > > frame:0
> > > > > > >           TX packets:49 errors:0 dropped:0 overruns:0
> > > > > > > carrier:0
> > > > > > >           collisions:0 txqueuelen:1000
> > > > > > >           RX bytes:7734 (7.5 KiB)  TX bytes:8838 (8.6
> > > > > > > KiB)
> > > > > > >
> > > > > > >
> > > > > > > So WLAN0 is up. Great!
> > > > > > >
> > > > > > > When I was using "iw" and stuff to set up my AP, I used
> > > > > > > to
> > > > > > > start
> > > > > > > hostapd
> > > > > > > and udhcpd to set up the IP address, and start
> > > > > > > broadcasting
> > > > > > > the
> > > > > > > SSID.
> > > > > > > When I get to this point with NM, I was under the
> > > > > > > impression
> > > > > > > that
> > > > > > > NM
> > > > > > > would
> > > > > > > take care of all of this. But I cannot see my SSID on my
> > > > > > > phone. I
> > > > > > > do
> > > > > > > have a
> > > > > > > functioning wpa_supplicant btw.
> > > > > > >
> > > > > > > Out of curiosity, I started hostapd and udhcpd. I could
> > > > > > > get
> > > > > > > hostapd
> > > > > > > to work
> > > > > > > (but not the SSID I set in NM!!) and UDHCPD never worked.
> > > > > > >
> > > > > > > I was wondering what I was missing in this and how I can
> > > > > > > start
> > > > > > > the
> > > > > > > broadcast and activate the DHCPD automatically with NM.
> > > > > > >
> > > > > > > I'm running NM 1.0.10.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Thanks!
> > > > > > > _______________________________________________
> > > > > > > networkmanager-list mailing list
> > > > > > > networkmanager-list gnome org
> > > > > > > https://mail.gnome.org/mailman/listinfo/networkmanager-li
> > > > > > > st

Follow-Ups:
- Re: NetworkManager WiFi AP Mode
  - From: Dan Williams

References:
- NetworkManager WiFi AP Mode
  - From: Ali Nematollahi
- Re: NetworkManager WiFi AP Mode
  - From: Dan Williams
- Re: NetworkManager WiFi AP Mode
  - From: Ali Nematollahi
- Re: NetworkManager WiFi AP Mode
  - From: Dan Williams
- Re: NetworkManager WiFi AP Mode
  - From: Ali Nematollahi
- Re: NetworkManager WiFi AP Mode
  - From: Dan Williams
- Re: NetworkManager WiFi AP Mode
  - From: Ali Nematollahi
- Re: NetworkManager WiFi AP Mode
  - From: Dan Williams

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]