[PATCH 3/3] bsc: on-demand setup of nanoBTS and HSL femto sockets

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

Harald Welte laforge at gnumonks.org
Wed May 4 09:02:53 UTC 2011


On Tue, May 03, 2011 at 11:29:16PM +0200, Holger Hans Peter Freyther wrote:
> On 05/03/2011 10:44 PM, pablo at gnumonks.org wrote:
> > From: Pablo Neira Ayuso <pablo at gnumonks.org>
> > 
> > The daemon set up nanoBTS and HSL femto sockets by default,
> > ie. the three sockets to support these two drivers are open even
> > if we have no BTS of that kind. This patch enables them if they
> > are present in any configuration file.
> 
> good goal, but maybe trigger this from within the VTY code? E.g. what
> if I want to add a HSL BTS to a running system? or start with no
> config file at all? Anyway our story of doing such config changes at
> runtime is not very good.

yes, but I agree we should do this from the VTY code.  At least all new
features we're adding should be more runtime vty based then thinking of
a config file that we parse once and then forget about it.

So when we get a 'bts type ...' command (or when we leave the BTS_NODE)
we should check if the respective sockets are needed.

But yes, another big long pending TODO is to think about how we can
make most or even all runtime config changes work.

-- 
- Harald Welte <laforge at gnumonks.org>           http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)




More information about the OpenBSC mailing list