Second try. (I already sent this mail yesterday, but it did not appear
in the mailinglist. I do not know why. Maybe because I attached a file
(a patch))
Hi all,
This is my first post to the OpenBSC mailinglist.
I had a problem with the latest pysim version giving errors while trying
to program 2G (Fake)MagicSIM cards.
This had worked fine in the past with an older release from 2011.
I tried al lot of versions in between.
I was finally able to narrow it down to the commit that broke
compatibility with (fake)magicsim:
http://cgit.osmocom.org/pysim/commit/pySim/commands.py?id=8c1b33c439fef423c…
The comment with this comit is: "Do not return the FCI information while
selecting a file
The sysmoUSIM-SJS1 card does not support returning the FCI information.
Plus, the FCI information are not used anyway."
If I revert the change with attached patch, it works again.
But it may break sysmoUSIM-SJS1 compatibility.
I am not sure on how to test whether the programming of sysmoUSIM-SJS1
still works fine and if the SIMS themselves then will still work as
expected with OpenBSC or OpenBTS or OpenAirinterface.
If the code needs to stay in for sysmoUSIM-SJS1 then we probably need
somehing like the pseudocode below:
if carttype is fakemagicsim:
"a4000002"
elif cardtype is sysmoUSIM-SJS1:
"a4000C02"
else:
#What should be the default for the other cards?
Or is there another solution?
With best regards,
Martin Dudok van Heel
This is the patch inline (attaching it as a file, blocked my email from
going through)
mdvh_pysim_make_fakesim_work_again_patch_2016081201.diff
diff --git a/pySim/commands.py b/pySim/commands.py
index 721b3d4..b7fb77f 100644
--- a/pySim/commands.py
+++ b/pySim/commands.py
@@ -41,7 +41,7 @@ class SimCardCommands(object):
def select_file(self, dir_list):
rv = []
for i in dir_list:
- data, sw =
self._tp.send_apdu_checksw(self.cla_byte + "a4000C02" + i)
+ data, sw =
self._tp.send_apdu_checksw(self.cla_byte + "a4000002" + i)
rv.append(data)
return rv
On 12-08-16 09:50, Holger Freyther wrote:
>> On 12 Aug 2016, at 09:18, Rene Groothuis wrote:
>>
>> Hello,
> Hi!
>
>
>> I’m still having problems, sorry to report this. Below the log file
>> of different combinations:
>>
>
>> I’ve used different (same model) SIM cards. I’ve reinstated the USB
>> reader. Tried in different USB ports. No Luck.
>>
>> What am I doing wrong, can you please help?
>>
>>
> Sysmocom sold the last 16in1 magicsim in 2012? Did you buy these cards
> from us? Maybe this specific one is just broken? Maybe try an older
> version of pySIM? E.g. maybe some of the patches required for the
> sysmoUSIM-SJS1 broke magicsim support?
>
> In the future you could consider getting the sysmoUSIM-SJS1 from us,
> they are of way higher quality than the Chinese (GRcard, magicsim,
> etc.) ones. For emergencies like these it might make sense for you to
> get a support contract from sysmocom as well.
>
> good luck
>
> holger
>
>
<bump> https://gerrit.osmocom.org/1067
Would be nice to have the build script in master, and at the same time verify
that you have +2 voting powers on osmo-trx -- you're currently the only one
there. Feel free to appoint other reviewers at your discretion (tell me).
Thanks!
~Neels
--
- 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
Hi.
I've ran "make check" in osmo-bts recently ang got weird dir names in
tests/*/ like '$srcdir' - it seems like those should be evaluated
variable but it's written literally to FS. Do you guys see it as well or
it's some glitch local to my shell?
--
Max Suraev <msuraev(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
* Geschaeftsfuehrer / Managing Director: Harald Welte
Hi osmo_sock experts,
I'm currently looking at making the osmo-hnbgw interface addresses
configurable, an I came across a detail. This is not really pressing, but while
I'm at it I might as well cover all of the addresses.
So far I see in osmo-iuh's hnbgw.c the local address osmo-hnbgw uses to accept
Iuh connections from a 3G cell, and the remote addresses of IuCS and IuPS, each
passed to osmo_sock_init():
3G cell -------> 1.2.3.4
OSMO-HNBGW
IuPS-local? -------> 10.9.8.7 OSMO-SGSN
So we tell one socket to listen on local 1.2.3.4 for Iuh.
We tell another to send IuPS to 10.9.8.7.
But how would I tell the IuPS to use a given local interface 1.2.3.5 to contact
the SGSN's address? Would I bind() to a given local IP address and connect() to
the remote one? I must admit that the details are not 100% clear to me. AFAIK
it can be important to set a local IP address and port to send from. So if
there's something I don't understand yet I would appreciate a hint.
Anyway, in osmo_sock_init, I see:
if ((flags & (OSMO_SOCK_F_BIND | OSMO_SOCK_F_CONNECT)) ==
(OSMO_SOCK_F_BIND | OSMO_SOCK_F_CONNECT)) {
fprintf(stderr, "invalid: both bind and connect flags set:"
" %s:%u\n", host, port);
return -EINVAL;
}
Should we have another osmo_sock_init that can set up a socket like this code I
found somewhere at sysmocom to define both ends of a connection?
fd = socket(AF_INET, SOCK_DGRAM, 0);
if (fd < 0) {
printf("socket() failed: %s\n", strerror(errno));
return -1;
}
memset(&bindaddr, 0, sizeof(bindaddr));
bindaddr.sin_family = AF_INET;
bindaddr.sin_port = htons(lport);
rc = inet_pton(AF_INET, baddr, &(bindaddr.sin_addr));
if (rc != 1) {
printf("inet_pton() failed with %i: %s\n", rc, strerror(errno));
return -1;
}
rc = bind(fd, (struct sockaddr *)&bindaddr, sizeof(bindaddr));
if (rc < 0) {
printf("bind() failed: %s\n", strerror(errno));
return -1;
}
memset(&destaddr, 0, sizeof(destaddr));
destaddr.sin_family = AF_INET;
destaddr.sin_port = htons(dport);
rc = inet_pton(AF_INET, dest, &(destaddr.sin_addr));
if (rc != 1) {
printf("inet_pton() failed with %i: %s\n", rc, strerror(errno));
return -1;
}
rc = connect(fd, (const struct sockaddr *)&destaddr, sizeof(destaddr));
if (rc < 0) {
printf("connect() failed: %s\n", strerror(errno));
return -1;
}
rc = send(fd, buf, len, 0);
if (rc != len) {
printf("send() failed\n");
return -1;
}
Thanks,
~Neels
--
- 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
The following git repositories have now moved to gerrit, please submit
future patches for these at gerrit.osmocom.org, no longer via mailing
lists:
osmo-gsm-manuals
asn1c
libasn1c
osmo-trx
openpcd
osmo-sim-auth
libtelnet
mncc-python
osmocom-lcs
Thanks,
~Neels
--
- 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
Hi Max,
> Unfortunately I could not find any tests for the code in
> question so the only way to test it is by:
I uploaded tests recently. You can find them here:
https://gerrit.osmocom.org/#/c/933/4/tests/coding/coding_test.c
> I think the puncturing code should be part of the library (otherwise
> every user will have to reimplement the same thing again and again).
I am agree with you. We recently discussed this question with Tom Tsou.
He said, that there was some performance related reasons to perform
puncturing inside both gsm0503_pdtch_encode() / gsm0503_pdtch_decode().
With best regards,
Vadim Yanitskiy.
Hi all,
opinions please: I would move patch submission for the following osmocom
repositories to gerrit:
osmo-gsm-manuals
asn1c
libasn1c
osmo-python-tests
osmo-trx (TT already agreed)
Let me know if any other come to mind. Possibly *all* projects seen at
git.osmocom.org?
Thanks,
~Neels
--
- 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
Hi!
I've asked about it before but this seems to have been lost in
communication.
The question is basically how to enable multi-TRX support for
osmo-bts-trx using phy/instance infrastructure similar to other bts?
What I've tried so far is documented in
http://projects.osmocom.org/issues/1648 but it did not result in working
setup yet.
In short, I'd like to configure OpenBSC with 1 BTS with 2 TRX, each with
its own arfcn and set of channels. I'm running "osmo-bts-trx -t 2" and
correspondingly "osmo-trx -c 2" on usrp b210. Any ideas on what's
missing to make this actually work are greatly appreciated.
--
Max Suraev <msuraev(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
* Geschaeftsfuehrer / Managing Director: Harald Welte