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.orgHi Sylvain and Daniel,
On Thu, Jan 07, 2010 at 07:39:54AM +0100, Sylvain Munaut wrote:
> I've noticed that recent versions of bs11_config don't show all the
> > infos they used to.
> >
> > commit eb429b7b44f1c39548a1995cb93484b9cbe2996e
> > Author: Sylvain Munaut <tnt at 246tNt.com>
> > Date: Mon Oct 26 20:19:59 2009 +0100
> >
> > [TLV] Split the parser into 'parse loop' and 'parse single value'
> >
> > seems to be the problem. If I revert it bs11_config query shows more
> > information again. I've looked at the patch, but so far couldn't find
> > out what it does differently. I'll keep looking, but maybe someone else
> > has an idea.
>
> The way they react to unknown tag is different. (when
> def->def[tag].typedef->def[tag].type doesn't contain anything valid).
>
> Could you post a hex dump of the TLV block where their decoding differs ?
No, it actually is related to the different TLV type of some NM attributes
depending on ip.access and BS-11 (such as AVAIL_STATUS).
I've fixed this in 39315c47989326275823d1589425ee62d15bc823 and bs11_config
query now shows all the data again.
--
- 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)