March 2026 - gerrit-log - lists.osmocom.org

[M] Change in ...osmo-s1gw[master]: pfcp_peer: implement periodic PFCP heartbeat
by laforge 27 Mar '26

27 Mar '26

laforge has submitted this change. ( https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/42487?usp=email ) Change subject: pfcp_peer: implement periodic PFCP heartbeat ...................................................................... pfcp_peer: implement periodic PFCP heartbeat Add a heartbeat_interval parameter to the pfcp_peer config section. When non-zero, pfcp_peer sends a periodic Heartbeat Request to the UPF at the configured interval using a named gen_statem timeout (hb_timer). The timer is started on entry to the connected state and cancelled on re-entry to the connecting state. Default is 10000 ms (10 seconds). Change-Id: I306324f8eca325202a3fa23125854db9d5eaab38 --- M config/sys.config M contrib/openapi.yaml M doc/manuals/chapters/configuration.adoc M doc/manuals/chapters/rest.adoc M include/osmo_s1gw.hrl M priv/openapi.json M src/osmo_s1gw_sup.erl M src/pfcp_peer.erl M src/rest_server.erl 9 files changed, 46 insertions(+), 9 deletions(-) Approvals: pespin: Looks good to me, but someone else must approve Jenkins Builder: Verified laforge: Looks good to me, approved diff --git a/config/sys.config b/config/sys.config index 5bebbe6..a34837d 100644 --- a/config/sys.config +++ b/config/sys.config @@ -35,7 +35,9 @@ %% optional: PFCP Association Setup timeout in milliseconds (default: 2000) %% assoc_setup_timeout => 2000, %% optional: PFCP Heartbeat Request timeout in milliseconds (default: 2000) - %% heartbeat_req_timeout => 2000 + %% heartbeat_req_timeout => 2000, + %% optional: periodic PFCP heartbeat interval in milliseconds (default: 10000) + %% heartbeat_interval => 10000 }} %% Optional PFCP Network Instance IEs (omitted if not configured) %% {pfcp_net_inst_core, "core-side"}, %% PFCP Network Instance IE value (to core) diff --git a/contrib/openapi.yaml b/contrib/openapi.yaml index 8ca18aa..f6dae12 100644 --- a/contrib/openapi.yaml +++ b/contrib/openapi.yaml @@ -535,6 +535,9 @@ heartbeat_req_timeout: type: integer description: PFCP Heartbeat Request response timeout in milliseconds + heartbeat_interval: + type: integer + description: Periodic PFCP heartbeat interval in milliseconds GtpuKpiCfg: type: object diff --git a/doc/manuals/chapters/configuration.adoc b/doc/manuals/chapters/configuration.adoc index a361730..62dbc87 100644 --- a/doc/manuals/chapters/configuration.adoc +++ b/doc/manuals/chapters/configuration.adoc @@ -138,7 +138,8 @@ laddr => "127.0.1.1", %% local address for PFCP (UDP) raddr => "127.0.1.2" %% remote address of the UPF %% assoc_setup_timeout => 2000, %% optional, milliseconds - %% heartbeat_req_timeout => 2000 %% optional, milliseconds + %% heartbeat_req_timeout => 2000, %% optional, milliseconds + %% heartbeat_interval => 0 %% optional, milliseconds (0 = disabled) }}, %% Optional Network Instance IEs: @@ -161,6 +162,11 @@ How long (in milliseconds) to wait for a PFCP Heartbeat Response before declaring the heartbeat timed out. Default: `2000`. +`heartbeat_interval`:: + Interval (in milliseconds) between periodic PFCP Heartbeat Requests sent + by OsmoS1GW while associated with the UPF. Set to `0` to disable periodic + heartbeats entirely. Default: `10000`. + NOTE: The legacy flat keys `pfcp_loc_addr` and `pfcp_rem_addr` are still accepted for backwards compatibility. The `pfcp_peer` map takes priority if both are present. diff --git a/doc/manuals/chapters/rest.adoc b/doc/manuals/chapters/rest.adoc index c3f53af..2f3dd92 100644 --- a/doc/manuals/chapters/rest.adoc +++ b/doc/manuals/chapters/rest.adoc @@ -80,7 +80,8 @@ "laddr": "127.0.1.1", "raddr": "127.0.1.2", "assoc_setup_timeout": 2000, - "heartbeat_req_timeout": 2000 + "heartbeat_req_timeout": 2000, + "heartbeat_interval": 10000 }, "gtpu_kpi": { "enable": false, @@ -111,6 +112,7 @@ `raddr`::: Remote UPF (PFCP peer) address. `assoc_setup_timeout`::: PFCP Association Setup response timeout in milliseconds. `heartbeat_req_timeout`::: PFCP Heartbeat Request response timeout in milliseconds. + `heartbeat_interval`::: Periodic PFCP heartbeat interval in milliseconds (0 = disabled). `gtpu_kpi`:: `enable`::: Whether GTP-U KPI reporting via nftables counters is active. diff --git a/include/osmo_s1gw.hrl b/include/osmo_s1gw.hrl index 692a6ff..87da075 100644 --- a/include/osmo_s1gw.hrl +++ b/include/osmo_s1gw.hrl @@ -43,6 +43,7 @@ -define(ENV_DEFAULT_PFCP_REM_ADDR, "127.0.1.2"). -define(ENV_DEFAULT_PFCP_ASSOC_SETUP_TIMEOUT, 2000). -define(ENV_DEFAULT_PFCP_HEARTBEAT_REQ_TIMEOUT, 2000). +-define(ENV_DEFAULT_PFCP_HEARTBEAT_INTERVAL, 10000). %% 10 seconds -define(ENV_DEFAULT_GTPU_KPI_ENABLE, false). -define(ENV_DEFAULT_GTPU_KPI_TABLE_NAME, "osmo-s1gw"). -define(ENV_DEFAULT_GTPU_KPI_INTERVAL, 3000). diff --git a/priv/openapi.json b/priv/openapi.json index 3153505..3bc27f9 100644 --- a/priv/openapi.json +++ b/priv/openapi.json @@ -771,6 +771,10 @@ "heartbeat_req_timeout": { "type": "integer", "description": "PFCP Heartbeat Request response timeout in milliseconds" + }, + "heartbeat_interval": { + "type": "integer", + "description": "Periodic PFCP heartbeat interval in milliseconds" } } }, diff --git a/src/osmo_s1gw_sup.erl b/src/osmo_s1gw_sup.erl index 9809fff..832d30f 100644 --- a/src/osmo_s1gw_sup.erl +++ b/src/osmo_s1gw_sup.erl @@ -163,7 +163,9 @@ assoc_setup_timeout => maps:get(assoc_setup_timeout, Cfg, ?ENV_DEFAULT_PFCP_ASSOC_SETUP_TIMEOUT), heartbeat_req_timeout => maps:get(heartbeat_req_timeout, Cfg, - ?ENV_DEFAULT_PFCP_HEARTBEAT_REQ_TIMEOUT)}. + ?ENV_DEFAULT_PFCP_HEARTBEAT_REQ_TIMEOUT), + heartbeat_interval => maps:get(heartbeat_interval, Cfg, + ?ENV_DEFAULT_PFCP_HEARTBEAT_INTERVAL)}. -spec gtpu_kpi_cfg() -> gtpu_kpi:cfg(). diff --git a/src/pfcp_peer.erl b/src/pfcp_peer.erl index 30b45bd..9dd25ea 100644 --- a/src/pfcp_peer.erl +++ b/src/pfcp_peer.erl @@ -77,7 +77,8 @@ -type cfg() :: #{laddr := string() | inet:ip_address(), raddr := string() | inet:ip_address(), assoc_setup_timeout => pos_integer(), - heartbeat_req_timeout => pos_integer()}. + heartbeat_req_timeout => pos_integer(), + heartbeat_interval => non_neg_integer()}. -type peer_info() :: #{state := atom(), laddr := inet:ip_address(), @@ -214,7 +215,8 @@ %% Tx PFCP Association Setup {ok, S1} = send_assoc_setup(S0), TVal = maps:get(assoc_setup_timeout, Cfg, ?ENV_DEFAULT_PFCP_ASSOC_SETUP_TIMEOUT), - {keep_state, S1, [{state_timeout, TVal, assoc_setup_timeout}]}; + {keep_state, S1, [{{timeout, hb_timer}, cancel}, + {state_timeout, TVal, assoc_setup_timeout}]}; %% Handle Association Setup timeout connecting(state_timeout, assoc_setup_timeout, S) -> @@ -269,10 +271,23 @@ %% CONNECTED state -connected(enter, OldState, S) -> +connected(enter, OldState, + #peer_state{cfg = Cfg} = S) -> ?LOG_INFO("State change: ~p -> ~p", [OldState, ?FUNCTION_NAME]), s1gw_metrics:gauge_set(?S1GW_GAUGE_PFCP_ASSOCIATED, 1), - {keep_state, S}; + case maps:get(heartbeat_interval, Cfg, ?ENV_DEFAULT_PFCP_HEARTBEAT_INTERVAL) of + 0 -> {keep_state, S}; %% periodic heartbeat is disabled + Interval -> + ?LOG_INFO("Starting periodic PFCP heartbeat (interval=~p ms)", [Interval]), + {keep_state, S, [{{timeout, hb_timer}, Interval, heartbeat}]} + end; + +%% Periodic heartbeat timer +connected({timeout, hb_timer}, heartbeat, + #peer_state{cfg = Cfg} = S0) -> + {_, S1} = send_heartbeat_request(undefined, S0), + Interval = maps:get(heartbeat_interval, Cfg, ?ENV_DEFAULT_PFCP_HEARTBEAT_INTERVAL), + {keep_state, S1, [{{timeout, hb_timer}, Interval, heartbeat}]}; connected({call, From}, {session_establish_req, SEID, PDRs, FARs}, diff --git a/src/rest_server.erl b/src/rest_server.erl index 7960ffa..bff37fc 100644 --- a/src/rest_server.erl +++ b/src/rest_server.erl @@ -285,7 +285,9 @@ <<"assoc_setup_timeout">> => maps:get(assoc_setup_timeout, Cfg, ?ENV_DEFAULT_PFCP_ASSOC_SETUP_TIMEOUT), <<"heartbeat_req_timeout">> => maps:get(heartbeat_req_timeout, Cfg, - ?ENV_DEFAULT_PFCP_HEARTBEAT_REQ_TIMEOUT)}. + ?ENV_DEFAULT_PFCP_HEARTBEAT_REQ_TIMEOUT), + <<"heartbeat_interval">> => maps:get(heartbeat_interval, Cfg, + ?ENV_DEFAULT_PFCP_HEARTBEAT_INTERVAL)}. -spec config_gtpu_kpi() -> map(). -- To view, visit https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/42487?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: erlang/osmo-s1gw Gerrit-Branch: master Gerrit-Change-Id: I306324f8eca325202a3fa23125854db9d5eaab38 Gerrit-Change-Number: 42487 Gerrit-PatchSet: 3 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>

