Hi,
the below commit drops the osmo-bts-abis.pdf from the Makefile!
Currently the Abis manual is thus missing completely.
Please fix... thx!
~Neels
commit 05f5adbe837f2cbfb9301cdb8c9b454ca0bfc825
Author: Alexander Couzens <lynxis(a)fe80.eu>
Date: Fri Oct 14 16:56:42 2016 +0200
OsmoBTS: add vty reference documentation
Including the required changes of the Makefile which is now simliar
as the other projects Makefile's.
Based on: OsmoBTS 0.3.0.283-f869
Change-Id: Id7362ce1c584b1926330b93770d68453e091c71c
--
- 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 Sylvian,
I was hoping that you could review the conv_gen.py and related changes
that Vadim has been working on. I don't feel familiar enough with the
code (and not morally authorized to merge such significant canges) to
your code.
The code is at https://gerrit.osmocom.org/#/c/828/5 as well as related
changes like https://gerrit.osmocom.org/#/c/829/4
Thanks!
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Presumably after this libosmocore commit, I get scores of new warnings (see
below) when compiling openbsc:
commit ed9d6da5df98538adc70aa03cb569eb9505d04b6
Author: Max <msuraev(a)sysmocom.de>
AuthorDate: Tue Oct 11 15:20:28 2016 +0200
Constify ctrl_cmd struct fields where appropriate
Some of these can be fixed by constifying the functions as well, but
talloc_free() of a const char * looks really wrong?
Please follow up on this or revert the commit... constifying is good, but
having twice the amount of warnings means twice the reading effort during
development cycles.
I would most prefer a revert now and come back as soon as no new warnings are
introduced; ymmv...
In file included from /usr/local/include/osmocom/core/talloc.h:4:0,
from ../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:22:
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c: In function ‘bsc_nat_handle_ctrlif_msg’:
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:131:16: warning: passing argument 1 of ‘_talloc_free’ discards ‘const’ qualifier from pointer target type
talloc_free(cmd->variable);
^
/usr/include/talloc.h:227:5: note: expected ‘void *’ but argument is of type ‘const char *’
int _talloc_free(void *ptr, const char *location);
^
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:143:34: warning: passing argument 2 of ‘bsc_get_pending’ discards ‘const’ qualifier from pointer target type
pending = bsc_get_pending(bsc, cmd->id);
^
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:86:29: note: expected ‘char *’ but argument is of type ‘const char *’
static struct bsc_cmd_list *bsc_get_pending(struct bsc_connection *bsc, char *id_str)
^
../../../src/osmo-bsc_nat/bsc_ussd.c: In function ‘bsc_ussd_check’:
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c: In function ‘forward_to_bsc’:
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:228:31: warning: passing argument 1 of ‘extract_bsc_nr_variable’ discards ‘const’ qualifier from pointer target type
if (!extract_bsc_nr_variable(cmd->variable, &nr, &bsc_variable)) {
^
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:198:12: note: expected ‘char *’ but argument is of type ‘const char *’
static int extract_bsc_nr_variable(char *variable, unsigned int *nr, char **bsc_variable)
^
In file included from /usr/local/include/osmocom/core/talloc.h:4:0,
from ../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:22:
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:259:16: warning: passing argument 1 of ‘_talloc_free’ discards ‘const’ qualifier from pointer target type
talloc_free(bsc_cmd->id);
^
/usr/include/talloc.h:227:5: note: expected ‘void *’ but argument is of type ‘const char *’
int _talloc_free(void *ptr, const char *location);
^
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:266:16: warning: passing argument 1 of ‘_talloc_free’ discards ‘const’ qualifier from pointer target type
talloc_free(bsc_cmd->variable);
^
/usr/include/talloc.h:227:5: note: expected ‘void *’ but argument is of type ‘const char *’
int _talloc_free(void *ptr, const char *location);
^
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c: In function ‘extract_bsc_cfg_variable’:
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:323:31: warning: passing argument 1 of ‘extract_bsc_nr_variable’ discards ‘const’ qualifier from pointer target type
if (!extract_bsc_nr_variable(cmd->variable, &nr, bsc_variable)) {
^
../../../src/osmo-bsc_nat/bsc_nat_ctrl.c:198:12: note: expected ‘char *’ but argument is of type ‘const char *’
static int extract_bsc_nr_variable(char *variable, unsigned int *nr, char **bsc_variable)
^
--
- 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
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