public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Shadi <shadisalman11@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: Update regulatory rules for Syria (SY).
Date: Fri, 15 Nov 2024 07:19:46 +0000	[thread overview]
Message-ID: <19377941c0f6489b91e77431378cb074@realtek.com> (raw)
In-Reply-To: <UH0YMS.VC3MBEUCWKPP2@gmail.com>

<shadisalman11@gmail.com> wrote:
> I'm a Linux user in Syria. We don't have any rules dictating which
> frequencies we use indoors. However, the regulatory rules in db.txt
> specify only 2.4GHz networks to be used. This default behavior is
> currently not allowing us to connect to most of the wireless networks
> in Syria. Which are mostly 5GHz networks.
> 
> Can you please update the regulatory rules so that the default behavior
> does not ban those networks ?
> 

I can update the regulatory rules for Syria. 

By page [1], the Short Range Devices Regulations [3] defines 2 GHz, 5 GHz and
60 GHz rules, no problem to this part. 

The Regulations for local wireless networks [2] looks like to define
Wireless Local Area Networks (RLAN/WLAN) for 5 GHz, 4.2 GHz and 6 GHz.
I suppose we can also add 6 GHz rules (the range between 5925 - 7125)
for WiFi 6E, but the table in page 6 shows weird frequency ranges.

By Google translation to English: 
 * 7171 - 7171
 * 7171 - 7371
 * 7151 - 7517
 * 7517 - 7271
 * 1123.7-1111
 * 75111 - 66111

Could you help to translate the table? 

[1] https://sytpra.gov.sy/pages/%D9%84%D9%88%D8%A7%D8%A6%D8%AD-%D8%AA%D9%86%D8%B8%D9%8A%D9%85%D9%8A%D8%A9/%D9%84%D9%88%D8%A7%D8%A6%D8%AD-%D8%A7%D9%84%D8%B7%D9%8A%D9%81-%D8%A7%D9%84%D8%AA%D8%B1%D8%AF%D8%AF%D9%8A-%D8%A7%D9%84%D8%B1%D8%A7%D8%AF%D9%8A%D9%88%D9%8A

[2] http://sytpra.gov.sy/public/uploads/files/%D8%A7%D9%84%D8%A7%D8%B7%D8%A7%D8%B1%20%D8%A7%D9%84%D9%82%D8%A7%D9%86%D9%88%D9%86%D9%8A/%D9%84%D9%88%D8%A7%D8%A6%D8%AD%20%D8%AA%D9%86%D8%B8%D9%8A%D9%85%D9%8A%D8%A9/%D9%84%D9%88%D8%A7%D8%A6%D8%AD%20%D8%A7%D9%84%D8%B7%D9%8A%D9%81%20%D8%A7%D9%84%D8%AA%D8%B1%D8%AF%D8%AF%D9%8A%20%D8%A7%D9%84%D8%B1%D8%A7%D8%AF%D9%8A%D9%88%D9%8A/5.pdf

[3] http://sytpra.gov.sy/public/uploads/files/%D8%A7%D9%84%D8%A7%D8%B7%D8%A7%D8%B1%20%D8%A7%D9%84%D9%82%D8%A7%D9%86%D9%88%D9%86%D9%8A/%D9%84%D9%88%D8%A7%D8%A6%D8%AD%20%D8%AA%D9%86%D8%B8%D9%8A%D9%85%D9%8A%D8%A9/%D9%84%D9%88%D8%A7%D8%A6%D8%AD%20%D8%A7%D9%84%D8%B7%D9%8A%D9%81%20%D8%A7%D9%84%D8%AA%D8%B1%D8%AF%D8%AF%D9%8A%20%D8%A7%D9%84%D8%B1%D8%A7%D8%AF%D9%8A%D9%88%D9%8A/L1.pdf



      reply	other threads:[~2024-11-15  7:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 13:37 Update regulatory rules for Syria (SY) Shadi
2024-11-15  7:19 ` Ping-Ke Shih [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=19377941c0f6489b91e77431378cb074@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=shadisalman11@gmail.com \
    /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