Bug 2362247

Summary:	Consider upstreaming setregdomain and udev script
Product:	[Fedora] Fedora	Reporter:	Adam Baxter <fedora>
Component:	wireless-regdb	Assignee:	John W. Linville <linville>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	linville, ngompa13
Target Milestone:	---	Keywords:	Upstream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-08-27 19:16:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Baxter 2025-04-25 05:11:03 UTC

I couldn't find an equivalent of Debian's wishlist, so I hope this is OK.

I raised https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104022 over at the Debian project, and it's been suggested that I ask Fedora to upstream their customisations of wireless-regdb, specifically the udev rules and setregdomain script. This would help users have the correct regulatory domain / country code set, which will become more of an issue with 6ghz networks and some 5ghz networks depending on channel and channel width. See https://community.frame.work/t/responded-amd-rz616-wifi-card-doesnt-work-with-6ghz-on-kernel-6-7/43226/5 for an example.



Reproducible: Always

Comment 1 Neal Gompa 2025-08-27 19:16:27 UTC

Per discussion with the Framework folks, I've split out the script, man page, and rules into their own project: https://gitlab.com/VelocityLimitless/Projects/iw-setregdomain

This can be used for various distributions and projects to have a central offering to package and ship.