1 0

[M] Change in ...osmo-s1gw[master]: pfcp_peer: implement periodic PFCP heartbeat
by laforge 27 Mar '26

27 Mar '26

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/42487?usp=email ) Change subject: pfcp_peer: implement periodic PFCP heartbeat ...................................................................... Patch Set 2: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/42487?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: erlang/osmo-s1gw Gerrit-Branch: master Gerrit-Change-Id: I306324f8eca325202a3fa23125854db9d5eaab38 Gerrit-Change-Number: 42487 Gerrit-PatchSet: 2 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Fri, 27 Mar 2026 00:45:04 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

[L] Change in osmo-ttcn3-hacks[master]: pgw: Test v6 and v4v6 PDU session userplane
by laforge 27 Mar '26

27 Mar '26

Attention is currently required from: pespin. laforge has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/42501?usp=email ) Change subject: pgw: Test v6 and v4v6 PDU session userplane ...................................................................... Patch Set 2: (1 comment) File pgw/testenv.sh: https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/42501/comment/75f3f960_0bc2… : PS2, Line 51: s if the IPv4 route is already added above, why do we add it here again? If v4 route is already present, I would have expected only to add a v6 address here? -- To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/42501?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-ttcn3-hacks Gerrit-Branch: master Gerrit-Change-Id: Idf009b9118db8117c547a1bb0f27afdfa3f03924 Gerrit-Change-Number: 42501 Gerrit-PatchSet: 2 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-CC: laforge <laforge(a)osmocom.org> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Fri, 27 Mar 2026 00:44:23 +0000 Gerrit-HasComments: Yes Gerrit-Has-Labels: No

