Hi,
I see that while adding decompression support dexter has fixed a bug in
the sndcp code. Before the GTP-U frame would include the LLC FCS and now
we do this:
npdu_len = (msg->data + msg->len) - npdu - 3;
What I wonder (and the commit message didn't say is) was the fragment
part handled as well. The calculation is:
/* make sure to subtract length of SNDCP header from 'len' */
rc = defrag_enqueue(sne, suh->seg_nr, data, len - (data - hdr));
and len is passed in from the TLV struct in gprs_llc_rcvmsg. I think the
fragmented case is working okay.
Shall we try to unify the length calculation to rely on the local "len"
variable instead of checking msg->data+msg->len?
cheers
holger
Hi,
I am currently working in a project where I was asked to implement a GTP
tunnel from client to company servers.
I have read through osmocom pages and tried to implement the simple network
structure. I have seen from Basic testing of openGGSN page:
" test GTP-U interoperability of the kernel with at least one other
implementation, not just kernel-to-kernel (which currently is not supported
in the kernel, as it only implements the GGSN/P-GW role) "
I would not like to implement openGGSN but just linux-kernel-gtp-u
implementation between two kernels.
To achieve kernel-to-kernel implementation, I found sgsn patch on the
internet:
https://patchwork.ozlabs.org/patch/739408/
and there is already a kernel-gtp-U in osmocom.
So, my basic network structure is below.
[image: Satır içi resim 2]
I would like make a tunnel between sgsn and ggsn. I have used libgtpnl
tools to create link and then tunnel. I have added a default gateway GTP
interface to route table on sgsn side, but the packets cannot reach ggsn
side.
Is there any detailed explanation for a simple bidirectional tunnel setup.
If so, it would be so nice to know about.
Thank you for all your efforts,
Fırat
Hi all,
the Osmocom Conference 2017 last week was an overwhelming success. We
received lots of positive feedback from all sides. Thanks to all the
speakers, to the attendees as well as to the anonymous sponsor of the
travel grant funds.
It is my great pleasure that due to the great support by C3VOC (The CCC
Video Operation Center), we have full recordings of all talks given at
OsmoCon 2017.
You can find the videos on the C3VOC site at
https://media.ccc.de/search/?q=osmocon
They are also linked individually from the OsmoCon 2017 homepage at
https://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017
I hope the video recordings will be of help for everyone who could not
make it to the event in person.
We will also be collecting the slides and put them up on the wiki during
the next few days.
Please don't hesitate to raise any feedback and/or questions.
Technical feedback/questions regarding Osmocom software / projects
should be addressed to the appropriate mailing lists, such as
openbsc(a)lists.osmocom.org.
Feedback to the organizers should be sent to osmocon2017(a)sysmocom.de.
Looking forward to the next OsmoCon, which we'll expect to be spanning
ore than just a single day.
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)
Hi Harald and Andreas,
I’m writing to inquiry about the development roadmap of the kernel gtp module. For example, is there any plan to support the following features soon
- lightweight tunnel
- ipv6
The openair-cn project I’m working on is a user of the kernel gtp module. I’m happy to help improve the kernel gtp support, so it’s good to first ask about the roadmap.
Regards,
-Jiannan
Hi everyone,
We're using kernel GTP developed by Osmocom on openair-cn. Turns out that we
are not able to connect an UE for longer than 20 seconds using an ZTE eNB
apparently because the GTP-U is not answering to the echo requests. As far I
know this response is supposed to be implemented but it is not answering. Do
you guys have any tips on this issue?
Thanks in advance,
Alandre
Hi All,
In current OAI implementation, we found that there are cases SPGW is out-of-sync with MME, because of the delete_session_request is not received by the SPGW because of some errors, however MME has cleared the state of that session. Then when the UE re-attaches, a new create_session_request is sent to SPGW; and because we try to allocate the same IP for the same IMSI (local change), the SPGW will result out in trying to update an existing GTP tunnel.
According to http://lxr.free-electrons.com/source/drivers/net/gtp.c#L937 and https://github.com/RoadRunnr/osmo-ggsn/blob/master/libgtnl/src/gtp-genl.c#L…, the NLM_F_EXCL flag is used to prevent updating an existing tunnel. I’m is wondering what is the reason of preventing updating?
While we are actively investigating sending delete_session_request properly, as temporary workaround, I’m thinking to recovery from the out-of-sync problem, we can allow the new GTP tunnel to overwrite the old one in libgtpnl. Your suggestions are welcomed. Thanks.
Regards,
-Jiannan
OsmoCon 2017 updates
There are some updates related to OsmoCon2017, the first Osmocom
Conference, held on April 21st, 2017 in Berlin, Germany.
See http://osmocom.org/news/68 for the web version of this announcement.
== Summary ==
Summary (for those too busy to read the full post):
* Schedule of talks has been released
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017#Schedule
* Travel Grants available for participants who are otherwise unable to
travel to Berlin: http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_TravelGrants
* Social Event details available, including menu:
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_SocialEvent
* April 21st is approaching fast, make sure you get your Ticket in time.
Limited number of seats available
http://shop.sysmocom.de/products/ticket-for-osmocon-2017
== Details ==
=== Schedule has been released ===
The list of talks with their abstracts has been on the website for quite
some time, but now we actually have put together a schedule based on
those talks.
Please see
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017#Schedule
for the schedule.
As you can see, the day is fully packed with talks about Osmocom
cellular infrastructure projects. We had to cut some talk slots short
(30min instead of 45min), but I'm confident that it is good to cover a
wider range of topics, while at the same time avoiding fragmenting the
audience with multiple tracks.
=== Travel Grants ===
We are happy to announce that we have received donations to permit for
providing travel grants!
This means that any attendee who is otherwise not able to cover their
travel to OsmoCon 2017 (e.g. because their interest in Osmocom is not
related to their work, or because their employer doesn't pay the travel
expenses) can now apply for such a travel grant.
For more details see
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_TravelGrants
and/or constact osmocon2017(a)sysmocom.de.
=== Social Event ===
Tech Talks are nice and fine, but what many people enjoy even more at
conferences is the informal networking combined with good food. For
this, we have the social event at night, which is open to all attendees.
See more details about it at
http://osmocom.org/projects/osmo-dev-con/wiki/OsmoCon2017_SocialEvent
--
- 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,
building osmo-pcu on a raspberry Pi 3, I noticed a failure in make check:
## --------------------------------- ##
## osmo-pcu 0.2.896-0a8f test suite. ##
## --------------------------------- ##
Regression tests
1: rlcmac ok
2: ts_alloc ok
3: tbf ok
4: bitcomp FAILED (testsuite.at:30)
5: edge ok
6: types ok
7: ms ok
8: llc ok
9: llist ok
10: codel ok
11: fn ok
## ------------- ##
## Test results. ##
## ------------- ##
ERROR: All 11 tests were run,
1 failed unexpectedly.
## -------------------------- ##
## testsuite.log was created. ##
## -------------------------- ##
The exact same test also fails on a raspberry Pi 2, with the same
osmo-pcu and gcc versions but succeeds on an old Pentium4
Feel free to contact me if you need further informations.
-----
Arnaud ZANETTI