Hey Neels,
and potentially other users of osmo-dev.git reading the ML,
since I'm using osmo-dev's net scripts to test OsmoBSCNAT while
developing it, I submitted patches with significant changes that make
testing easier/possible:
* config_mine is now a diff to config_2g3g
* optionally build mobile + virtphy from osmocom-bb.git
* optionally start BSC2, virtual BTS, virtual MS
* all cmds can be overwritten in config_mine now, without modifying
run.sh (e.g. to use valgrind, CMD_BSCNAT="valgrind osmo-bsc-nat")
Patches were submitted for review here:
https://gerrit.osmocom.org/c/osmo-dev/+/27432/1
Related osmo-bsc-nat patches:
https://gerrit.osmocom.org/c/osmo-bsc-nat/+/27461
Best,
Oliver
--
- Oliver Smith <osmith(a)sysmocom.de> https://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschaeftsfuehrer / Managing Director: Harald Welte
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
March 11, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!)
In this edition, Kevin "tsaitgaist" Redon will present on
"USB-C - the connector and USB-PD (Power Delivery)".
This meeting will have the following schedule:
20:00 meet + greet
20:10 presentation as outlined above
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear fellow Osmocom developers,
as you all know, we've sadly had to skip OsmoDevCon 2020 and 2021,
trying to compensate it at least to some extent with our OsmoDevCall
every two weeks.
The COVID-19 pandemic is far from over, and we don't know what the
upcoming winter season will bring.
Nevertheless, I think it would be a good idea to start a discussion of
whether we should plan for an OsmoDevCon in 2022.
I personally would say let's plan for the usual late April 2022 time frame,
and if the pandemic situation deteriorates, we can still cancel it with
something like one month lead time.
I would also personally suggest to limit attendance to people who are fully
vaccinated, and in addition do a self-test for all participants every
morning.
In terms of venue, we might also consider to move to a venue that allows better
ventilation. Irrespective of the above we can also bring the air filters from
the sysmocom office.
So with that as an input statement, I would like to hear your opinion
on the above proposals. Who would want to attend? Any complaints against
the "vaccinated only plus daily self-tests in the morning" approach?
Regards,
Harald
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Just now I looked at the failures in ttcn3-bsc-test-latest.
https://jenkins.osmocom.org/jenkins/job/ttcn3-bsc-test-latest/
TL;DR: we should roll a release.
Two real failures happen that are actual bugs in the latest release,
and the rest of the failures are due to the lingering subscriber leak.
BSC_Tests.TC_ho_into_this_bsc
fails because osmo-bsc-latest omits the 'Codec List (BSS Supported)' in the
Handover Request Acknowledge message, which is mandatory on AoIP. This error is
fixed on osmo-bsc master. It makes no sense to me to punch a hole in the tests
for latest -- this failure shows a real failure of the current osmo-bsc
release.
BSC_Tests.TC_cm_service_during_lcs_loc_req
shows a subscriber leak, where a bsc_subscr is not cleaned up. This bsc_subscr
lingers all the way to the end of the BSC_Tests run, and all other current
failures of ttcn3-bsc-test-latest are due to that. (The only one not failing is
TC_refuse_chan_act_to_vamos(), because it is the only one not verifying that no
bsc_subscr stay behind.)
So this also shows a real error in the current osmo-bsc release.
There is nothing I would do at this point to make bsc-test-latest appear to be
passing, because the errors shown are errors.
The conclusion is that it might be time to roll another release one of these
days.
Related: important fixes I recently submitted are all merged to master, so from
my side it would be a good time.
~N
--
- Neels Hofmeyr <nhofmeyr(a)sysmocom.de> http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
February 25, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!)
In this edition, I will present about a number of "advanced" SIM card topics,
such as GlobalPlatform SCP02, OTA, ARA-M and the ISIM applet.
This meeting will have the following schedule:
20:00 meet + greet
20:10 talk on advanced SIM topics by @laforge
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
February 11, 2022 at 20:00 CET
at
https://meeting5.franken.de/b/har-xbc-bsx-wvs (URL has changed!)
In this edition, we will not have a presentation, as unfortunately nobody
has volunteered to present this time. Nevertheless, we will still have
the call in case anyone wants to chat about random stuff.
This meeting will have the following schedule:
20:00 meet + greet
20:10 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello Harald & Co.
This sounds like a positive development. If there is any resulting trouble(s) we'll deal with it if / as nec.
Let me take this opportunity to thank you and Osmocom for hosting OP25.
Best Regards
Max
Hello,
I need help to understand my problem installing a simple HelloWorld applet
on USIM card.
There is already a USIM applet (AID: a0000000871002ffXXffXX89) running
there, so perhaps that's the issue.
1. Should I remove it?
Here is my code to INSTALL (for load), LOAD, INSTALL (for install):
https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed
2. All of them returns 9000, which is OK, I'm using a simple CardReader,
but when I insert the SIM to a phone, no applet comes up.
Initially, I thought that the AID for instance is the reason. So when I do
https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed#file-appl…
... module_aid="d07002CA44900101", app_aid="d07002CA44900101"
I'm getting 6A88 (Referenced data not found). I changed it to
A0000000871002FFffFFff8900000101
A000000087 - RID for 3GPP
1002 - USIM
FFff - country code
FFff - card issuer code
89 - Telecom
00000101 - App version? Havent figured out this yet
the answer is 9000. But no app pops up on the phone once I insert SIM card
back.
3. Also I'm checking if any load file actually ends up by taking some
non-volatile space in SIM -- no difference.
4. After Install for install, there is nothing to be done, rght? Like
updating EF_DIR is not required, where USIM is the only applet.
Could you please assist? My twitter is twitter.com/novitoll
Thanks,
--
Sabr
Dear Osmocom community,
It's my pleasure to announce the next OsmoDevCall on
January 28, 2022 at 20:00 CET
at
https://meeting4.franken.de/b/har-xbc-bsx-wvs
In this edition, laforge will present a number of brief (lightning)
talks about a number of projects he's currently been thinking about or
working on, including
* efficient TDMoIP protocol
* TDMoIP community network
* hardware design of ISDN BRI interface for TDMoIP community network
* continuous testing setup for simtrace2 "cardem" firmware
* non-transparent ISA-over-USB bridge attached to qemu
The idea is to ping-pong some ideas wit others and maybe find somebody interested in helping out.
This meeting will have the following schedule:
20:00 meet + greet
20:10 various brief talks (see above)
21:00 unstructured supplementary social event [*]
Attendance is free of charge and open to anyone with an interest
in Osmocom or open source cellular technologies.
More information about OsmoDevCall, including the schedule
for further upcoming events can be found at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoDevCall
Looking forward to meeting you on Friday.
Best regards,
Harald
[*] this is how we started to call the "unstructured" part of osmocom
developer conferences in the past, basically where anyone can talk about
anything, no formal schedule or structure.
--
- Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello,
Sorry, for the late reply. (replying again in new thread as prev mails failed).
Quoted prev mails in quotes below.
>> Which is "your test sim". Can you share the make and model?
It's a sysmoUSIM-SJS1, I believe.
I'm receiving 9000 for INSTALL for load, and for consequent LOAD
commands 9000 as well. Only for the last INSTALL for install, I'm
getting 6A88 (reference data not found). I think, the issue is in
AIDs. I'm trying to figure out if I should use arbitrary bytes for AID
or construct AID (which includes RID + RIX) the same way as
existing Load Files, Applets' AID are on the SIM card?
I'm using d07002CA44 from this https://github.com/mrlnc/HelloSTK2,
I believe that should be reason for the 6A88 error code.
Could you please assist?
Here is my Install for Install Python3 code:
--
def install_install_make_selectable(self, exe_rid="d07002CA44",
module_aid="d07002CA44900101",
app_aid="d07002CA44900101"):
apdu = "".join([
"80", # CLS
"e6", # INSTR
"0c", # p1 ; for install (b3=1) ; for make selectable (b4=1)
"00", # p2
"%02x", # p3 ; Lc
])
# 11.5.2.3.2, page 170
data = "".join([
"%02x" % int(len(exe_rid)/2),
exe_rid, # V, executable Load file AID / load file AID
"%02x" % int(len(module_aid)/2),
module_aid, # V, executable Module AID / class file AID
"%02x" % int(len(app_aid)/2),
app_aid, # V, Application AID / instance AID
"0100", # L privileges ; V=00, 11.1.2 Privileges
Coding, page 146
"%02x", # L Install Parameters field
])
system_params_v = "".join([
"c802", # TL - non-volatile memory quota
"00ff", # V
"c702", # TL - volatile memory quota
"00ff",
])
install_params_tl = "".join([
"EF", # T - System Specific Parameters
"%02x"
])
install_params_v = ""
install_params_v += system_params_v
install_params_v += "".join([
# ETSI 102 226, page 23
# 8.2.1.3.2.1 Coding of the SIM File Access and Toolkit
Application Specific Parameters
"ca",
"%02x", # TL
])
toolkit_app_params = "".join([
"01", # L of access domain
##
## Access Domain
## 00 - full access
## 01 - APDU access (reserved for 2G; see 3GPP TS 31 116)
## 02 - UICC access (reserved for 3G)
## ff - no access
##
"ff", # V access domain
"01", # V priority
"00", # V max timers
"0f", # V max menu text
"02", # V max menu entries
"0000" * int("02"),
"00", # max number of channels for this application instance
"00", # length of MSL
])
install_params_v = install_params_v %
int(len(toolkit_app_params)/2) + toolkit_app_params
### C9 - Application Specific Parameters (none?)
applet_specific_params_v = "".join([
""
])
applet_specific_params_tlv = "".join([
"c9",
"%02x" % int(len(applet_specific_params_v)/2),
applet_specific_params_v
])
install_params_v += applet_specific_params_tlv
install_params = install_params_tl %
int(len(install_params_v)/2) + install_params_v
data = data % int(len(install_params)/2) + install_params
data += "00" # load token
apdu = apdu % int(len(data)/2) + data
apdu += "00c0000000" # C-MAC
return apdu
--
> On Dec 24, 2021, 2:51 AM, Sabyrzhan Tasbolatov wrote:
> Hello,
>
> I need help with installing the HelloWorld.cap applet in my test SIM.
> I know how to construct APDUs and osmocom's shadysim.py,
> does not work properly for me. So I've written the script myself.
>
> https://gist.github.com/Novitoll/2d8146b85f4384eb4dd039eb8116d1ed
>
> GP "Card Specification – Public Release v2.3.1".
>
> 1. Install for LOAD, Data = 00, SW = 9000
> 2. LOAD 0, SW = 9000
> 3. LOAD 1, SW = 9000
> 4. LOAD 2, SW = 9000
> 5. LOAD 3, SW = 9000, final
> 6. Install for install and make selectable, SW = 6988 (Reference data not found)
>
> Trying to figure out where the issue is.
> I've tried to re-use `install_app` function from shadysim.py - same result.
>
> I'm using this https://github.com/mrlnc/HelloSTK2/blob/main/HelloSTK2.cap
>
> Could anyone assist?
--
>> On Tue, Jan 4, 6:30 PM, Harald Welte wrote:
>> Hi Sabr,
>> On Mon, Jan 03, 2022 at 03:51:54PM +0600, Sabyrzhan Tasbolatov wrote:
>>> Following up
>>
>>I didn't see your original mail, sorry.
>>
>>> > I need help with installing the HelloWorld.cap applet in my test SIM.
>>
>>Which is "your test sim". Can you share the make and model?
>>
>>> > I know how to construct APDUs and osmocom's shadysim.py
>>> > <https://git.osmocom.org/sim/sim-tools/tree/shadysim/shadysim.py>,
>>> > does not work properly for me.
>>
>>please note that different cards have different expectations (and bugs) on the exact
>>parameters to load applets. Also, shadysim is a "early proof of concept"
>>and not something that intended to be a full implementation and/or
>>support a wide variety of cards with related workarounds, etc.
