From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: 802.11ac - specific config requirements for hostapd
Date: Fri, 28 Dec 2018 22:54:39 +0000 [thread overview]
Message-ID: <993FC711-423C-4972-9D4E-996F0FBC9584@ipfire.org> (raw)
In-Reply-To: <8FF0C2E7-B7FE-4601-BE99-897092E75FB5@gmx.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
> On 28 Dec 2018, at 22:49, Horace Michael <horace.michael(a)gmx.com> wrote:
>
>
>
>
> Hi
> <michael.tremer(a)ipfire.org> wrote:
>> Hi,
>>
>>> On 28 Dec 2018, at 22:41, Horace Michael <horace.michael(a)gmx.com>
>> wrote:
>>>
>>> Hello,
>>>
>>> Please consider to add to WUI (cgi-bin/wlanap.cgi) a field where
>> specific 802.11ac settings can be added.
>>> Ex:
>>> vht_oper_chwidth=1
>>> vht_oper_centr_freq_seg0_idx=42
>>>
>>
>> It is absolutely impossible to hardcode a specific channel.
>>
>
> vht_oper_centr_freq_seg0_idx was a bad example - it is computed based on the channel...
>
> Other than that the list of settings required by 802.11ac is quite long and currently there is no place to add them in WUI.
*What* other settings? 802.11ac runs fine as it is. You need to be clearer on what you want to achieve here.
-Michael
>>> Others specific settings might be needed - as listed in the hostapd
>> configuration file https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf
>>
>>>
>>> Currently these settings added to /etc/hostapd.conf don't survire
>> when WUI is used - settings need to be added back afer WUI is used and
>> hostapd restarted.
>>>
>>> Thank you for considering this improvement,
>>> Horace
>>
>> -Michael
>
> --
> Horace Michael (aka H&M)
> Please excuse my typos and brevity. Sent from a Smartphone.
next prev parent reply other threads:[~2018-12-28 22:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-28 22:44 Michael Tremer
2018-12-28 22:49 ` Horace Michael
2018-12-28 22:54 ` Michael Tremer [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-28 22:45 Tom Rymes
2018-12-28 22:41 Horace Michael
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=993FC711-423C-4972-9D4E-996F0FBC9584@ipfire.org \
--to=michael.tremer@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