Hi All,
Does anyone tried enabling the A5/1 Encryption using osmo-bsc and osmo-msc?
We are using an UPBOARD with the following elements; osmo-bsc, osmo-bts-trx and osmo-trx in it; and a NUC with osmo-hlr, osmo-msc, osmo-mgcp, and osmo-stp.
Both servers are using Ubuntu 16.04 OS.
We enabled the a5/1 encryption in both osmo-bsc and osmo-msc. Then provisioned the programmable SIM to osmo-hlr with aud2g comp128v1 auth.
OsmoHLR# subscriber imsi 515941234567890 show ID: 9 IMSI: 515941234567890 MSISDN: 09271234567 2G auth: COMP128v1 KI=00112233445566778899aabbccddeeff
We are not really sure what causes the LOCUP Reject.
Can anyone help us with this issue?
Attached are the configuration used during the testing and a trace taken during the testing.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Tue, Feb 27, 2018 at 11:26:25AM +0000, Ron wrote:
Hi All,
Does anyone tried enabling the A5/1 Encryption using osmo-bsc and osmo-msc?
Hi Ron,
I have recreated your setup locally and can reproduce the error. Needless to say that this should work and shame on us for apparently not having an effective regression test for this :/ https://osmocom.org/issues/3017
I've tested A5/1 recently and it works for me, however, I usually have both 2G and 3G auth keys in the HLR database. Now that I have removed the 3G tokens from the HLR, an A5/1-COMP128v1 setup indeed fails to authenticate.
In the meantime, you can try to workaround if you also enter 3G K+OPC in the HLR database.
~N
Actually, Ron,
there is no bug here. I was quite sure of my SIM configuration, but in fact it was programmed to use COMP128v3, not v1, and hence I got a differing SRES upon Auth Response.
Double check that your SIM/USIM is configured to use COMP128v1 for 2G! For example, try to configure COMP128v3 in the HLR and see if that helps.
I've rejected issue #3017 now. It all works. (Feels good to be able to say that for a change.)
~N
Noted on this Neels.
Thank you for the confirmation.
We’ll try to check our SIM/USIM configuration first.
Best Regard,
Ron Menez ron.menez@entropysolution.commailto:ron.menez@entropysolution.com
On Feb 28, 2018, at 11:07 PM, Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@sysmocom.de> wrote:
Actually, Ron,
there is no bug here. I was quite sure of my SIM configuration, but in fact it was programmed to use COMP128v3, not v1, and hence I got a differing SRES upon Auth Response.
Double check that your SIM/USIM is configured to use COMP128v1 for 2G! For example, try to configure COMP128v3 in the HLR and see if that helps.
I've rejected issue #3017 now. It all works. (Feels good to be able to say that for a change.)
~N
-- - Neels Hofmeyr <nhofmeyr@sysmocom.demailto:nhofmeyr@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
-
Neels Hofmeyr -
Ron