Ok so I recompiled WPA_S with CONFIG_AP=y but same results:
NetworkManager --debug &
[1] 2917
root@beaglebone:~#
(NetworkManager:2917): NetworkManager-WARNING **: glib-version:
cannot handle SIGUSR1 and SIGUSR2 signals. Consider upgrading glib to
2.36.0 or newer
NetworkManager[2917]:
Ah I see. I understand now. Thanks Dan. I'll get that going and will post
my results!
Thanks!!
On Wed, Jun 8, 2016 at 9:26 AM, Dan Williams wrote:
> On Wed, 2016-06-08 at 08:29 -0700, Ali Nematollahi wrote:
> > I can rebuild again but doesn't my current log say:
> >
> >
On Wed, 2016-06-08 at 08:29 -0700, Ali Nematollahi wrote:
> I can rebuild again but doesn't my current log say:
>
> Supported interface modes:
>
> * IBSS
>
> * managed
>
> * AP
>
> * AP/VLAN
>
> Doesn't it mean it supports
I can rebuild again but doesn't my current log say:
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
Doesn't it mean it supports ap mode and it was built with ap support?
On Jun 7, 2016 2:13 PM, "Dan Williams"
On Tue, 2016-06-07 at 13:00 -0700, Ali Nematollahi wrote:
> I've been using AP mode for over a year with the same set up. I use
> many
> commands to set it up but it has been working perfectly fine. Here is
> the
> output you requested:
I misread the error message; it's not from the kernel, but
I've been using AP mode for over a year with the same set up. I use many
commands to set it up but it has been working perfectly fine. Here is the
output you requested:
phy phy0 info
Wiphy phy0
Band 1:
Capabilities: 0x1072
HT20/HT40
On Tue, 2016-06-07 at 12:01 -0700, Ali Nematollahi wrote:
> wlan0: AP mode support not included in the build
Looks like your wifi driver doesn't support AP mode... What does 'iw
phy phy0 info' say in the "Supported interface modes" section?
Dan
___
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 **:
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
>
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
ifconfig
eth0 Link encap:Ethernet HWaddr ec:24:b8:cf:e0:be
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:
>
Hi Dan
here are the outputs:
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
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]: (wlan0): using
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]: (wlan0): using nl80211 for WiFi device control
[ 2300.379934] wlcore: loaded
[
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
>
15 matches
Mail list logo