Weird usage of gprs_ns_vty_init from gprs_bssgp_create

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/.

Andreas Eversberg andreas at eversberg.eu
Fri Jun 28 14:00:56 UTC 2013


Holger Hans Peter Freyther wrote:
> The dangling pointer will lead to a crash when the VTY of the PCU is
> used in such situation/window.
>   
hi holger,

the main problem is that the bssgp/ns instance is created at the time
the bts (and the pcu) receives informations from bsc. the pcu cannot
(yet) instantiate at startup time, the required informations for the
instance are not yet present then. this means that the pcu.cfg cannot
have any ns/nse vty command. i don't see a good solution right now.
maybe it is possible to create only the bssgp/ns instance itself,
without creating, listening, connecting the nsvc. then, if the bts
becomes unavailable, the nsvc is destroyed only, then the nsvc can be
created again on next start of bts.

regards,

andreas





More information about the osmocom-net-gprs mailing list