1 0

[XS] Change in osmo-uecups[master]: gtp_tunnel: Log Tx of ICMPv6 Router Solicitation
by laforge 26 Mar '26

26 Mar '26

laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-uecups/+/42500?usp=email ) Change subject: gtp_tunnel: Log Tx of ICMPv6 Router Solicitation ...................................................................... gtp_tunnel: Log Tx of ICMPv6 Router Solicitation Change-Id: I5883a0e399e47b6e169c5adf8446e9d2aeecbe68 --- M daemon/gtp_tunnel.c 1 file changed, 4 insertions(+), 0 deletions(-) Approvals: osmith: Looks good to me, but someone else must approve laforge: Looks good to me, approved Jenkins Builder: Verified diff --git a/daemon/gtp_tunnel.c b/daemon/gtp_tunnel.c index fc99e4f..c115cd4 100644 --- a/daemon/gtp_tunnel.c +++ b/daemon/gtp_tunnel.c @@ -215,8 +215,12 @@ static int _gtp_tunnel_tx_icmpv6_rs(struct gtp_tunnel *t) { struct msgb *msg; + char ipbuf[INET6_ADDRSTRLEN]; int rc; + LOGT(t, LOGL_INFO, "Tx ICMPv6 Router Solicitation for %s\n", + osmo_sockaddr_ntop(&t->user_addr_ipv6_ll.u.sa, ipbuf)); + OSMO_ASSERT(t->user_addr_type == GTP1U_EUA_TYPE_IPv6 || t->user_addr_type == GTP1U_EUA_TYPE_IPv4v6); -- To view, visit https://gerrit.osmocom.org/c/osmo-uecups/+/42500?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: merged Gerrit-Project: osmo-uecups Gerrit-Branch: master Gerrit-Change-Id: I5883a0e399e47b6e169c5adf8446e9d2aeecbe68 Gerrit-Change-Number: 42500 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>

1 0

[XS] Change in osmo-uecups[master]: gtp_tunnel: Log Tx of ICMPv6 Router Solicitation
by laforge 26 Mar '26

26 Mar '26

Attention is currently required from: pespin. laforge has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-uecups/+/42500?usp=email ) Change subject: gtp_tunnel: Log Tx of ICMPv6 Router Solicitation ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/osmo-uecups/+/42500?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-uecups Gerrit-Branch: master Gerrit-Change-Id: I5883a0e399e47b6e169c5adf8446e9d2aeecbe68 Gerrit-Change-Number: 42500 Gerrit-PatchSet: 1 Gerrit-Owner: pespin <pespin(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: osmith <osmith(a)sysmocom.de> Gerrit-Attention: pespin <pespin(a)sysmocom.de> Gerrit-Comment-Date: Thu, 26 Mar 2026 21:58:28 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

[XS] Change in osmo-ci[master]: OBS: add Ubuntu 26.04
by laforge 26 Mar '26

26 Mar '26

Attention is currently required from: osmith. laforge has posted comments on this change by osmith. ( https://gerrit.osmocom.org/c/osmo-ci/+/42503?usp=email ) Change subject: OBS: add Ubuntu 26.04 ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/osmo-ci/+/42503?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-ci Gerrit-Branch: master Gerrit-Change-Id: Id22f4902b73ad9b4131b837a8036df68cf665f8f Gerrit-Change-Number: 42503 Gerrit-PatchSet: 1 Gerrit-Owner: osmith <osmith(a)sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-Reviewer: pespin <pespin(a)sysmocom.de> Gerrit-Attention: osmith <osmith(a)sysmocom.de> Gerrit-Comment-Date: Thu, 26 Mar 2026 21:58:15 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

[XS] Change in osmo-bts[master]: measurement: is_meas_complete(): fix fn_mod variable type
by laforge 26 Mar '26

26 Mar '26

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmo-bts/+/42515?usp=email ) Change subject: measurement: is_meas_complete(): fix fn_mod variable type ...................................................................... Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42515?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: I6b0bce9bc9fca1d6effbb2da2319132cdff4e9c7 Gerrit-Change-Number: 42515 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-CC: Jenkins Builder Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 26 Mar 2026 21:57:22 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

[XS] Change in osmo-bts[master]: bts_ctrl_commands: remove debugging leftover
by laforge 26 Mar '26

26 Mar '26

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmo-bts/+/42514?usp=email ) Change subject: bts_ctrl_commands: remove debugging leftover ...................................................................... Patch Set 1: Code-Review+2 -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42514?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: I571a10f94482e3097aa915f192db6215f085dbcd Gerrit-Change-Number: 42514 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-CC: Jenkins Builder Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 26 Mar 2026 21:57:09 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

