This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20180228/9deed674/attachment.bin>