Re: Open Source Software Stack for 3G

[Neels Hofmeyr]

> didn't take the time to rtfd

It's not exactly trivail of course, and questions are welcome.
But I guess a good starting point to get osmocom running on your own is
https://osmocom.org/projects/cellular-infrastructure/wiki/Osmocom_Network_In_The_Box

~N

Re: Open Source Software Stack for 3G

[Neels Hofmeyr]

Osmocom has 3G support, so which part is missing for you? What is your aim?

~N

On Wed, Sep 13, 2023 at 06:08:51AM +, 200207...@kocaeli.edu.tr wrote:
> Hello, I am a student at Kocaeli University. I am looking for open source 
> software stack for 3G like OpenAirInterface for 5G or Osmocom for 2G for my 
> work. (Osmocom has partial support for 3G)
> 
> I request you to direct me to the right resource that may know.
> 
> Thanks for your time and interest.
> 
> Kind regards,

-- 
- Neels Hofmeyr   http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte

Re: failure in Transceiver startup

[Neels Hofmeyr]

On Tue, Nov 29, 2022 at 03:07:26AM +0100, Sally Regenbogen wrote:
> The CLI gave me this error:
> 
> ~/osmocom/osmocom-bb/src/host/layer23/src/transceiver# sudo ./transceiver -e
> 1 -2 -a 47 -r 99
> 47
> 41
> 1
> <000c> l1ctl.c:77 Tx Reset Req (1)
> <000c> l1ctl_link.c:171 Sending: '0d 00 00 00 01 00 00 00 '
> <000c> l1ctl.c:77 Tx Reset Req (1)
> <000c> l1ctl_link.c:171 Sending: '0d 00 00 00 01 00 00 00 '
> Aborted

I'm not familiar with 'transceiver', just a general approach:
Whenever I see a program just aborted like this, one way to find out why is gdb.
Maybe this can give a hint on where in the code it aborted:

 gdb -ex run --args ./transceiver -e 1 -2 -a 47 -r 99

it helps when the program is built with debug symbols enabled.

when you know which place in the code bailed out it might give hints on the
cause and/or how to work around it, when you're lucky.

~N

Re: About 3g5 hardware

[Neels Hofmeyr]

Hi Bastien,

whether the device connects to your HNB-GW depends on the firmware +
configuration run on the device. The firmware cannot be shared openly.

Given that you gain access to the DMI configuration interface, this wiki page
may help:

https://osmocom.org/projects/cellular-infrastructure/wiki/Configuring_the_ipaccess_nano3G

~N

Re: New attack ?

[Neels Hofmeyr]

On Tue, Mar 01, 2022 at 11:16:50AM -0800, Mychaela Falconia wrote:
> mode.  I reason that these "modern" SIMs must be using Milenage in
> their native 3G/4G mode, thus their secret key material is not classic
> Ki, but K/Ki (128 bits) plus OPc (another 128 bits), for a total of
> 256 bits of secret key material.
> 
> What happens when these "modern" SIMs are accessed via GSM 11.11 SIM
> protocol, or when 2G authentication is requested in a USIM session?

Networks and user equipment capable of UTRAN a.k.a. R99+ ("release 99"), do use
full Milenage AKA even on 2G networks. For pre-R99 MS on a UTRAN capable
network, the HLR and USIM may use the 3G key material as basis to generate
shorter authentication tokens -- this is not seen in practice at all these
days. It is reasonable to expect full Milenage Authentication and Key Agreement
everywhere.

Figure 18 in 3GPP 33.102 section 6.8.1.1 shows all of this in detail. I had
this chart on the wall when implementing UMTS AKA in osmo-hlr and osmo-msc.

~N

Re: OsmoDevCon 2022 ?

[Neels Hofmeyr]

> requiring vaccination to attend by default. Maybe with the option for 
> attendees
> to request attendance despite no vaccination, and then see whether we can
> unanimously agree on that?

I'd like to add that I find it should also be sufficient to have recovered from
COVID. This is a common rule in schools in Berlin that does relieve teachers
from the need to test regularly (called 2G, incidentally).

Another question is whether we play by RKI rules and not accept certain
vaccines.

I guess we should first see whether anyone would be refused attendance based on
these rules and take it from there?

Here is a dudle to anonymously figure out the current vaccination status. Feel
free to enter your current status, especially if you're not fully vaccinated
and would like to attend. This is just to get a basis for discussion:

https://dudle.inf.tu-dresden.de/w93G6NPqfA/

I guess we need to repeat such poll in early '22.

