OsmocomDECT: Linux 3.0 merged
I've merged the DECT tree with the Linux 3.0 release. P640j/Wideband support will also be pushed out soon
Added by almost 13 years ago
I've merged the DECT tree with the Linux 3.0 release. P640j/Wideband support will also be pushed out soon
Added by laforge almost 13 years ago
For quite some time we've been hacking away on a project called osmo-bts.
You can find it source code as usual on git.osmocom.org, for occasional web browsing we offer cgit access.
osmo-bts is a BTS-side Layer3 and Layer2 protocol implementation, including Abis/IP, TS 08.58 RSL, TS 12.21 OML, TS 04.06 LAPDm and various other bits and pieces required to run a BTS.
Specifcally, it does not include a GSM Um Layer1. Rather, the idea is to port osmo-bts to a variety of L1 implementations.
So far, hardware support only exists for an upcoming BTS product which is not available yet, the sysmocom femtobts. However, there is active work being done un hacking some OsmocomBB phones into using them as a BTS, as well as support for other L1/hardware, too.
We are also planning to implement a 'virtual layer1', that can be used to run a BTS without any radio layer, interfacing the OsmocomBB stack via TCP/IP for netwokr simulation and software testing.
Added by laforge almost 13 years ago
The German podcast Kuechenradio has released Episode 297: Hacker im Wald, covering OpenBSC founding member Dieter Spaar and his activities regarding GSM, UMTS and TETRA security research.
Added by laforge about 13 years ago
Today, a Chaosradio Express (CRE) about TETRA has been released at http://chaosradio.ccc.de/cre183.html
OsmocomTETRA founder Harald Welte was interviewed by Tim Pritlove, maker of the popular German language technology podcast Chaosradio Express.
The 2 hours and 20 minutes long interview covers the historic evolution from analog radio, trunked radio to digital trunked radion and TETRA. It also covers users, security issues and the OsmocomTETRA project.
Please note: CRE is a German language publication.
Added by about 13 years ago
I've merged with Linus' current tree, due to a newly assigned netlink family, the NETLINK_DECT value has changed. Both the libnl and libdect trees need to be updated as well and recompiled against the current set of kernel headers (specifically, using the current include/linux/netlink.h file).
Refer to the Build_instructions if in doubt.
Added by about 13 years ago
Thanks to laforge, the git problems should be fixed now. Apparently OpenVZ by default limits the amount of sockets per instance to 1% of the global limit. Git is forking wildly, creating lots of orphaned sockets until it hits the limit.
Added by about 13 years ago
Some people have reported problems when cloning the kernel tree, unfortunately these are so far unresolved. The kernel changes can alternatively be obtained in patch form from Patches.
Added by laforge about 13 years ago
We have recently started to analyze some old Motorola Dimetra equipment, the progress can be found at Dimetra_EBTS and the follow-up pages.
Any hints on how to configure/setup/use this hardware are appreciated, especailly regarding the Ethernet protocol between BR and TSC, as well as the E1 protocol from TSC to SwMI.
Added by laforge over 13 years ago
We haven't had a functioning commit log mailinglist since mid-2009, when the revision control system of openbsc was converted from svn to git.
Especially today, with the large number of separate git repositories on http://cgit.osmocom.org/, it is very easy to loose track of what other developers are doing.
The new mailing list 'osmocom-commitlog' (renamed from openbsc-commits) will receive updates from all repositories on git.osmocom.org.
Feel free to subscribe at http://lists.osmocom.org/mailman/listinfo/osmocom-commitlog
Added by laforge over 13 years ago
We're sorry to report that there are some problems with our git repositories at the moment, resulting in 'early EOF / index-pack failed' messages when users are attempting to clone one of our repositories.
The problem has been thoroughly analyzed, but even after many hours of analysis, no solution has been found yet. Your best chance is to keep re-trying the clone, in 5-10% of the cases it will succeed.
More technical details are available at this posting to the git mailing list:
http://article.gmane.org/gmane.comp.version-control.git/169909
Sorry for the inconvenience.
Also available in: Atom