osmocom-net-gprs January 2022

osmocom-net-gprs@lists.osmocom.org

5 participants
11 discussions

OsmoDevCon 2022 ?

by Harald Welte

Dear fellow Osmocom developers, as you all know, we've sadly had to skip OsmoDevCon 2020 and 2021, trying to compensate it at least to some extent with our OsmoDevCall every two weeks. The COVID-19 pandemic is far from over, and we don't know what the upcoming winter season will bring. Nevertheless, I think it would be a good idea to start a discussion of whether we should plan for an OsmoDevCon in 2022. I personally would say let's plan for the usual late April 2022 time frame, and if the pandemic situation deteriorates, we can still cancel it with something like one month lead time. I would also personally suggest to limit attendance to people who are fully vaccinated, and in addition do a self-test for all participants every morning. In terms of venue, we might also consider to move to a venue that allows better ventilation. Irrespective of the above we can also bring the air filters from the sysmocom office. So with that as an input statement, I would like to hear your opinion on the above proposals. Who would want to attend? Any complaints against the "vaccinated only plus daily self-tests in the morning" approach? Regards, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 years, 1 month

[RFC PATCH net-next v3 1/5] gtp: Allow to create GTP device without FDs

by Marcin Szycik

From: Wojciech Drewek <wojciech.drewek(a)intel.com> Currently, when the user wants to create GTP device, he has to provide file handles to the sockets created in userspace (IFLA_GTP_FD0, IFLA_GTP_FD1). This behaviour is not ideal, considering the option of adding support for GTP device creation through ip link. Ip link application is not a good place to create such sockets. This patch allows to create GTP device without providing IFLA_GTP_FD0 and IFLA_GTP_FD1 arguments. If the user does not provide file handles to the sockets, then GTP module takes care of creating UDP sockets by itself. Sockets are created with the commonly known UDP ports used for GTP protocol (GTP0_PORT and GTP1U_PORT). In this case we don't have to provide encap_destroy because no extra deinitialization is needed, everything is covered by udp_tunnel_sock_release. Signed-off-by: Wojciech Drewek <wojciech.drewek(a)intel.com> --- drivers/net/gtp.c | 74 ++++++++++++++++++++++++++++++++++++++++++----- 1 file changed, 67 insertions(+), 7 deletions(-) diff --git a/drivers/net/gtp.c b/drivers/net/gtp.c index 24e5c54d06c1..a2ad0af913cb 100644 --- a/drivers/net/gtp.c +++ b/drivers/net/gtp.c @@ -66,8 +66,10 @@ struct gtp_dev { struct sock *sk0; struct sock *sk1u; + u8 sk_created; struct net_device *dev; + struct net *net; unsigned int role; unsigned int hash_size; @@ -320,8 +322,16 @@ static void gtp_encap_disable_sock(struct sock *sk) static void gtp_encap_disable(struct gtp_dev *gtp) { - gtp_encap_disable_sock(gtp->sk0); - gtp_encap_disable_sock(gtp->sk1u); + if (gtp->sk_created) { + udp_tunnel_sock_release(gtp->sk0->sk_socket); + udp_tunnel_sock_release(gtp->sk1u->sk_socket); + gtp->sk_created = false; + gtp->sk0 = NULL; + gtp->sk1u = NULL; + } else { + gtp_encap_disable_sock(gtp->sk0); + gtp_encap_disable_sock(gtp->sk1u); + } } /* UDP encapsulation receive handler. See net/ipv4/udp.c. @@ -664,9 +674,6 @@ static int gtp_newlink(struct net *src_net, struct net_device *dev, struct gtp_net *gn; int hashsize, err; - if (!data[IFLA_GTP_FD0] && !data[IFLA_GTP_FD1]) - return -EINVAL; - gtp = netdev_priv(dev); if (!data[IFLA_GTP_PDP_HASHSIZE]) { @@ -677,6 +684,8 @@ static int gtp_newlink(struct net *src_net, struct net_device *dev, hashsize = 1024; } + gtp->net = src_net; + err = gtp_hashtable_new(gtp, hashsize); if (err < 0) return err; @@ -844,6 +853,38 @@ static struct sock *gtp_encap_enable_socket(int fd, int type, return sk; } +static struct sock *gtp_encap_create_sock(int type, struct gtp_dev *gtp) +{ + struct udp_tunnel_sock_cfg tuncfg = {}; + struct udp_port_cfg udp_conf = { + .local_ip.s_addr = htonl(INADDR_ANY), + .family = AF_INET, + }; + struct net *net = gtp->net; + struct socket *sock; + int err; + + if (type == UDP_ENCAP_GTP0) + udp_conf.local_udp_port = GTP0_PORT; + else if (type == UDP_ENCAP_GTP1U) + udp_conf.local_udp_port = GTP1U_PORT; + else + return ERR_PTR(-EINVAL); + + err = udp_sock_create(net, &udp_conf, &sock); + if (err) + return ERR_PTR(err); + + tuncfg.sk_user_data = gtp; + tuncfg.encap_type = type; + tuncfg.encap_rcv = gtp_encap_recv; + tuncfg.encap_destroy = NULL; + + setup_udp_tunnel_sock(net, sock, &tuncfg); + + return sock->sk; +} + static int gtp_encap_enable(struct gtp_dev *gtp, struct nlattr *data[]) { struct sock *sk1u = NULL; @@ -868,11 +909,30 @@ static int gtp_encap_enable(struct gtp_dev *gtp, struct nlattr *data[]) } } + if (!data[IFLA_GTP_FD0] && !data[IFLA_GTP_FD1]) { + sk0 = gtp_encap_create_sock(UDP_ENCAP_GTP0, gtp); + if (IS_ERR(sk0)) + return PTR_ERR(sk0); + + sk1u = gtp_encap_create_sock(UDP_ENCAP_GTP1U, gtp); + if (IS_ERR(sk1u)) { + udp_tunnel_sock_release(sk0->sk_socket); + return PTR_ERR(sk1u); + } + gtp->sk_created = true; + } + if (data[IFLA_GTP_ROLE]) { role = nla_get_u32(data[IFLA_GTP_ROLE]); if (role > GTP_ROLE_SGSN) { - gtp_encap_disable_sock(sk0); - gtp_encap_disable_sock(sk1u); + if (gtp->sk_created) { + udp_tunnel_sock_release(sk0->sk_socket); + udp_tunnel_sock_release(sk1u->sk_socket); + gtp->sk_created = false; + } else { + gtp_encap_disable_sock(sk0); + gtp_encap_disable_sock(sk1u); + } return -EINVAL; } } -- 2.31.1