Re: Osmocom Mailing List re-organization

[Neels Hofmeyr]

I think we also could change jenkins-notifications and/or gerrit-log, IIRC one
of those was once named "the high noise mailing list" and catches more than
just what the name says, currently don't remember which/both of them?

builds@ ?
noise@ ?
build-noise@ ?

Re: Osmocom C files syntax understanding

[Neels Hofmeyr]

On Thu, Nov 19, 2020 at 10:57:14PM +0300, Mario Lucas wrote:
> I mean instead of rush and head hit against some difficult C codes in Osmocom 
>  — to have relatively easy kind of «sub-project» of Osmococom for start 
> learning purposes….

Sorry to dissappoint you, but all of Osmocom code is inherently relatively
complex. It is neither practical nor required to understand all of it, we are
numerous "experts" with knowledge in specific parts.

The only way that I gained knowledge about Osmocom so far is that I get a
specific task ("Implement X" or "Fix Y") and then bang my head against it until
I understand what is going on. It is almost never easy, I often need help first.

If you could formulate a specific motivation, a specific aspect of what part of
GSM you are interested in, that could help you to gain some entry and ask
helpful questions.

Knowing C is a necessary prerequisite, I'd say it is prohibitively hard to
learn C *and* Osmocom code at the same time.

~N

Re: Osmocom Village at CCC Camp 2019

[Neels Hofmeyr]

ant to remind you, if you bring cooking equipment, there will be no 
> direct fresh water and waste water
> supply for your kitchen. We will have some central places with fresh water 
> supply and where you can wash
> your kitchen utensiles and dishes.
> 
> Power:
> Power will be generated from diesel with power generators. All engergy you'll 
> use will have to be
> generated. Think about our environment and use as little power as possible. 
> For that reason, there is no
> possibility to fulfill high power demands for pizza ovens, saunas and alike. 
> If you need cooling for your
> food supplies, please think about your refrigeration requirements. Less is 
> more. And please bring enough
> outdoor and rain proof extension cables to connect your tents and equipment.
> 
> Fire:
> Open wood or coal fire is not allowed at any time. That applies for anything 
> that needs heat for kitchen
> usage. If you need heat, please bring your own safe gas-based camping heaters.
> 
> Waste:
> Of course there will be containers for waste, paper and glass on the camp 
> site. But the camp tries to be
> as sustainable and ecological as possible. So please consider bringing 
> reusable dishes and cutlery. Also
> think about bringing a refillable water bottle for this is the more 
> ecological alternative to bottled
> water. The tap water is perfectly drinkable.
> 
> Wiki:
> There will be no automatic transfer of your data from the village 
> registration tool to the wiki. Please
> create your own Wiki page using the form at [5] 
> https://events.ccc.de/camp/2019/wiki/Form:Village if you
> want your village appear in the wiki. Please be aware that the only valid 
> place for village registration
> is [6] https://signup.c3assemblies.de/
> 
> Timeline:
> 14.8: Buildup: Only for angels who help with buildup and registered at the 
> orga- or angelsystem with their dates
> 16.8: People can start to build up their villages, no power or network yet
> 19.8: Power is probably(!) available from now
> 21.8: Offical start of the CCCamp19 \o/
> 25.8: Last day of the CCCamp19, start of disassembly in the evening
> 28.8: Last day of disassembly, all must be finished no later than this day. 
> If you stay 27th/28th, you are
> expected to help out!
> 
> Please see [7] https://events.ccc.de/camp/2019/wiki/Timeline for recent 
> updates.
> 
> [1] https://signup.c3assemblies.de/
> [2] https://tickets.events.ccc.de/camp2019hw/
> [3] https://signup.c3assemblies.de/
> [4] https://tickets.events.ccc.de/camp2019hw/
> [5] https://events.ccc.de/camp/2019/wiki/Form:Village
> [6] https://signup.c3assemblies.de/
> [7] https://events.ccc.de/camp/2019/wiki/Timeline
> 


-- 
- Neels Hofmeyr   http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte


signature.asc
Description: PGP signature

Re: osmocom-bb compilation problems

[Neels Hofmeyr]

On Thu, May 17, 2018 at 12:59:55AM +0300, Nikos Balkanas wrote:
> -> git push ssh://osmo/osmocom-bb.git

Admitted, the patch pushing instructions only matched the case where one added
a secondary 'gerrit' remote. So I tweaked the "Push for review" section:
https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit#Push-for-review

