Enhnance WiFi options in gateway config #276

New Issue

SebaBe · 2023-01-05T11:17:09+01:00

SebaBe commented

2023-01-05 11:17:09 +01:00

The aim is to set advanced WiFi settings in a common, simplified manner without loosing the settings after an upgrade.

If not set, the current defaults should be used.

Add WiFi channel width, e.g.:

        option chan2ghz '1'
        option width2ghz '[20,40]'
        option chan5ghz '36'
        option width5ghz '[20,40,80,160]'

Posible addition, channel alignment could be added, e.g.:

        option width5ghz '[...,80xxxx,80ceee,80ecee,80eece,80eeec,...]'

If not set, "80xxxx" would be a suitable default.

Add the used WiFi protocol.
WiFi nomenclature would be quiet an easy solution, e.g.:

        option chan2ghz '1'
        option proto2ghz '[1,2,3,4]'
        option chan5ghz '36'
        option proto5ghz '[1,2,3,4,5,6]'

The aim is to set advanced WiFi settings in a common, simplified manner without loosing the settings after an upgrade. If not set, the current defaults should be used. 1) Add WiFi channel width, e.g.: ``` option chan2ghz '1' option width2ghz '[20,40]' option chan5ghz '36' option width5ghz '[20,40,80,160]' ``` 2) Posible addition, channel alignment could be added, e.g.: ``` option width5ghz '[...,80xxxx,80ceee,80ecee,80eece,80eeec,...]' ``` If not set, "80xxxx" would be a suitable default. 3) Add the used WiFi protocol. WiFi nomenclature would be quiet an easy solution, e.g.: ``` option chan2ghz '1' option proto2ghz '[1,2,3,4]' option chan5ghz '36' option proto5ghz '[1,2,3,4,5,6]' ```

fbl added this to the next-feature milestone 2023-01-05 11:43:45 +01:00

fbl added the

feature

layer3

labels 2023-01-05 11:46:37 +01:00

fbl self-assigned this 2023-01-05 11:46:40 +01:00

fbl commented

2023-01-05 11:46:51 +01:00

Add the used WiFi protocol. WiFi nomenclature would be quiet an easy solution.

What do you want to achive here? Under which circumstances is it desirable to limit the capabilities of a backwards compatible network interface? How would this improve the experience of a regular user of our firmware?

Implementing this with OpenWrt, hostapd and mac80211 is not trivial, as WiFi generations come with several independent new features / improvements, which would have to be disabled separately.

> Add the used WiFi protocol. WiFi nomenclature would be quiet an easy solution. What do you want to achive here? Under which circumstances is it desirable to limit the capabilities of a backwards compatible network interface? How would this improve the experience of a regular user of our firmware? Implementing this with OpenWrt, hostapd and mac80211 is not trivial, as WiFi generations come with several independent new features / improvements, which would have to be disabled separately.

SebaBe commented

2023-01-05 15:35:06 +01:00

Add the used WiFi protocol. WiFi nomenclature would be quiet an easy solution.

What do you want to achive here? Under which circumstances is it desirable to limit the capabilities of a backwards compatible network interface? How would this improve the experience of a regular user of our firmware?

Implementing this with OpenWrt, hostapd and mac80211 is not trivial, as WiFi generations come with several independent new features / improvements, which would have to be disabled separately.

To be honest, I don't have a usecase available.

Most likely you're right... I just thought about common WiFi options, so it fitted into the list.

> > Add the used WiFi protocol. WiFi nomenclature would be quiet an easy solution. > > What do you want to achive here? Under which circumstances is it desirable to limit the capabilities of a backwards compatible network interface? How would this improve the experience of a regular user of our firmware? > > Implementing this with OpenWrt, hostapd and mac80211 is not trivial, as WiFi generations come with several independent new features / improvements, which would have to be disabled separately. To be honest, I don't have a usecase available. Most likely you're right... I just thought about common WiFi options, so it fitted into the list.

👍 1

fbl referenced a pull request that will close this issue

2023-02-21 23:52:46 +01:00

fff-wireless: add layer3 option for channel bandwidth #281

fbl modified the milestone from next-feature to 202303-beta

2023-02-21 23:54:46 +01:00

fbl referenced this issue from a commit

2023-03-22 21:33:30 +01:00

fff-wireless: add layer3 option for channel bandwidth

fbl closed this issue

2023-03-22 21:33:30 +01:00

Sign in to join this conversation.