luci/protocols, branch master

luci-proto-modemmanager: rework initial EPS bearer modes

2026-10-05T09:12:37Z

Follow the rework of the 'init_epsbearer' modes in the modemmanager package: - modem: Leave unchanged (stored on modem), the new default - network: Network-assigned - connection: Same as connection (was 'default') - custom: Custom The LuCI value 'none' was stored as an empty option, which since modemmanager commit 246506690f2d clears the initial EPS bearer instead of leaving it untouched as described. Store 'modem' explicitly instead. The legacy values 'none' and 'default' are shown as 'modem' and 'connection'. Link: https://github.com/openwrt/packages/issues/30299 Signed-off-by: Michael Pfeifroth

protocols: remove myself as maintainer for vpnc

2026-09-07T04:01:51Z

I have not had touched this in years, and was added as maintainer during treewide PKG_MAINTAINER additions. I do not have anything to test this against. Therefore, removing myself as maintainer. Signed-off-by: Daniel F. Dickinson

luci-proto-modemmanager: fix iptype default value

2026-08-18T10:04:11Z

The 'iptype' and 'init_iptype' ListValue options declared 'ipv4v6' as the default in LuCI, while the modemmanager package itself defaults to 'ipv4' (see net/modemmanager README.md). Since LuCI omits writing a UCI option when the selected value matches the field's declared default, selecting 'IPv4/IPv6 (both)' in the UI never actually saved 'option iptype ipv4v6' to /etc/config/network. On the next apply, modemmanager fell back to its own default ('ipv4'), silently downgrading the connection to IPv4-only and making the 'ipv4v6' option effectively unusable through LuCI. Align both defaults with the modemmanager package default ('ipv4') and drop the now-inaccurate '- defaults to IPv4' hint from the 'ipv4v6' label. The dropdown entries are also reordered so the new default ('ipv4') is listed first, matching the convention used by other ListValue fields in this file. Reported-by: moawut Ref: https://forum.openwrt.org/t/luci-proto-modemmanager-support-thread/23696/120 Signed-off-by: Michael Pfeifroth

luci-proto-ipv6: dhcpv6: add option to select the DHCPv6 client ID

2026-07-21T21:02:15Z

OpenWrt gained a per-interface "sendclientid" option which overrides the preferred DUID used for DHCPv6 requests. Expose it in the advanced settings of the DHCPv6 client protocol: - "auto" (default) uses the explicitly configured client ID, or falls back to the global default DUID and finally a DUID-LL derived from the interface MAC address - "global" always uses the global default DUID - "hardware" passes no client ID to odhcp6c, so a type 3 DUID-LL is used Unlike DHCPv4 there is no "none" mode, as odhcp6c always sends a client identifier. The explicit client ID is only evaluated in "auto" mode, hence it now depends on that setting. Assisted-by: Claude:claude-opus-4-8 Signed-off-by: Hauke Mehrtens

luci-proto-openvpn: fix auth_user_pass option, clarify label

2026-07-19T07:21:34Z

Maintainer: @systemcrash CC: @feckert Version: Main Compile tested: X86-64 Run tested: X86-64 Description: The push_opt tab incorrectly registered a server-side auth_user_pass Value option. So move it to the client-side FileUpload option on the general tab. auth_user_pass is a client-only option; the corresponding server-side directive is auth-user-pass-verify, which is already correctly defined under the scripts tab as auth_user_pass_verify. Also update the general-tab auth_user_pass label to a clearer description of the expected file format (username and password on separate lines). Signed-off-by: Erik Conijn

luci-proto-xfrm: replace ifid datatype check with range check

2026-07-07T14:35:36Z

According to the documentation, values from '1' to '4294967295' are allowed values for the 'ifid' option. The value ‘0’ is excluded, as '0' is treated as the default ID or an unassigned ID. While we’re at it, mark the option as non-optional. Signed-off-by: Florian Eckert

luci-proto-openvpn: fix shell code injection through gerateKey arg

2026-06-27T23:34:39Z

Ensure to quote the `cl_meta` argument of the `gerateKey` procedure. Signed-off-by: Jo-Philipp Wich

luci-proto-wireguard: escape slash in regex in javascript

2026-06-26T11:16:00Z

Escape slash. Enables proper parsing of javascript by gettext tools. Signed-off-by: Hannu Nyman

treewide: escape slash chars in regex strings in .js files

2026-06-25T20:14:58Z

Properly escape the slash '/' chars that are included in the regex strings in javascript files. Slash is used as a regex delimiter in javascript, so an un-escaped slash may cause parsing errors in some tools like xgettext used with .po translation manipulation. Signed-off-by: Hannu Nyman

luci-proto-openfortivpn: fix typo

2026-06-24T14:59:44Z

fix typo Signed-off-by: Andy Chiang