Hi,
I just noticed that the GGSN returns its IP address in a GTP packet about
PDP, in the "End User Address" IE (etsi/GSM/by_chapter/29.060.pdf 7.7.27).
I'm asking myself whether this needs to be mapped by gtphub.
127.0.0.3 127.0.0.2
SGSN <-------- GTPHUB <--------- GGSN
"127.0.0.2" "127.0.0.2"
map this? ^
This sounds almost like no mapping is required, as if it tells the MS
which IP address it has "as seen from outside":
"The PDP Address shall be the address that this PDP context of the MS is
identified with from the external packet data network."
But I have no idea, really. Does anyone else? If not, we'll just have to
see later...
Thanks!
~Neels
Hi openbsc,
here is my improved version of the OAP aka SGSN-ID patch series.
This series is pushed to the neels/sgsn-id-3 branch.
This version is substantially simpler, because I decided against factoring out
the IPA client. Instead, the gprs_gsup_client.c will directly call the OAP API
to handle OAP messages. Factoring out the IPA client was not a requirement and
taking too much time, and since the name will remain "GSUP client" (to avoid
changing the VTY configuration names among other things), it does after all
make sense to think of it as: "the GSUP client employs OAP to authenticate"
instead of "GSUP and OAP are two separate clients on the IPA wire".
The OAP spec has changed. Particularly instead of SRES and Kc, the challenge
response now sends XRES only; and the spec now includes an AUTS request (not
yet implemented).
Going through the changes, I've made a few fixes (like wrong file header
comments), and made some changes. The OAP API looks quite different, and now
merely returns struct msgb* and lets the caller take care of sending.
This time, OAP has its own separate testsuite tests/oap.
I have further OAP tests in mind to add; particularly the complete SGSN
registration test from the previous patch version is not yet included here.
Anyway, the OAP API test has become more comprehensive.
Some of the patch mods have come from comments by hfreyther and jerlbeck, other
changes were obvious from reviewing the code.
I think this time around the patch is much more mature. I hope you agree, if
not I'll gladly improve it further, of course :)
Thanks for your reviews!
~Neels
These patches fix some things that hurt my eyes. The renames from dublicate to
duplicate may theoretically break API compat, but I could find no affected
callers. These are not required, feel free to veto...
~Neels
Hi all!
This is an announcement for an "irregular" Berlin Osmocom User Group
event.
David Rupprecht of Ruhr-Uni Bochum has offered to give us a presentation
sharing his experience in Running OpenAirInterface.
OpenAirInterface (http://openairinterface.eurecom.fr/) is a project of
the Eurecom research institute in Sofia Antipoils / France. For many
years they have been working towards an open source SDR LTE
implementation.
The presentation will be held on
Oct 15, 8pm @ IN-Berlin, Lehrter Str. 53, 10557 Berlin
(yes, this is _NOT_ CCC Berlin where regular OSMUG meetings are held!)
The meeting is open to anyone interested in mobile communications. You
do not have to be involved with the Osmocom projects in order to attend.
Anyone interested in mobile communications protocols is welcome.
If you are interested to show up, feel free to do so. The meeting is
"free as in free beer", despite no actual free beer being around ;)
More information about the venue can be found at
http://www.in-berlin.de/space/
The official event announcement website is
http://openbsc.osmocom.org/trac/blog/david-rub-openair-20151015
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi openbsc,
the following patch series adds a GTP hub program (maturity level:
proof-of-concept). Its aim is related to the recent addition of OAP: it will
allow routing multiple SGSNs through one GTP server hub (proxy).
The program so far forwards UDP packets to and from hardcoded ports, and logs
validity of GTP headers passing through. I think this a good time to do a
review cycle and merge to master, before adding the interesting stuff.
What will follow: decode GTP body, map/separate PDP contexts across clients and
servers, replace TEIs. To do that without reinventing the GTP wheel, I may need
to separate data parsing from send/recv in openggsn.
There are also some bits that should probably be moved out (to where I copied
it from) and the API there changed (so that I can use it here without copying).
Those are clearly marked with todo comments.
Thanks for your review!
~Neels
Hi Nico,
[responding to the openbsc list, as it is more applicable than
baseband-devel]
On Sun, Oct 04, 2015 at 01:59:41PM +0200, Nico Golde wrote:
> For those interested... is there any code for osmo-iuh already available
> somewhere? I don't see it on git.osmocom.org.
it is not yet published, I would like to do that at the date of the
event itself. It will be on git.osmocom.org.
The actual core HNBAP/RUA code is already there. Next is the plan on
how to integrate with the existing OsmoNITB. Somehow the A interface
code needs to be abstracted out, so that a subscriber_connection can
either be served by an A or by an IuCS interface.
Another step currently needed is UMTS AKA in the NITB.
Once the above two problem areas are adressed, we should have a solution
that works at least for signalling (LU, SMS, USSD,...).
--
- 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)
Hi all!
This is the announcement for the re-incarnated Osmocom Berlin meeting:
Oct 7, 8pm @ CCC Berlin, Marienstr. 11, 10117 Berlin
Harald will be presenting about the Iuh protocol stack of UMTS small
cells / femtocells and his work towards implementing it as part of
Osmocom.
Agenda:
20:00h Welcome
20:15h Presentation about Iuh / osmo-iuh
21:00h Informal meeting / chatting
The meeting is open to anyone interested in mobile communications. You
do not have to be involved with the Osmocom projects in order to attend.
Anyone interested in mobile communications protocols is welcome.
If you are interested to show up, feel free to do so. There is no
registration required. The meeting is free as in "free beer", despite
no actual free beer being around.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org>
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello,
One of our BS-11 stations began to behave strangely. I see the following messages
during boot-up:
PHASE: 1 Load SMU Intended Abis-link: Down
PHASE: 2 Load MBCCU MBCCU0: No Load MBCCU1: No Load Abis-link: Down
PHASE: 2 Load MBCCU MBCCU0: Load BTSCAC MBCCU1: No Load Abis-link: Down
PHASE: 2 Load MBCCU MBCCU0: Load BTSCAC MBCCU1: Load BTSCAC Abis-link: Down
PHASE: 2 Load MBCCU MBCCU0: Load BTSCAC MBCCU1: No Load Abis-link: Down
It looks like BS tries to load firmware on MBCCU1 and then gives up.
I tried to delete and re-create trx1 objects using bs11_config, no result.
Tried to reflash BS11, but got software load NACK, and when using —force option
the software download process finishes but the boot-up message is the same as above.
Does it mean that TRX1 is failed and cannot be used no more?
Best Regards,
Sergey.