TLLI problems and proposed solution

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/OpenBSC@lists.osmocom.org/.

Holger Hans Peter Freyther holger at freyther.de
Tue Jul 30 09:03:12 UTC 2013


On Tue, Jul 30, 2013 at 10:05:24AM +0200, Holger Hans Peter Freyther wrote:

> I added the below diff.. but it is probably better to check if one could
> combine these llme's at a higher level? Or at least free the old LLME
> and use the new one? My last problem right now is that LLC data is not
> sent to the GGSN.. :}

*aehm* i had a hacked-up libgtp... for doing some perf measurements of
tun0... I am currently attempting to watch youtube on my E71.. but it is
buffering a lot and the 10s PDU lifetime does not appear big eough.. so
there are a lot of re-transmissions going on.

>  		/* make sure we only send it to the right llme */
>  		OSMO_ASSERT(msgb_tlli(msg) == mmctx->llme->tlli
> -				|| msgb_tlli(msg) == mmctx->llme->old_tlli);
> +				|| msgb_tlli(msg) == mmctx->llme->old_tlli
> +				|| tlli_foreign2local(msgb_tlli(msg)) == mmctx->llme->tlli);

and add the same for the old_tlli. :}




More information about the OpenBSC mailing list