From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH 5/5] doc: document new AP profile key: [General].Band
Date: Thu, 8 Dec 2022 15:48:12 -0800 [thread overview]
Message-ID: <20221208234812.778191-5-prestwoj@gmail.com> (raw)
In-Reply-To: <20221208234812.778191-1-prestwoj@gmail.com>
---
src/iwd.ap.rst | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/src/iwd.ap.rst b/src/iwd.ap.rst
index 7b8844e7..22d307e1 100644
--- a/src/iwd.ap.rst
+++ b/src/iwd.ap.rst
@@ -52,11 +52,23 @@ The group ``[General]`` contains general AP configuration.
:widths: 20 80
:align: left
+ * - Band
+ - Frequency band
+
+ Band the access point will operate on. This is optional and if omitted
+ the 2.4GHz band will be used. Value should be "2.4GHz" or "5GHz".
+
+ Note: Due to regulatory requirements the linux kernel does not allow or
+ strictly limits 5GHz use in AP mode while in world roaming. These
+ frequencies become available once the country is set, either via IWD's
+ main.conf option ``[General].Country`` (see ``man iwd.config``) or
+ externally (e.g. iw reg set <CC>).
+
* - Channel
- Channel number
- Optional channel number for the access point to operate on. Only the
- 2.4GHz-band channels are currently allowed.
+ Optional channel number for the access point to operate on. If omitted
+ the channel will be chosen automatically.
Network Authentication Settings
-------------------------------
--
2.34.3
prev parent reply other threads:[~2022-12-08 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 23:48 [PATCH 1/5] nl80211util: populate no-IR list parsing frequencies James Prestwood
2022-12-08 23:48 ` [PATCH 2/5] wiphy: track no-IR frequencies James Prestwood
2022-12-08 23:48 ` [PATCH 3/5] wiphy: add wiphy_get_no_ir_freqs James Prestwood
2022-12-08 23:48 ` [PATCH 4/5] ap: add support for 5GHz frequencies in AP mode James Prestwood
2022-12-08 23:48 ` James Prestwood [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=20221208234812.778191-5-prestwoj@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).