Hi Matthias, > Gesendet: Samstag, 09. März 2019 um 21:59 Uhr > Von: "Matthias Fischer" > An: "Bernhard Bitsch" , "IPFire Development" > Betreff: Re: Aw: GUI for WLanAP doesn't reflect current settings for 'noscan' option > > Hi Bernhard, > > On 09.03.2019 21:15, Matthias Fischer wrote: > > ... > >>> Can anyone confirm? > >>> > >> 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 => noscan=1 > /var/ipfire/wlanap/settings => NOSCAN=on > > wlanap.cgi - OFF is checked: > /var/ipfire/wlanap/hostapd.conf => noscan=0 > /var/ipfire/wlanap/settings => NOSCAN=OFF > > Do you get the same results? > > Best, > Matthias > 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=off" hostapd generates a 40MHZ signal, and vice versa. The semantics are ok also: "Neighbour scan=off" --> scan --> noscan=0. Best, Bernhard > >> Best, > >> Bernhard > > > > Thanks for the feedback, but that is strange. > > > > To get it working as expected, I had to change line 423 from: > > > > $Lang::tr{'wlanap neighbor scan'}: on | off$Lang::tr{'wlanap neighbor scan warning'} > > > > To: > > > > $Lang::tr{'wlanap neighbor scan'}: on | off$Lang::tr{'wlanap neighbor scan warning'} > > > > Don't know if I'm just puzzled, but whatever I did, ON remained checked. > > > > Will take a closer look again. > > > > Best, > > Matthias > > > >