2 years, 2 months

[RFC PATCH net-next v2 1/5] gtp: Allow to create GTP device without FDs

by Marcin Szycik

2 years, 2 months

[RFC PATCH net-next v3 2/5] gtp: Add support for checking GTP device type

by Marcin Szycik

From: Wojciech Drewek <wojciech.drewek(a)intel.com> Add a function that checks if a net device type is GTP. Signed-off-by: Wojciech Drewek <wojciech.drewek(a)intel.com> --- include/net/gtp.h | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/include/net/gtp.h b/include/net/gtp.h index 0e16ebb2a82d..ae915dd33d20 100644 --- a/include/net/gtp.h +++ b/include/net/gtp.h @@ -27,6 +27,12 @@ struct gtp1_header { /* According to 3GPP TS 29.060. */ __be32 tid; } __attribute__ ((packed)); +static inline bool netif_is_gtp(const struct net_device *dev) +{ + return dev->rtnl_link_ops && + !strcmp(dev->rtnl_link_ops->kind, "gtp"); +} + #define GTP1_F_NPDU 0x01 #define GTP1_F_SEQ 0x02 #define GTP1_F_EXTHDR 0x04 -- 2.31.1

2 years, 3 months

[RFC PATCH net-next v2 2/5] gtp: Add support for checking GTP device type

by Marcin Szycik

2 years, 3 months

lists.osmocom.org migrated to mailman3

by Harald Welte

Dear Osmocom community, today our mailing list server lists.osmocom.org has finally been migrated from mailman2-on-freebsd to mailman3-on-linux. This also included a variety of changes to DNS. I'll spare you the details, but everything _should_ be up and running now. * The List-Id headers should not have changed. * all list subscriptions + user accounts have been converted. * old 'static html' archives are still available (read only) at URLs like https://lists.osmocom.org/pipermail/baseband-devel/ * old List URLs like https://lists.osmocom.org/mailman/listinfo/baseband-devel are redirected to their respective modern counterparts In case you notice any mailing list related problem, please don't hesitate to contact me. Happy hacking, Harald -- - Harald Welte <laforge(a)osmocom.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

2 years, 3 months

None

by None

RLC/MAC layer in real networks is always used in acknowledged/reliable mode, and LLC is always only used in unreliable (UI) mode. The reason for this is that TCP cannot deal with the enormous packet loss that GPRS or similar radio links pose. If TCP would be exposed to the real packet loss, it would stall way too much. So my rationale was to use the same while creating osmo-sgsn. We use LLC in UI mode. Or are we talking about something completely else? 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)

2 years, 3 months

None

by None

* With multiple TBF assignment the tbf_by_tlli will return a list =A0 anyway. * For the multiple RACH cases we could it probably handle it more =A0 nicely. E.g. avoid this: <0005> bts.cpp:1035 Got RACH from TLLI=3D0xcf7611f6 while TBF(TFI=3D0= TLLI=3D0xcf7611f6 DIR=3DDL) still exists. Killing pending DL TBF <0002> bts.cpp:359 Got IMM.ASS confirm, but TLLI=3Dcf7611f6 does not = exit -- - Holger Freyther <<a href=3D"mailto:hfreyther@sysmocom.de">hfreyther@sy= smocom.de</a>> =A0 =A0 =A0 <a href=3D"http://www.sysmocom.de/" target=3D= "_blank">http://www.sysmocom.de/</a> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte </blockquote></div> </div> --20cf301d42625eb38c04ea05cbef--