[XS] Change in osmo-bts[master]: l1sap: check_for_ciph_cmd(): add missing msgb length check
by laforge 26 Mar '26

26 Mar '26

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmo-bts/+/42513?usp=email ) Change subject: l1sap: check_for_ciph_cmd(): add missing msgb length check ...................................................................... Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42513?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: I47690f1a6357e42913bfa8100e36c05cb4f0607a Gerrit-Change-Number: 42513 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-CC: Jenkins Builder Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 26 Mar 2026 21:56:59 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

[S] Change in osmo-bts[master]: osmo-bts-trx: clean up log messages in response handlers
by laforge 26 Mar '26

26 Mar '26

Attention is currently required from: fixeria. laforge has posted comments on this change by fixeria. ( https://gerrit.osmocom.org/c/osmo-bts/+/42512?usp=email ) Change subject: osmo-bts-trx: clean up log messages in response handlers ...................................................................... Patch Set 1: Code-Review+1 -- To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/42512?usp=email To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email Gerrit-MessageType: comment Gerrit-Project: osmo-bts Gerrit-Branch: master Gerrit-Change-Id: Iec722198f161621dd00ce3baabb732e1a1d91a37 Gerrit-Change-Number: 42512 Gerrit-PatchSet: 1 Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Reviewer: laforge <laforge(a)osmocom.org> Gerrit-CC: Jenkins Builder Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de> Gerrit-Comment-Date: Thu, 26 Mar 2026 21:56:39 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: Yes

1 0

2026

2025

2024

2023

2022

gerrit-log March 2026