Hello Sylvain,
On Mon, 17 Oct 2011 16:11:25 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote:
>
> Actually to get it to start I have to:
> - After powering it, wait for like 10 min. (If I try to start openbsc
> any sooner, it will never bootstrap)
If I remember, I never had to wait longer than half a minute after
power on. But this was with the version from August, so some changes
in the code might cause this behaviour.
> But I could add this 'reset' process as an nokia specific option to
> the vty (i.e. reset_on_start or something ).
A configuration option is fine, I would set the default to "always
reset" and only if someone know what he does, he can turn the reset
off (I think I had strange effects while changing the configuration
and not doing a reset, so this situation should be avoided).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi,
we own a frequency usage licence from the Bundesnetzagentur and ran our
network with auth policy token. So every new phone trying to attach to our
network will receive a SMS with information how to register and a token.
Thereafter, the phone is kicked out and will no longer be able to register
again.
Now there was a problem with some phones from Cupertino which, as I heard,
registered to our network, received the SMS, were kicked out again but did not
try to re-register with their home network. So some "nice" guys threaten to
call the Bundesnetzagentur if we will not shut down the network immediately.
As a quick solution, we changed the registration procedure from Token-Input to
IMEI-Input.
My question is: Are there really legal problems when using the "Auth Token"
policy?
Many Thanks,
Lennart
Hi,
I've just pushed a libosmosdr sublibrary in a sylvain/sdr branch in
the libosmocore git.
Currently it contains mostly a complex vector 'class' along with
various math functions used on them (convolution / correlation / ...).
Some aspects the the API along with some of the underlying math are
inspired by the code from openbts, but it is a complete rewrite in
pure C with some aspects simplified, and some others extended.
If anybody has comments before I merge it in master, they're welcome.
The doxygen doc should be clear enough (and even includes fancy latex
equation :P)
Cheers,
Sylvain
From: Pablo Neira Ayuso <pablo(a)gnumonks.org>
Hi!
This patch reworks the timer insfrastructure of libosmocore to
make it more scalable. I remember some discussion with Harald while
I was in Berlin that this can be of interest.
It also reworks the timer torture test, the current list-based
timer seems to have problem with it.
You can find this changes in the pablo/timer branch.
Pablo Neira Ayuso (3):
add rb-tree implementation to libosmocore
timer: add scalable RB-tree based timer infrastructure
tests: add new torture test for timer infrastructure
include/osmocom/core/Makefile.am | 2 +-
include/osmocom/core/linuxrbtree.h | 160 +++++++++++++++
include/osmocom/core/timer.h | 6 +-
src/Makefile.am | 2 +-
src/rbtree.c | 389 ++++++++++++++++++++++++++++++++++++
src/timer.c | 176 +++++++++--------
tests/timer/timer_test.c | 141 ++++++++++---
7 files changed, 757 insertions(+), 119 deletions(-)
create mode 100644 include/osmocom/core/linuxrbtree.h
create mode 100644 src/rbtree.c
--
1.7.2.5
Fix to small spelling error.
diff --git a/openbsc/src/gprs/gprs_gmm.c b/openbsc/src/gprs/gprs_gmm.c index
cc9d297..ff2069a 100644
--- a/openbsc/src/gprs/gprs_gmm.c
+++ b/openbsc/src/gprs/gprs_gmm.c
@@ -1055,7 +1055,7 @@ static int gsm0408_rcv_gmm(struct sgsn_mm_ctx *mmctx,
struct msgb *msg,
break;
case GSM48_MT_GMM_RA_UPD_COMPL:
/* only in case SGSN offered new P-TMSI */
- DEBUGP(DMM, "-> ROUTEING AREA UPDATE COMPLETE\n");
+ DEBUGP(DMM, "-> ROUTING AREA UPDATE COMPLETE\n");
mmctx_timer_stop(mmctx, 3350);
mmctx->p_tmsi_old = 0;
/* Unassign the old TLLI */
Hello Sylvain,
On Mon, 17 Oct 2011 14:11:58 +0200, "Sylvain Munaut" <246tnt(a)gmail.com> wrote:
> And also a fix for the Nokia InSite startup sequence where the reset
> command was not sent due to missing initialization of .do_reset.
The Reset command was enabled in my initial version. As far as I know
it was intentionally disabled during the CCC camp to get faster
turnaround times while setting up the camp network.
Its possible to skip the reset if nothing has changed in the configuration,
however if for example the ARFCN is changed, the reset is required (it
might be possible to do a TRX-only reset but I never tested it).
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi,
> The Reset command was enabled in my initial version. As far as I know
> it was intentionally disabled during the CCC camp to get faster
> turnaround times while setting up the camp network.
>
> Its possible to skip the reset if nothing has changed in the configuration,
> however if for example the ARFCN is changed, the reset is required (it
> might be possible to do a TRX-only reset but I never tested it).
Mmm, I'll retry tonight but at least with the new LAPD code I had
trouble when the reset wasn't there.
Actually to get it to start I have to:
- After powering it, wait for like 10 min. (If I try to start openbsc
any sooner, it will never bootstrap)
- Then start openbsc with the 'reset' part in it.
But I could add this 'reset' process as an nokia specific option to
the vty (i.e. reset_on_start or something ).
Cheers,
Sylvain
Hi all,
this is just a heads-up: The ABI of the osmo_timer has just changed (due
to merging pablo's rb_tree based timer implementation instead of our
linked list one). The API has not changed, so simply recompiling the
programs against the new library header files will work.
As a result, I have bumped the major library version, resulting in
libosmocore-3.0.0.so. There is also a new version tag to mark this
change: 0.4.0
Regards,
Harald
--
- 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)
First Osmocom GMR code release
As some of the readers may already know, a couple of Osmocom developers
have been working on a new sub-project: OsmocomGMR.
The primary goal of this project is to provide a reusable and clean
implementation of the various layers of GMR-1.
What is GMR-1 ? Well, it stands for "GEO Mobile Radio" and it's a set of
specifications describing a satellite based mobile phone network heavily
inspired from GSM. One of the major commercial operators of GMR-1
technology is "Thuraya", providing coverage over
Europe/Africa/Asia/Australia.
So far the implementation focused on the lowest layers:
* Physical layer with FCCH sync and demodulation support for
* pi4-CBPSK and pi4-CQPSK bursts.
* Channel coding layer (scrambling/puncturing/convolutional
coding/crc/interleaving/...)
And some ancillary tools to exploit those:
* A good capture tool to listen to particular ARFCN(s) and
channelize them properly
* Wireshark support (BCCH only so far)
The first 'demo application' using all of the above provides
functionalities similar to what airprobe is for GSM: An air interface
protocol analyzer that goes all the way from capturing data off-the-air
to sending packets to wireshark for analysis. Limited to BCCH only
currently but this will evolve with time.
Development was mainly done by Sylvain Munaut, with help from Dimitri
Stolnikov (early signal captures and his great capture tool), Harald
Welte (initiating the project) and Steve Margraf (testing different
setup and antenna ideas).
If you'd like to know more, you are encourated to read the wiki
(http://gmr.osmocom.org/) and join the mailing list
(http://lists.osmocom.org/mailman/listinfo/gmr)
--
- 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)
Hello all,
Looking for ideas. I have a NanoBTS Model 140 which doesn't seem to
work with GPRS. It never connects to the SGSN. The openbsc/sgsn
environment is ok - I can swap in another nano and it works fine.
I've taken some log captures: