Attention is currently required from: pespin.
laforge has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37915?usp=email )
Change subject: s1gw: Validate S1SetupResp is forwarded fine MME->ENB
......................................................................
Patch Set 1: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37915?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: I6d9b060eb81269c7cb76e007f669c5b9ead97158
Gerrit-Change-Number: 37915
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 26 Aug 2024 08:05:49 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: Yes
Attention is currently required from: dexter, fixeria.
laforge has posted comments on this change by dexter. ( https://gerrit.osmocom.org/c/pysim/+/37840?usp=email )
Change subject: ara_m: use class byte of current lchan
......................................................................
Patch Set 7: Code-Review-1
(1 comment)
Patchset:
PS6:
> This is interesting. I have looked up MANAGE CHANNEL in ETSI TS 102.221. […]
Ok, I was mistaken (was recalling this from memory). MANAGE CHANNEL is not affected. However, TS 102 221 Table 10.5 states several other instructions that must have CLA=80 and hence do not support logical channels: TERMINAL PROFILE, TERMINAL RESPONSE, FETCH, ENVELOPE and SUSPEND UICC. Rel 17 now also has EXCHANGE CAPABILITIES and MANAGE LSI, but we don't support those yet. Other specs may at least in theory also have similar constraaints in the table defining their CLA bytes.
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/37840?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: Ie3e48678f178a488bfaea6cc2b9a3e18145a8d10
Gerrit-Change-Number: 37840
Gerrit-PatchSet: 7
Gerrit-Owner: dexter <pmaier(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: dexter <pmaier(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 26 Aug 2024 07:20:10 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: Yes
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: dexter <pmaier(a)sysmocom.de>
Attention is currently required from: laforge.
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/pysim/+/37926?usp=email
to look at the new patch set (#2).
The following approvals got outdated and were removed:
Verified-1 by Jenkins Builder
Change subject: contrib: script to generate "update" commands from diff of fsdumps
......................................................................
contrib: script to generate "update" commands from diff of fsdumps
Change-Id: I08897cd353093575f98c68580afbc68b6f2f878f
---
A contrib/fsdump-diff-apply.py
1 file changed, 169 insertions(+), 0 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/pysim refs/changes/26/37926/2
--
To view, visit https://gerrit.osmocom.org/c/pysim/+/37926?usp=email
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: newpatchset
Gerrit-Project: pysim
Gerrit-Branch: master
Gerrit-Change-Id: I08897cd353093575f98c68580afbc68b6f2f878f
Gerrit-Change-Number: 37926
Gerrit-PatchSet: 2
Gerrit-Owner: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Attention is currently required from: pespin.
fixeria has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920?usp=email )
Change subject: s1gw: Add initial PFCP support emulating UPF
......................................................................
Patch Set 2:
(3 comments)
File s1gw/ConnHdlr.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920/comment/d90492f3_1e30… :
PS2, Line 185: float Tval := 5.0
> Because sometimes the timeouts were too tight, specially when creating tons of sessions where then a […]
I see, but this function is all about the S1AP Setup. This particular message does not trigger any PFCP procedures; the PDUs are passed as-is. This is why I am wondering why and whether it really belongs to this patch logically.
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920/comment/c559db86_1ce8… :
PS2, Line 269: do_repeat := true
> only once, but since it's an activate, it has to be a repeat otherwise when code goes into whatever […]
Ah, I see. Indeed, we need to `repeat` then.
File s1gw/S1GW_Tests.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920/comment/4d10e572_b9f1… :
PS2, Line 81: id) alive
> TBH I don't think it's worth spending time in splitting this ...
On the one hand, yes. One the other, I oftentimes feel puzzled when I track some change in git-blame and end up with a patch doing something else and changing things by the way. In such case neither the commit name nor the description tells you *why*.
> id: I'm simply refactoring code since anyway i need to add a lot of infra when adding the pfcp side.
This is just moving `testcasename()` from within the function to the caller.
Does the PFCP related logic require to pass custom `id` here? I don't think so.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920?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: If2b135e113d2568092e90ac9b6c5f651ab30f5d0
Gerrit-Change-Number: 37920
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 26 Aug 2024 04:46:46 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: pespin.
fixeria has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37923?usp=email )
Change subject: erab_fsm: Abort and reply call with error if unable to establish PFCP sess
......................................................................
Patch Set 1:
(2 comments)
File src/erab_fsm.erl:
https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37923/comment/b294973f_390a… :
PS1, Line 176: next_state, ?FUNCTION_NAME, S, %% loop transition to enable state_timeout
> Yes, that sounded weird to me at the time when you said so. […]
Ok, I see you have also changed the loop transition to `keep_state` in the `pfcp_peer` (Ic17c1c7210ab4ae0ddc840a5ffd13b7cdda243c9). I gave it a try and indeed it's working as expected: the peer re-tries association.
This is weird, because I spent quite some time debugging and figuring out why state timeout does not work, e.g. here: https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37265. Maybe it was a bug of older Erlang/OTP version, or this problem occurs only under some conditions.
I would keep it as-is for now, until we know more about this problem. Strictly speaking, changing from `next_state` to `keep_state` is not needed to get things done in this patch. You're just doing this by the way since you're touching the related code path, but this is clearly not a must in this case.
https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37923/comment/763ea469_5e49… :
PS1, Line 179: {stop_and_reply,
(cosmetic) Also, please move the case body to the next line for consistency with the existing code (like done above).
```
{error, Reason} ->
{stop_and_reply, ...
```
--
To view, visit https://gerrit.osmocom.org/c/erlang/osmo-s1gw/+/37923?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: If23881205b995e76647289d5e6c1c85d02f93b47
Gerrit-Change-Number: 37923
Gerrit-PatchSet: 1
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 26 Aug 2024 04:21:24 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: pespin <pespin(a)sysmocom.de>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>
Attention is currently required from: fixeria.
pespin has posted comments on this change by pespin. ( https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920?usp=email )
Change subject: s1gw: Add initial PFCP support emulating UPF
......................................................................
Patch Set 2:
(3 comments)
File s1gw/ConnHdlr.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920/comment/4ed63c0f_28b1… :
PS2, Line 185: float Tval := 5.0
> This looks unrelated. […]
Because sometimes the timeouts were too tight, specially when creating tons of sessions where then also ttcn3 has to answer to them.
It is also easier to debug if some time is left between the error and the tear down, one can see in the pcap the seconds clearly.
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920/comment/c6fef19a_49d0… :
PS2, Line 269: do_repeat := true
> Do we normally expect receiving the Assoc Setup Req more than once? […]
only once, but since it's an activate, it has to be a repeat otherwise when code goes into whatever alt, if this message is received then it will skip the alt unexpectedly.
File s1gw/S1GW_Tests.ttcn:
https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920/comment/a28d2780_1654… :
PS2, Line 81: id) alive
> These changes looks unrelated to me: […]
alive: I can put it into another patch
id: I'm simply refactoring code since anyway i need to add a lot of infra when adding the pfcp side.
TBH I don't think it's worth spending time in splitting this at this time of the development of this testsuite where lots of stuff is still missing and may change / be rewritten when more features are added.
--
To view, visit https://gerrit.osmocom.org/c/osmo-ttcn3-hacks/+/37920?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: If2b135e113d2568092e90ac9b6c5f651ab30f5d0
Gerrit-Change-Number: 37920
Gerrit-PatchSet: 2
Gerrit-Owner: pespin <pespin(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Sun, 25 Aug 2024 22:43:51 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>