luci/modules/luci-mod-network/htdocs/luci-static/resources/view, branch master

luci-mod-network: fix available wifi channels

2026-07-09T09:32:07Z

rpcd iwinfo freqlist does not set a `no_ir` field. It is instead a flag so check in the flags list instead. Signed-off-by: Samuele Yang

luci-mod-network: wireless: add gcmp256, sae_ext_key, transition_disable

2026-07-08T23:28:44Z

Expose three per-BSS WPA3 tuning options in the wireless security tab: - gcmp256: advertise the GCMP-256 pairwise cipher - sae_ext_key: advertise the SAE-EXT-KEY AKM (SAE using a group-dependent hash, aka SAE-GDH) - transition_disable: signal Transition Disable (WPA3 Specification v3.5 section 13) so a client that connected once no longer downgrades GCMP-256 and SAE-EXT-KEY are mandatory for Wi-Fi 7 (EHT) but break interoperability with some clients. The wifi-scripts backend therefore defaults them on only for WPA3-Personal Compatibility Mode (sae-compat) on an EHT radio, and off everywhere else. The gcmp256/sae_ext_key checkboxes mirror that default, derived from both the encryption mode and the radio htmode, so the box shows the real default: leaving it untouched keeps the option unset (the backend decides), while toggling it writes an explicit override. As htmode is a radio property, not a wifi-iface one, it is read from the current selection of the radio's frequency widget (falling back to the saved config) instead of a same-section dependency. transition_disable is offered only for the WPA3-only modes where the signalled bitmap is non-empty. Assisted-by: Claude:claude-opus-4-8 Link: https://github.com/openwrt/luci/pull/8790 Signed-off-by: Hauke Mehrtens

luci-mod-network: wireless: add WPA3-Personal Compatibility Mode

2026-07-08T23:28:39Z

Expose the sae-compat encryption mode (WPA3-Personal Compatibility Mode) in the wireless security settings. It advertises WPA2-PSK in the base RSNE while offering SAE through RSN Override elements, so that both legacy WPA2 and modern WPA3 clients can connect to a single SSID. The mode relies on RSN overriding, which is an access-point feature, so it is offered for AP mode only. It gets the passphrase field and, like the other WPA2/WPA3 modes, the 802.11r, KRACK-countermeasure and WPS options. Assisted-by: Claude:claude-opus-4-8 Link: https://github.com/openwrt/luci/pull/8790 Signed-off-by: Hauke Mehrtens

luci-mod-network: don't show Carrier on dynamic/alias interface

2026-07-07T14:39:46Z

Carrier is always Absent on dynamic/alias interface. Don't show Carrier on dynamic/alias interface. Signed-off-by: Coia Prant

luci-mod-network: fix Switch/VLAN view CSS across LuCI themes

2026-06-28T19:40:41Z

Override theme-wide input min-widths and button resets so port labels stay inside tiles and T/U colour-coding renders on openwrt-2020 and material. Use theme CSS variables for row and border colours where available. Signed-off-by: Mirko Vogt Co-authored-by: LLM (Composer)

luci-mod-network: add link speed column to the devices tab

2026-06-26T07:18:17Z

The negotiated link speed of a network device isn't shown on the Network configuration pages, so a link stuck below its capability (e.g. a gigabit port at 100 Mbit/s) goes unnoticed. Add a "Link Speed" column to the Devices tab showing the negotiated speed, with the device's ethtool-supported speeds in a tooltip when available, and "-" when the device has no carrier or reports no speed. The columns are ordered by OSI layer: link speed (L1) before MAC (L2) and MTU (L3). The current speed comes from the device link state; the supported speeds are the distinct network.device status "link-supported" modes, fetched once in load(). Add the network.device "status" ACL grant so the view can call it. Signed-off-by: Paul Tobias

luci-mod-network: experimental Switch/VLAN config notice

2026-06-23T14:17:36Z

Add warning about this config view being new and considered experimental. Signed-off-by: Mirko Vogt

luci-mod-network: add new Switch/VLAN configuration

2026-06-23T14:17:36Z

Register a new "Switch/VLAN config" entry in the Network top-level menu and add the view at view/network/switch-vlan.js. The menu entry is only visible when the network configuration contains either a bridge device with vlan_filtering explicitly enabled or at least one bridge-vlan section (mirroring the implicit enable behaviour of the existing Bridge VLAN filtering dialog). The view itself locates the first such bridge in declaration order, detects configurations that the new view cannot represent (PVID different from the untagged VLAN, duplicate untagged memberships, etc.) and blocks access with an explanatory error in that case. The following shortcomings resulted in an alternative Switch/VLAN view: - To reach the current switch/VLAN config page, one has to click through: Network -> Interfaces -> Devices -> Configure... (the respective switch/bridge) -> Bridge VLAN filtering which - at least for dedicated switches - is not sth. I feel comfortable having to do every time I want to make a basic change. - While ~5 ports might still fit next to each other, starting with 2 figure numbers (at the latest), we end up scrolling horizontally. Finding a higher port to configure on a 24 or 48 port switch inevitably results in plenty of horizontal scrolling, while at the same time you have to memorise which row maps to which VLAN-ID, as those scroll out the moment you start scrolling. - Every port needs to be configured by its own, no way to bulk-conf them, to apply the same VLAN config onto multiple ports (e.g. applying the same tag onto a large number or all ports). - Ports and VLAN-IDs are defined by sole numbers. There's no way to annotate them, e.g. a VLAN ID as "iot" or "mgmt", or a port as e.g. "uplink" or "server-mirko". With the following changes: - Add a dedicated "Switch/VLAN config" entry within the top-level "Network" dropdown (you might remember we already had such for swconfig back then, before it got obsoleted by DSA and conf via vlan aware bridges). - Avoid horizontal scrolling by showing switch ports in multiple rows if not fitting screen width. - Allow selection of multiple ports to configure them all the same way at once. - Introduce labels for ports and VLANs; they're optional annotations and don't serve any functional purpose except hinting the user, hence stored in respective sections within /etc/config/luci. - Visualising which VLANs are assigned to which ports by colour- coding the ports when hovering over configured VLANs. Signed-off-by: Mirko Vogt Co-authored-by: Opus and/or Composer

luci-mod-status: escape hostname in DHCP lease status tables

2026-06-22T22:15:31Z

Avoid stored XSS by HTML escaping backend provided hostname since underlying services to not sanitize. Signed-off-by: Jo-Philipp Wich

luci-mod-network: fix redundant translation strings

2026-06-12T16:12:05Z

_('%s') caused redundant strings like %s to appear in i18n. _('Add') caused redundant strings like Add to appear in i18n. in addition, delete an extra space. Signed-off-by: Andy Chiang