.
So the end result is - the ubuntu 2.4 wpa_supplicant doesn’t work with
libertas+libertas_sdio but it *does* work properly with wpa_supplicant
2.5.
Christopher Williamson
On 23 July 2016 at 13:29:41, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
> Just to follow up
- spent
several days on this already. If anyone has any other ideas on what
could be causing this please do let me know and I’ll follow up if I
experiment this with again.
Christopher Williamson
On 22 July 2016 at 22:47:15, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote
differences but at least I know
this device can work properly on the Linux 4.6.3 (which the livecd is
based on.)
I’ll follow up if and when I find out what the cause of the problem was.
Christopher Williamson
On 22 July 2016 at 22:42:50, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com
force this to be set to GB?
Christopher Williamson
On 22 July 2016 at 17:54:40, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
> Disregard - I have actually managed to get this to connect to a open network!
>
> # iw reg set GB
> # iw reg get
> country GB: D
just wpa_supplicant borking the connection in
some way. I stopped that this time around. I’ll try wpa1 now and
report back.
Christopher Williamson
On 22 July 2016 at 17:39:50, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
>
> Ok so I created a guest wifi network
firmwares I tried)
I’m not really sure what else to try at this point.
Christopher Williamson
On 22 July 2016 at 17:24:52, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
>
> Hi Dan,
>
> I will check out the WPA2 vs WPA vs open wireless thing in a few mins.
.
Christopher Williamson
On 22 July 2016 at 17:16:29, Dan Williams
(d...@redhat.com(mailto:d...@redhat.com)) wrote:
> Hi Dan,
>
> I will check out the WPA2 vs WPA vs open wireless thing in a few mins.
>
> For now though - the iwlist scan results for both a USB device and the
> libert
it for all involved! :P
Christopher Williamson
On 22 July 2016 at 09:21:44, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
>
> I was thinking about redirecting the wpa logging to syslog but figured I’d
> take the lazy way out by abusing curl:
>
&g
I was thinking about redirecting the wpa logging to syslog but figured
I’d take the lazy way out by abusing curl:
curl -s http://termbin.com/cx0e http://termbin.com/bvdj | sort
Resulting combined log file:
http://termbin.com/909y
Christopher Williamson
On 22 July 2016 at 09:09:59, Arend Van
I’ve created cleaner logs (particularly the dmesg one) and have added
timestamps line-by-line to both so it should be easier to track
between the two log files:
wpa_supplicant:
http://termbin.com/cx0e
dmesg | grep libertas:
http://termbin.com/bvdj
Christopher Williamson
On 21 July 2016 at
Sure!
wpa_supplicant logs:
http://termbin.com/z1hg
dmesg logs (grepped for libertas):
http://termbin.com/7rt5
Christopher Williamson
On 21 July 2016 at 21:38:26, Dan Williams
(d...@redhat.com(mailto:d...@redhat.com)) wrote:
> On Thu, 2016-07-21 at 11:55 -0700, Christopher William
wpa_supplicant reports the connection being
“rejected” as seen below:
wlan0: CTRL-EVENT-ASSOC-REJECT bssid=a0:63:91:1e:ee:43 status_code=1
Most of the debug output sadly doesn’t mean a great deal to me - wifi
isn’t really my area of expertise.
On 21 July 2016 at 19:10:56, Christopher Williamson
(h
Sure, here are the results:
http://termbin.com/e8e2
Christopher Williamson
On 21 July 2016 at 16:37:24, Dan Williams
(d...@redhat.com(mailto:d...@redhat.com)) wrote:
> On Wed, 2016-07-20 at 15:16 -0700, Christopher Williamson wrote:
> > I used NetworkManager in the previous test.
>
uses for 16.04 LTS.)
Christopher Williamson
On 20 July 2016 at 23:16:41, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
>
> I used NetworkManager in the previous test.
>
> This time around I have used wpa_supplicant directly and get the following
> re
I used NetworkManager in the previous test.
This time around I have used wpa_supplicant directly and get the
following results:
http://termbin.com/j8ea
Thought I’d throw them on a pastebin since it’s over 700 lines.
Christopher Williamson
On 20 July 2016 at 22:50:34, Dan Williams
(d
Hi Dan,
Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now
built that and dmesg is a much more lively place!
I’ve provided output logs for both when the device is connected and
when a connection attempt is made - hopefully this is useful.
When I first connect the device:
root@n
anyone has any more ideas I would be more than happy to try them!
Thanks for the help so far Dan!
Christopher Williamson
On 19 July 2016 at 18:41:34, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
> So I’ve now disabled IPv6 and have set the GB (Great Britain) regulat
but so far no
further progress on getting this working properly.
Christopher Williamson
On 19 July 2016 at 18:03:16, Christopher Williamson
(h...@chrisaw.com(mailto:h...@chrisaw.com)) wrote:
> Absolutely!
>
> With the debug logging enabled I got the following:
>
> Connecting the d
I get is:
[ 338.076632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
I was expecting more output and am guessing I’ve missed something here.
Christopher Williamson
On 19 July 2016 at 17:38:35, Dan Williams
(d...@redhat.com(mailto:d...@redhat.com)) wrote:
> On Tue, 2016-07-19 at 12
/show_bug.cgi?id=135421
I figured here may be a good place to ask about it and hopefully to
get to the bottom of why it happens and how I can help to fix it.
Happy to provide any information which may be helpful! :)
Christopher Williamson
Note: Apologies for anyone also on the libertas-dev mailing
20 matches
Mail list logo
