GTP tunnel seems to exist, but No encapsulation when using libgtpnl

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-net-gprs@lists.osmocom.org/.

Papa Tana papa.tana101 at gmail.com
Sun Aug 23 21:06:54 UTC 2020


Hi,

An update as promised, I tried my workaround:

 - sniff from userspace the echo-request sent by peer SGSN to libgtpnl: OK
 - craft a message (echo-response) and send it to SGSN: OK from another
port, but NOK from 2152
 Whatever I tried (bind to low level socket, Linux helper, etc...), it was
impossible because the SGSN only accepts the message that he recognize that
he has sent, and wait for the exact pair {ip, port} so, it was impossible
for me since it was owned by libgtpnl when I invoke  "gtp-link add".

The previous suggestion is really interesting to me:
* - speak netlink directly to the GTP-U module.*

Yes, there is some library that can speak netlink, but since I want to
learn first how to do it without using a library, I have learned how to
speak netlink to Linux Module (libnl-genl).
I have checked out the message structure(headers, length, type, flags,
sequence number, pid, Command, Data, ....).
I have monitored some stuff by using "nlmon".
And now, I can create a netlink socket as a File Descriptor, craft some
Netlink Message manually, flush it to the kernel and receive some response
from a sample kernel module.

But my question is, and what I need help with, what data does GTP.ko expect
from me when I need to request an add or delete tunnel, since I cannot see
any documentation about Linux GTP module interface.
I'm not requesting a code, but only the message or binary I need to
transport in my netlink socket towards GTP-U Linux module.

Thanks for any help or hint,
Best Regards,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/osmocom-net-gprs/attachments/20200824/2dd46d2a/attachment.htm>


More information about the osmocom-net-gprs mailing list