In another mail you posted an SSH access error. You have added your SSH public
key to your gerrit user as instructed on the wiki, right?

~N


signature.asc
Description: PGP signature

Re: osmocom-bb compilation problems

[Neels Hofmeyr]

On Wed, May 16, 2018 at 04:47:32AM +0300, Nikos Balkanas wrote:
> ​I think I got it working. I got this cryptic response:
> 
> -> git push ssh://osmo/osmocom-bb.git
> Everything up-to-date

That is definitely not how to push a patch for review to gerrit.

Look, you're the first to have trouble reading the wiki page on Gerrit
submissions, I believe the information there is quite clear. If it isn't, then
we should fix that. Let us know where we lose you.

If you still can't get it to work, please show us your ~/.ssh/config that you
apparently use, share the state your git clone is in and your complete
commandline and output that you use to push the patch.

> ​Anyway to check if changes committed?
> Cloning from gerrit will just give me ​the main osmocom-bb.git :(

You are merely allowed to push a patch for review. Cloning osmocom-bb.git will
only contain your patch if we approved and merged it. Usually that takes a
couple of review iterations on gerrit.osmocom.org first.

You have created a user on gerrit.osmocom.org?

~N


signature.asc
Description: PGP signature

Re: osmocom-bb compilation problems

[Neels Hofmeyr]

On Mon, May 14, 2018 at 09:38:42PM +0300, Nikos Balkanas wrote:
> On Mon, May 14, 2018 at 8:12 PM, Nikos Balkanas  wrote:
> 
> > Got it. I'm on it:)
> >
> 
> ​Tried to submit patch to gerrit:
> 
> -> git push git://gerrit.osmocom.org/osmocom-bb
> HEAD:refs/for/master/Minor_Typo_Fixes
> fatal: remote error: access denied or repository not exported: /osmocom-bb

Well, what can I say. Please carefully read the wiki page:
https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit
you will note the URL ssh://$usern...@gerrit.osmocom.org:29418/$PROJECT.git

~N


signature.asc
Description: PGP signature

Re: osmocom-bb compilation problems

[Neels Hofmeyr]

On Sun, May 13, 2018 at 09:28:57PM +0300, Nikos Balkanas wrote:
> The wiki is a non standard unix location, but a more convenient one. I
> propose to fix the info in README.building,
> to avoid future issues. The fix can be as simple as "Prerequisite is the
> armel toolchain. Check the  for installation"

Patches welcome!
osmocom-bb is managed at gerrit.osmocom.org, to post a patch see
https://osmocom.org/projects/cellular-infrastructure/wiki/Gerrit

~N



signature.asc
Description: PGP signature

Re: osmocom-bb installation help

[Neels Hofmeyr]

On Sat, May 12, 2018 at 09:42:16PM +0300, Nikos Balkanas wrote:
> Interesting, when I try:
> git clone https://git.osmocom.org/libosmocore
> gives me libosmocore 0.9.0.16
> git clone git://git.osmocom.org/libosmocore
> gives me the correct libosmocore 0.11.0.12.
> Seems your nginx server is caching the https request some 6 months now:)
> Problem solved:)

What, wow. I didn't know we even offered https git access there. All I ever use
is git://git.osmocom.org and git+ssh://gerrit.osmocom.org. There also is https
access on gerrit.osmocom.org (managed by gerrit).

https://osmocom.org/issues/3261

~N


signature.asc
Description: PGP signature

Re: MS driver: GSM tester config integration

[Neels Hofmeyr]

On Mon, Mar 05, 2018 at 11:28:49PM +, Holger Freyther wrote:
> Hey,
> 
> pespin left a good comment about the question of how the MS driver and the 
> GSM tester could be better integrated. I was about to write some argparse 
> code for the MS driver but I think it is best to make this configurable as a 
> scenario.
> 
> In terms of scenario knobs I can see:
> 
>  - #MS
>  - CDF function

what's CDF?

>  - IMSI generator (start with XXX and count upwards)

We have MSISDN and I think LAC generated on-the-fly, with state in the
file system. You could basically copy-paste that MSISDN generator code to
make an IMSI generator.

>  - virtphy vs. trxcon?

(no idea)


> The actual test would remain separate (and maybe turn it into a suite at some 
> point in the future). What do you think? What should I obey when 
> parsing/handling config?

The way I see it, you implement a "copy" of the mobile.py interface to,
instead of talking to ofono, talk to the virtphy/MS, whatever it's called.
(Like Pau said.)

Then either:

- We define a limited specific number of those virtual modems in the
  resources.conf to be available, and add a specific trait, as in a 'type:
  virtual' or something. You would then add a scenario that asks for the
  modems to be of 'type: virtual', and run the exact tests from the
  existing suites, just with virtual modems instead of physical ones.

- Or we could even auto-generate the entire virtual modem, sort of in the
  way that we start core net components at the moment, by calling a
  function from within the test case.  For example, the osmo-msc is not a
  resource handled in scenarios, we just ask for IP address resources and
  hand one to the osmo-msc startup.  Then there would be a separate
  *suite* with its conf not even asking for any modem resources, just its
  tests call a function that ask to setup virtual modems on-the-fly.  A
  drawback here is that you can't just re-run existing suites -- you can't
  just swap out the physical modem kind for a virtual one and run the
  exact same suite, you have to write different tests that launch virtual
  modems from the test case script.

It depends on: a) do you want to run the existing tests on the virtual
modems at all? b) how physical/resource-like vs.
software-component-running-like is a virtual modem?

For virtual modem being a resource, I'd add only separate scenario
definitions and possibly add tests to existing suites if that makes any
sense; for virtual modems started up like a software component, I'd add an
entirely separate suite even for the first test implemented (because then
that suite wouldn't ask for 'modem' resources to begin with).


BTW, in general, a virtphy issue could be the multicast. I saw stsp having
some trouble keeping the multicast from seeping out of all the interfaces.
We probably want the osmo-gsm-tester to contain that somehow.

~N


signature.asc
Description: PGP signature

Re: layer23/mobile: VTY is broken

[Neels Hofmeyr]

On Mon, Oct 23, 2017 at 12:43:52PM +0200, Harald Welte wrote:
> I think in general we should not fall into that trap.  We have *no clue* at 
> all
> who might be using libosmo* for whatever purpose.  If we provide a libary with
> a given API/ABI, then it's our responsibility to keep that ABI/API as stable 
> as
> possible.

True.

There are ways to fix this one: we can allow to register a given command a
second time, which then replaces the previously registered command. We can also
allow this only for the common node commands.

Should I implement this? Then upon new release, all potential VTY users out
there can still register their own common node commands to replace the default
ones and should not experience breakage.

~N


signature.asc
Description: Digital signature

Re: layer23/mobile: VTY is broken

[Neels Hofmeyr]

On Mon, Oct 23, 2017 at 12:42:25AM +0330, Vadim Yanitskiy wrote:
> At the moment there are the custom 'exit' and 'end'
> commands in the OsmocomBB/mobile/vty_interface.c.
> So, the crash happens because it attempts to install
> already existing commands.

Ah, damn. I checked all of the repositories I know to use the VTY, I didn't
imagine that OsmocomBB also has a VTY. That's really my fault then.

Lucky for me that the BB custom ones seem to merely dup the libosmocore stock
ones, so I get away with your patch:

> https://gerrit.osmocom.org/4373

> Also, I've fixed one more thing by the way:
> https://gerrit.osmocom.org/4374

well done.

Thanks for saving my A

~N


signature.asc
Description: Digital signature

Re: CalypsoBTS and modern OsmoBSC

[Neels Hofmeyr]

Please, again, no-one should *ever* send image bitmaps of text screenshots to a
mailing list!

~N



signature.asc
Description: Digital signature

Re: OsmocomBB full Opensouce?

[Neels Hofmeyr]

On Thu, May 04, 2017 at 11:35:23AM +0200, Harald Welte wrote:
> As OsmocomBB has moved to gerrit now (I believe?)

yes it has.

~N



signature.asc
Description: Digital signature

Re: osmocom-bb moved to gerrit

[Neels Hofmeyr]

On Wed, Apr 26, 2017 at 07:24:28AM +0700, Vadim Yanitskiy wrote:
> I can take this task and try to write a Jenkins script.

Excellent. Best put it in contrib/jenkins.sh like in the other repositories.

> Also, we need to have cross-compiler installed on the build machines.

I can install any packages, just let me know which.
(I assume we'd at first just build on a debian 8 slave)

~N



signature.asc
Description: Digital signature

Re: gerrit for osmocom-bb

[Neels Hofmeyr]

On Thu, Apr 20, 2017 at 10:18:57AM +0200, Neels Hofmeyr wrote:
> In the redmine admin, I see an "Autologin: disabled" item that can be set
> to 1, 7, 30 or 365 days. I'd switch that to 30 days if everyone agrees.

Actually, I set it to 30 days now. Please tell me if you disagree and I'll
set it back to "disabled".

~N


signature.asc
Description: Digital signature

Re: gerrit for osmocom-bb

[Neels Hofmeyr]

On Wed, Apr 19, 2017 at 09:01:30PM +0200, Sylvain Munaut wrote:
> Hi,
> 
> > One issue that I fear is that I see very little activity outside of the
> > sysmocom team in gerrit in terms of review.  I had the feeling this was
> > better while posting patches still on the mailing lists.  I'm not sure
> > there is a causality.
> 
> I'm not sure if it's just me or if I'm using it wrong but I'm always
> annoyed when I have to login to gerrit ...

I've gotten somewhat used to it but it's a bit of an eyebrow raiser every
time. The OpenID seems like it should be really useful, why else would it
have been invented, but practically for me it blows up the usual
click-on-login with the password remembered from my keystore to a
three-step process. I wish gerrit simply had a password. (It does, but
that seems to be unusuable for website logins, only for build bots?)

> 1) I shouldn't be logged out at all ... it's not a high security stuff
> that session should be kept open for a long time, like > 1 week
> without issues ...
> 2) I have to retype the openid login url. I mean there is a login with
> Yahoo and login with Launchpad Id dedicated link, isn't there a way to
> add, "login with your osmocom redmine account" link ?

