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 [thread overview]
Message-ID: <36a367d1-686a-6f2a-721d-d1fa62f06717@ipfire.org> (raw)
In-Reply-To: <trinity-22559968-f7cd-4b87-abb2-9ba4f0352c8c-1552166357318@3c-app-gmx-bs71>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
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?
>>
>> 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.
Ok, I think I mixed this up somehow before. After correcting the above line back to original I get:
wlanap.cgi - ON is checked:
/var/ipfire/wlanap/hostapd.conf => noscan=0
/var/ipfire/wlanap/settings => NOSCAN=off
wlanap.cgi - OFF is checked:
/var/ipfire/wlanap/hostapd.conf => noscan=1
/var/ipfire/wlanap/settings => NOSCAN=on
And the appropriate choice remains checked. Duh!
Correct!?
Best,
Matthias
prev parent reply other threads:[~2019-03-09 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-09 17:54 Matthias Fischer
2019-03-09 19:48 ` Aw: " Bernhard Bitsch
2019-03-09 20:15 ` Matthias Fischer
2019-03-09 20:59 ` Matthias Fischer
2019-03-09 21:19 ` Aw: " Bernhard Bitsch
2019-03-09 22:21 ` Matthias Fischer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36a367d1-686a-6f2a-721d-d1fa62f06717@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox