From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Fischer To: development@lists.ipfire.org Subject: Re: Aw: GUI for WLanAP doesn't reflect current settings for 'noscan' option Date: Sat, 09 Mar 2019 21:59:39 +0100 Message-ID: <9968de9b-3772-da9e-3672-2e70bcf2bbc6@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2067033274154657471==" List-Id: --===============2067033274154657471== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Bernhard, On 09.03.2019 21:15, Matthias Fischer wrote: > ... >>> Can anyone confirm? >>>=20 >> Cannot confirm this. The WUI just shows the last saved stated as checked. = >> Switch to off / save --> off is checked >> Switch to on / save --> on is checked Hm. Could you please check the resulting values for ON and OFF settings? Here: wlanap.cgi - ON is checked: /var/ipfire/wlanap/hostapd.conf =3D> noscan=3D1 /var/ipfire/wlanap/settings =3D> NOSCAN=3Don wlanap.cgi - OFF is checked: /var/ipfire/wlanap/hostapd.conf =3D> noscan=3D0 /var/ipfire/wlanap/settings =3D> NOSCAN=3DOFF Do you get the same results? Best, Matthias >> Best, >> Bernhard >=20 > Thanks for the feedback, but that is strange. >=20 > To get it working as expected, I had to change line 423 from: >=20 > $Lang::tr{'wlanap neighbor scan'}:&nbs= p;on | off$Lang::tr{'wlanap neighbor scan warning'} >=20 > To: >=20 > $Lang::tr{'wlanap neighbor scan'}:&nbs= p;on | off$Lang::tr{'wlanap neighbor scan warning'} >=20 > Don't know if I'm just puzzled, but whatever I did, ON remained checked. >=20 > Will take a closer look again. >=20 > Best, > Matthias >=20 --===============2067033274154657471==--