OpenWRT Boot Times Affected by WiFi: Difference between revisions

Line 1:

...wondering about long boot times for OpenWRT 25.x.y on a WRT32X or similar?

...wondering about long boot times for OpenWRT 25.x.y on a WRT32X or similar if a WiFi Channel is set to "Auto"?

Could it be WiFi ~~related~~? Believe it or not: YES!

Could it really be the fault of a WiFi setting causing long boot times? Believe it or not: YES!

=== /lib/firmware/regulatory.db ===

Line 33:

# channels 1-6 EIRP=40dBm(43dBm peak)

(57240 - 71000 @ 2160), (40)

</pre><code>DFS</code> ~~means~~ Dynamic Frequency Selection. The radio must check for radar before using that channel as an access point. This can delay wireless startup.

</pre><code>DFS</code> Dynamic Frequency Selection. The radio must check for radar before using that channel as an access point. This can delay wireless startup.

<code>AUTO-BW</code> ~~means~~ automatic bandwidth handling inside the regulatory code. It helps determine whether wider channels are allowed across compatible frequency ranges. It does not mean automatic channel selection.

<code>AUTO-BW</code> automatic bandwidth handling inside the regulatory code. It helps determine whether wider channels are allowed across compatible frequency ranges. It does not mean automatic channel selection.

<code>NO-OUTDOOR</code> ~~means~~ outdoor use is not allowed for that frequency range.

<code>NO-OUTDOOR</code> outdoor use is not allowed for that frequency range.

<code>NO-IR</code> ~~means~~ No Initiating Radiation. The device is not allowed to initiate transmissions on that range. In practice, this can prevent access point mode or active scanning.

<code>NO-IR</code> No Initiating Radiation. The device is not allowed to initiate transmissions on that range. In practice, this can prevent access point mode or active scanning.

<code>NO-OFDM</code> ~~means~~ Orthogonal Frequency-Division Multiplexing is not allowed. This is mostly relevant to special legacy restrictions.

<code>NO-OFDM</code> Orthogonal Frequency-Division Multiplexing is not allowed. This is mostly relevant to special legacy restrictions.

<code>wmmrule=ETSI</code> ~~applies~~ ETSI Wireless Multimedia parameters. This affects Quality of Service / contention behavior, not DFS startup delay.

<code>wmmrule=ETSI</code> ETSI Wireless Multimedia parameters. This affects Quality of Service / contention behavior, not DFS startup delay.

=== Try This (For Boot Speed Testing ONLY! Transmit Power ONLY changed to verify if OpenWRT does indeed read new config) ===

@@ Line 1: / Line 1: @@
-...wondering about long boot times for OpenWRT 25.x.y on a WRT32X or similar?
+...wondering about long boot times for OpenWRT 25.x.y on a WRT32X or similar if a WiFi Channel is set to "Auto"?
-Could it be WiFi related?  Believe it or not: YES!
+Could it really be the fault of a WiFi setting causing long boot times?  Believe it or not: YES!
 === /lib/firmware/regulatory.db ===
@@ Line 33: / Line 33: @@
 	# channels 1-6 EIRP=40dBm(43dBm peak)
 	(57240 - 71000 @ 2160), (40)
-</pre><code>DFS</code> means Dynamic Frequency Selection. The radio must check for radar before using that channel as an access point. This can delay wireless startup.
+</pre><code>DFS</code> Dynamic Frequency Selection. The radio must check for radar before using that channel as an access point. This can delay wireless startup.
-<code>AUTO-BW</code> means automatic bandwidth handling inside the regulatory code. It helps determine whether wider channels are allowed across compatible frequency ranges. It does not mean automatic channel selection.
+<code>AUTO-BW</code> automatic bandwidth handling inside the regulatory code. It helps determine whether wider channels are allowed across compatible frequency ranges. It does not mean automatic channel selection.
-<code>NO-OUTDOOR</code> means outdoor use is not allowed for that frequency range.
+<code>NO-OUTDOOR</code> outdoor use is not allowed for that frequency range.
-<code>NO-IR</code> means No Initiating Radiation. The device is not allowed to initiate transmissions on that range. In practice, this can prevent access point mode or active scanning.
+<code>NO-IR</code> No Initiating Radiation. The device is not allowed to initiate transmissions on that range. In practice, this can prevent access point mode or active scanning.
-<code>NO-OFDM</code> means Orthogonal Frequency-Division Multiplexing is not allowed. This is mostly relevant to special legacy restrictions.
+<code>NO-OFDM</code> Orthogonal Frequency-Division Multiplexing is not allowed. This is mostly relevant to special legacy restrictions.
-<code>wmmrule=ETSI</code> applies ETSI Wireless Multimedia parameters. This affects Quality of Service / contention behavior, not DFS startup delay.
+<code>wmmrule=ETSI</code> ETSI Wireless Multimedia parameters. This affects Quality of Service / contention behavior, not DFS startup delay.
 === Try This (For Boot Speed Testing ONLY!  Transmit Power ONLY changed to verify if OpenWRT does indeed read new config) ===