I haven’t managed to get connected to a WPA network either so it looks
like open only at the moment but I fear that may just have been a
fluke.
A big problem I’m facing is that editing /etc/default/crda to
REGDOMAIN=GB wasn’t enough to set the wifi regulation mode to GB and I
have to set it manually. This sometimes works and sometimes reports
the following:
country 98: DFS-UNSET
(2402 - 2472 @ 40), (N/A, 20), (N/A)
(2457 - 2472 @ 15), (N/A, 20), (N/A), NO-IR
(5170 - 5250 @ 80), (N/A, 17), (N/A), NO-IR
(5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, NO-IR
(5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, NO-IR
(5735 - 5835 @ 80), (N/A, 20), (N/A), NO-IR
(57240 - 63720 @ 2160), (N/A, 0), (N/A)
At best this is simply an annoyance but at worst I’m thinking this may
be responsible for the issues I’m seeing.
Is there anywhere else I can force this to be set to GB?
Christopher Williamson
On 22 July 2016 at 17:54:40, Christopher Williamson
([email protected](mailto:[email protected])) wrote:
> Disregard - I have actually managed to get this to connect to a open network!
>
> # iw reg set GB
> # iw reg get
> country GB: DFS-ETSI
> (2402 - 2482 @ 40), (N/A, 20), (N/A)
> (5170 - 5250 @ 80), (N/A, 20), (N/A)
> (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
> (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
> (57000 - 66000 @ 2160), (N/A, 40), (N/A)
> # iwconfig wlan0 essid "shaunthesheep-guest”
> # dhclient wlan0
>
> It’s good to have some progress - so it looks like the issue preventing the
> previous connection was the iw reg not being set properly (or possibly 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
> ([email protected](mailto:[email protected])) wrote:
>
> >
> > Ok so I created a guest wifi network without any encryption enabled at all
> > and the client still refuses to connect.
> >
> > Again, the connection is made perfectly using the USB dongle I have but not
> > the built in libertas sd8686 chipset.
> >
> > I do currently use pfSense as a firewall box behind my wireless router
> > (acting as an AP) and can see that no DHCP request is making it to the
> > pfSense box. I believe you are right in the point about the firmware being
> > the problem here.
> >
> > I should also confirm - the firmware in use is the latest from the
> > linux-firmware Ubuntu 16.04 package. I did read around the net about being
> > having various issues with various firmware sources and not others but
> > despite trying firmware linked directly from Marvell I seem to always get
> > one of two issues:
> >
> > 1.) I am unable to connect and keep getting asked for passphrases, or:
> > 2.) The system completely freezes up (with the v8 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
> > ([email protected](mailto:[email protected])) 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
> > > libertas device:
> > >
> > > USB: http://termbin.com/hdwl
> > > Libertas: http://termbin.com/jxh7
> > >
> > > Will follow up shortly with WPA and Open network configs.
> > >
> > > Christopher Williamson
> > >
> > >
> > >
> > > On 22 July 2016 at 17:16:29, Dan Williams
> > > ([email protected](mailto:[email protected])) 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
> > > > libertas device:
> > > >
> > > > USB: http://termbin.com/hdwl
> > > > Libertas: http://termbin.com/jxh7
> > > >
> > > > Will follow up shortly with WPA and Open network configs.
> > > >
> > > > *Christopher Williamson*
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