2 years, 3 months

None

by None

* With multiple TBF assignment the tbf_by_tlli will return a list anyway. * For the multiple RACH cases we could it probably handle it more nicely. E.g. avoid this: <0005> bts.cpp:1035 Got RACH from TLLI=0xcf7611f6 while TBF(TFI=0 TLLI=0xcf7611f6 DIR=DL) still exists. Killing pending DL TBF <0002> bts.cpp:359 Got IMM.ASS confirm, but TLLI=cf7611f6 does not exit -- - Holger Freyther <hfreyther(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte

2 years, 3 months

None

by None

if we should use more C++ features (I am not talking STL, operator overloading)? Any opinions? holger PS: I think we should find a more nice solution to extern "C".. I spent various minutes trying to figure out which parts of the pcu have C linkage and which C++.. For things from libosmocore it is obvious.. but then we have the vty_info... -- - Holger Freyther <hfreyther(a)sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Schivelbeiner Str. 5 * 10439 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte

2 years, 3 months

None

by None

bug fixes. Ideally I'd love to see Andreas developing them on top of the current 'master' and submitting them to the mailing list as soon as he push them. This way Ivan (and everyone else) would be able to review them and merge as soon as possible. I hate the situation when fixes are stored in a private branch and are not merged into mainline. On Mon, Nov 26, 2012 at 5:02 PM, Ivan Kluchnikov <Ivan.Kluchnikov(a)fairwaves.ru> wrote: > Hi, all! > > I absolutely agree with Harald and I am ready to use described life-cycle > model for osmo-pcu. > Before that time I merged branch 'jolly', when the differences between > master and jolly become critical. > I didn't coordinate merges with Andreas and jolly branch wasn't rebased > before merges. I think, it was my mistake. > Now I am ready to merge jolly branch at any time, when Andreas indicates > that his branch is ready for merge. > > > 2012/11/25 Harald Welte <laforge(a)gnumonks.org> >> >> Dear all, >> >> it is a pity to see that since many weeks there has been no progress on >> merging any of Andreas' work. I think everyone involved is to be >> blamed to some extent. Andreas because the provided branches are not >> kept clean, Ivan probably for lack of time, and me for not paying more >> attention and helping this process along. >> >> The general life-cycle in any project, including osmo-pcu, should be as >> follows: >> >> * contributor starts on some improvements, creates private branch >> * master advances meanwhile >> * contributor rebases (not merges!) his changes on top of more recent >> master >> * contributor indicates that his branch is ready for merge >> * maintainer merges (some of?) the commits of the contributor branch >> * contributor re-bases remaining commits on new master >> * contributor requests merge of remaing patches >> ... >> >> If I open 'gitk' on any of the branches (master / jolly / jolly_dsp) I >> get grey hair (to say the least). One would normally expect: >> >> 1) 'jolly' to be based on some (maybe not current) master >> >> 2) 'jolly_dsp' to be based on 'jolly' >> >> Neither of the two is the case. I've tried to >> * rebase jolly on top of master >> as well as >> * rebase jolly_dsp on top of jolly >> >> and both are impossible due to the series of merges and the unclear >> ancestry / relationship of the branches. Or, just for fun, try 'git >> diff origin/jolly..origin/jolly_dsp. It shows you anything else but >> what one would expect >> >> Andreas: Please take some time to clean up the mess. Your 'jolly' >> branch should contain a series of clean per-feature commit's on top of >> current master, and 'jolly_dsp' should be a set of few patches on top of >> 'jolly'. >> >> This way there is always a clean queue of changesets that Ivan can merge >> (or cherry-pick). I can understand that if I was in Ivan's place, I >> would not really know where to even start merging some of those >> contributions. >> >> Thanks for everyone's attention. Please take some time to get this >> resolved. Let me know if you have some questions. There are plenty of >> people with lots of git experience around (Holger, Pablo, myself) who >> can help if something is unclear. >> >> Regards, >> Harald >> >> -- >> - Harald Welte <laforge(a)gnumonks.org> >> http://laforge.gnumonks.org/ >> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D >> "Privacy in residential applications is a desirable marketing option." >> (ETSI EN 300 175-7 Ch. >> A6) >> > > > > -- > Regards, > Ivan Kluchnikov. > http://fairwaves.ru > --=20 Regards, Alexander Chemeris. CEO, Fairwaves LLC / =D0=9E=D0=9E=D0=9E =D0=A3=D0=BC=D0=A0=D0=B0=D0=B4=D0= =B8=D0=BE http://fairwaves.ru

2 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

osmocom-net-gprs January 2022