My browser remembers the URL but I still need to type 'h' to trigger the
https... URL.

> 3) Then I'm redirected to redmine, where I have to login as well,
> because again for some reason I've been logged out. Same comment as
> above, unless I explicitely log out, that session should last for ever
> pretty much ...
> 4) When I then login to redmine, I get redirected to the OpenID end
> point but at this point the "open id state" or whatever has been lost
> and so I need to go back to gerrit and re-do the whole login process
> so it can do it in one go without being interrupted by the redmine
> login process and finally log me into gerrit ...

A way to shorten the process is to login on osmocom.org first, and only
then move on to gerrit -- annoying, I agree. I assume the redmine login
dialog loses gerrit's state.

> I can assure you I gave up on the whole process more than one time 

Gave up? :)
I pestered about it when we moved to gerrit, but it does work.
Admitted, sometimes the '500 Bad Gateway' needs a browser restart...

In summary, I agree the login is unusually cumbersome.

+1 for a "login via osmocom.org" link, not sure where to plug that though.

+1 for longer sessions, also not quite sure how configurable that is...

I think both redmine and gerrit remain logged in as long as the browser
keeps the login cookie?  I'm usually logged out only when I restart the
browser.

In the redmine admin, I see an "Autologin: disabled" item that can be set
to 1, 7, 30 or 365 days. I'd switch that to 30 days if everyone agrees.

Gerrit configuration is generally a bit unusual, so far I couldn't find a
way to configure login sessions.

~N



signature.asc
Description: Digital signature

Re: git.osmocom.org cgit improvements

[Neels Hofmeyr]

On Sun, Mar 19, 2017 at 09:57:57PM +0100, Holger Freyther wrote:
> > Holger, what's the status of your promise, made one day in a chat, to make
> > redmine catch the OS#123s?
> 
> lol, I love how we go from a private chat to this CC list.

Hey, if you love it that much, I can come up with plenty more private
conversations between us I could Cc around... ;)

In other words, sorry about disclosing. I kind of remembered it was a public
commitment. And it doesn't need to stick, either, anyone could take a look if
you're busy.

~N



signature.asc
Description: Digital signature

Re: git.osmocom.org cgit improvements

[Neels Hofmeyr]

On Fri, Mar 17, 2017 at 09:17:19PM +0100, Harald Welte wrote:
> 2) rendering of "about" page from README.md
> 
> As you might have noticed, I've introduced a README.md in a number of
> repositoires, and cgit is now rendering an about page for every
> repository, e.g. at http://git.osmocom.org/libosmo-abis/about/

It seems like these need some follow-ups in the debian packaging instructions
-- i.e. update to the new .md suffix or mark as installation (or ignore, but I
guess rather installation) file.

> 4) Osmocom ticket/issue hyperlink generation
> 
> Any Line that matches the "^((Relate|Close|Fixe)[ds]):" prefix is
> scanned for occurrences of "OS#(\d+)" which are then amended with
> hyperlinks to the respective issue on osmocom.org

Ah, so when OS#123 appears in the commit log's free text, it isn't linked?
Can we just scan everything for "\<OS#\d+\>"?

All in all these are excellent improvements!
Holger, what's the status of your promise, made one day in a chat, to make
redmine catch the OS#123s?

