From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Aw: Re: GUI for WLanAP doesn't reflect current settings for
 'noscan' option
Date: Sat, 09 Mar 2019 23:21:48 +0100
Message-ID: <36a367d1-686a-6f2a-721d-d1fa62f06717@ipfire.org>
In-Reply-To:
 <trinity-22559968-f7cd-4b87-abb2-9ba4f0352c8c-1552166357318@3c-app-gmx-bs71>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============2349104236553787300=="
List-Id: <development.lists.ipfire.org>

--===============2349104236553787300==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hi Bernhard,

On 09.03.2019 22:19, Bernhard Bitsch wrote:
> ...
>> On 09.03.2019 21:15, Matthias Fischer wrote:
>> > ...
>> Could you please check the resulting values for ON and OFF settings?
>>=20
>> Here:
>>=20
>> wlanap.cgi - ON is checked:
>> /var/ipfire/wlanap/hostapd.conf =3D> noscan=3D1
>> /var/ipfire/wlanap/settings =3D> NOSCAN=3Don
>>=20
>> wlanap.cgi - OFF is checked:
>> /var/ipfire/wlanap/hostapd.conf =3D> noscan=3D0
>> /var/ipfire/wlanap/settings =3D> NOSCAN=3DOFF
>>=20
>> Do you get the same results?
>>=20
>> Best,
>> Matthias
>>=20
>=20
> No, it's just the other way. Just as the original line reads, I think.
> I also checked the functionality. If I check "Neighbourhood scan=3Doff" hos=
tapd generates a 40MHZ signal, and vice versa.
> The semantics are ok also: "Neighbour scan=3Doff" --> scan --> noscan=3D0.

Ok, I think I mixed this up somehow before. After correcting the above line b=
ack to original I get:

wlanap.cgi - ON is checked:
/var/ipfire/wlanap/hostapd.conf =3D> noscan=3D0
/var/ipfire/wlanap/settings =3D> NOSCAN=3Doff
=20
wlanap.cgi - OFF is checked:
/var/ipfire/wlanap/hostapd.conf =3D> noscan=3D1
/var/ipfire/wlanap/settings =3D> NOSCAN=3Don

And the appropriate choice remains checked. Duh!

Correct!?

Best,
Matthias

--===============2349104236553787300==--