~N

-- 
- Neels Hofmeyr <nhofm...@sysmocom.de>  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte


signature.asc
Description: Digital signature

Re: Downtime due FreeBSD upgrade.

[Neels Hofmeyr]

Anytime is fine with me.

~N

On Fri, Feb 03, 2017 at 10:37:47AM +0800, Holger Freyther wrote:
> Even if it is short notice, any objections for Saturday->Sunday night
> of a European timezone? Otherwise I would pick next Friday->Saturday.


signature.asc
Description: Digital signature

Re: Calypso BTS

[Neels Hofmeyr]

On Mon, Dec 12, 2016 at 10:56:34AM +0100, Tomcsányi, Domonkos wrote:
> Did you create the hlr.sqlite3 file?

It should be created automatically. Given that the location is writable...  I'm
sure this is a minor detail related to the file system that the OP should be
able to figure out.

~N

-- 
- Neels Hofmeyr <nhofm...@sysmocom.de>  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte


signature.asc
Description: Digital signature

Re: OpenBTS the phone does not see

[Neels Hofmeyr]

You are on the wrong mailing list. OpenBTS is not part of Osmocom.
The naming can be confusing, the similarity of OpenBSC and OpenBTS came due to
historical reasons. https://osmocom.org/projects/osmobts/wiki/OpenBTS

~N

On Sun, Dec 11, 2016 at 01:52:52AM -0700, phreaker1983 wrote:
> Hi, I installed OpenBTS 5.0 for
> tutorials:https://www.youtube.com/watch?v=Ja7oSyyx7zw, everything went
> without error , after starting the phone doesn't see my base station, what
> could be the problem?
> 
> 
> 
> --
> View this message in context: 
> http://baseband-devel.722152.n3.nabble.com/OpenBTS-the-phone-does-not-see-tp4026754.html
> Sent from the baseband-devel mailing list archive at Nabble.com.

-- 
- Neels Hofmeyr <nhofm...@sysmocom.de>  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte


signature.asc
Description: Digital signature

Re: Calypso BTS

[Neels Hofmeyr]

On Sun, Dec 11, 2016 at 01:46:23AM -0700, phreaker1983 wrote:
> , then when you run : osmo-nitb -c ~/.osmocom/open-bsc.cfg-l
> ~/.osmocom/hlr.sqlite3-P-C --debug=DRLL:CC:MM:RR:RSL:NM shows me:<0005>
> bsc_init.c:498 Failed to parse the config file:

You probably just have a bug in your config file, or the config does not match
the openbsc version.  Typically this would also contain a more detailed error
message. To be able to help, we need more information like the complete error
output or the config file and openbsc version you are using.

~N


-- 
- Neels Hofmeyr <nhofm...@sysmocom.de>  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte


signature.asc
Description: Digital signature

Re: Redmine theme

[Neels Hofmeyr]

On Mon, Feb 29, 2016 at 10:17:43AM +0600, Вадим Яницкий wrote:
> I suggest to change a stock Redmine theme to something more beautiful,
> for example gitmike: https://github.com/makotokw/redmine-theme-gitmike

+0.5 for using a different theme. gitmike does look slick but IMHO tends
to have not enough contrast. And whether we want to look like github of
all things is a bikeshed, too ;)

~Neels



signature.asc
Description: Digital signature

Re: Moving from trac to a single redmine

[Neels Hofmeyr]

On Thu, Feb 18, 2016 at 07:52:55PM +0100, Holger Freyther wrote:
> last weekend I used the "stock" redmine trac->redmine converter and the 
> result is on projects.osmocom.org. It is not perfect but I think good enough 
> to start moving. We see that certain formating needs a post-import correction 
> but that should be doable by all of us quickly.

I swiftly registered a 'neels' account and as soon as it's granted project
memberships, I'd start off by making the overview png visible inline on
the OpenBSC wiki page (unless we can automate those somehow).

nitpick: I notice that in redmine, the project name "Openbsc" should
probably be capitalized ("OpenBSC")?

> * Saturday/Sunday do the migration of the trac.

was I too quick then? I'll recreate my account again if necessary.

> any objections?

no problem, since we're all idling around all the time anyway ;)
More seriously though, the wiki is on my todo list to explain gtphub and
adjust that overview png, also to include Iu. Some day not too far I hope...

~Neels


-- 
- Neels Hofmeyr <nhofm...@sysmocom.de>  http://www.sysmocom.de/
===
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Holger Freyther, Harald Welte


signature.asc
Description: Digital signature