hi holger,
it worked. thanx for your help. but now i got stuck here:
./configure in openbsc:
checking for LIBOSMOCORE... configure: error: Package requirements (libosmocore >= 0.1.6) were not met:
No package 'libosmocore' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables LIBOSMOCORE_CFLAGS
and LIBOSMOCORE_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
"pkg-config --list-all" does not show libosmocore. my directory: "dir /usr/local/lib/pkgconfig/" shows libosmocore.pc and spandsp.pc, nothing else. it seems that my version of pkg-config stores it somewhere else. my version is 0.23.
with that it works, but it should be easier, i think:
LIBOSMOCORE_LIBS=/usr/local/lib/ LIBOSMOCORE_CFLAGS=-I../libosmocore/include/ LIBOSMOVTY_LIBS=/usr/local/lib/ LIBOSMOVTY_CFLAGS=-I../libosmocore/include/ ./configure
now i get these errors when compiling openbsc:
gsm_04_11.c:343:16: error: invalid suffix "b111" on integer constant
...
the source sais "switch (fi & 0b111) {". i never saw binary values in C. (gcc version 4.1.2)
andreas
-----Ursprüngliche Nachricht-----
Von: openbsc-bounces(a)lists.gnumonks.org [mailto:openbsc-bounces@lists.gnumonks.org] Im Auftrag von Holger Hans Peter Freyther
Gesendet: Dienstag, 25. Mai 2010 16:06
An: openbsc(a)lists.gnumonks.org
Betreff: Re: AW: (problems compiling openbsc)
On 05/25/2010 09:49 PM, Andreas.Eversberg wrote:
> rm libtool
> autoreconf -f
--install
?
hi again,
here is the current compiler output. compile works, but linking fails:
gcc -Wall -I../../libosmocore/include/ -I../../libosmocore/include/ -g
-O2 ../../libosmocore/src/.libs/libosmocore.a -o bsc_hack bsc_hack.o
bsc_init.o
bsc_vty.o vty_interface_layer3.o libmsc.a libbsc.a libvty.a libmsc.a
-ldl -ldbi ../../libosmocore/src/vty/.libs/libosmovty.a -lcrypt
bsc_hack.o: In function `main':
/files/projects/isdn/openbsc/openbsc/src/bsc_hack.c:215: undefined
reference to `log_init'
/files/projects/isdn/openbsc/openbsc/src/bsc_hack.c:216: undefined
reference to `talloc_named_const'
/files/projects/isdn/openbsc/openbsc/src/bsc_hack.c:221: undefined
reference to `log_target_create_stderr'
/files/projects/isdn/openbsc/openbsc/src/bsc_hack.c:222: undefined
reference to `log_add_target'
/files/projects/isdn/openbsc/openbsc/src/bsc_hack.c:229: undefined
reference to `log_set_all_filter'
...
libosmocore.a has a reference to 'log_init', but the linker will not
find it somehow. any idea?
andreas
>> hi,
>>
>> while trying to bring latest api of openbsc and linux-call-router
>> together, i experienced the following problem:
>
>make a clean rebuild... your libtool seems hosed.
this does not work:
rm libtool
autoreconf -f
make
and i have the non-working libtool again.
hi,
while trying to bring latest api of openbsc and linux-call-router
together, i experienced the following problem:
make[2]: Entering directory
`/files/projects/isdn/openbsc/libosmocore/src'
/bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I.
-I.. -I../include -fPIC -Wall -g -O2 -MT timer.lo -MD -MP -MF
.deps/timer.Tpo -c -o timer.lo timer.c
../libtool: line 775: X--tag=CC: command not found
../libtool: line 808: libtool: ignoring unknown tag : command not found
../libtool: line 775: X--mode=compile: command not found
../libtool: line 925: *** Warning: inferring the mode of operation is
deprecated.: command not found
../libtool: line 926: *** Future versions of Libtool will require
--mode=MODE be specified.: command not found
../libtool: line 1069: Xgcc: command not found
../libtool: line 1069: X-DHAVE_CONFIG_H: command not found
../libtool: line 1069: X-I.: command not found
../libtool: line 1069: X-I..: command not found
../libtool: line 1069: X-I../include: No such file or directory
../libtool: line 1069: X-fPIC: command not found
../libtool: line 1069: X-Wall: command not found
../libtool: line 1069: X-g: command not found
../libtool: line 1069: X-O2: command not found
../libtool: line 1069: X-MT: command not found
../libtool: line 1069: Xtimer.lo: command not found
../libtool: line 1069: X-MD: command not found
../libtool: line 1069: X-MP: command not found
../libtool: line 1069: X-MF: command not found
../libtool: line 1069: X.deps/timer.Tpo: No such file or directory
../libtool: line 1069: X-c: command not found
../libtool: line 1120: Xtimer.lo: command not found
../libtool: line 1125: libtool: compile: cannot determine name of
library object from `': command not found
make[2]: *** [timer.lo] Error 1
make[2]: Leaving directory
`/files/projects/isdn/openbsc/libosmocore/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/files/projects/isdn/openbsc/libosmocore'
make: *** [all] Error 2
andreas
Hi!
This is just a notification that I've now created a mailing list related to
OpenGGSN development. As the entire OpenGGSN project is running on sf.net, the
mailinglist is also running there:
https://lists.sourceforge.net/lists/listinfo/ggsn-devel
So if you're interested in following what's happening in OpenGGSN, I suggest
you subscribe there, too. I understand it would probably make more sense
to simply move the entire project to osmocom.org and use this very openbsc
list (it is low-traffic, after all) - but we never know if the original
author wants to come back, and I'd be able to keep that door open for him
and thus the project separate and on sf.net.
I've also made a openggsn-0.90 release including various bugfixes that
were contributed trough the last 5 years, as well as one criticial security
fix. You can obtain it from:
http://sourceforge.net/projects/ggsn/
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi,
I have git clone the openbsc program and encountered problem running
osmo_sgsn,
got the following error messages:
"
There is no such command.
Error occurred during reading below line:
nsip local port 23000
Failed to parse the config file: 'osmo-sgsn.cfg'
<0014> sgsn_main.c : 170 Cannot parse config file.
"
Appreciate help on this.
Thanks
Ken
Hi all,
as you can see from the attachment, the OpenGGSN takeover request at
soruceforge has been resolved earlier than expected, since the original
project creator/administrator was not reachable for sf.net.
I'll keep you posetd about the further progress.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hello Harald,
On Wed, 19 May 2010 21:28:10 +0200, "Harald Welte" <laforge(a)gnumonks.org> wrote:
>
> So let's start with a poll:
>
> a) Do you think re-licensing to AGPLv3 is a good idea?
I don't have much experience in this area (different GPL versions), but
for me it sounds OK.
> b) If you have contributed, would you re-license your code under AGPLv3?
There is probably not that much from me, but feel free to put the affected
parts under AGPLv3.
Best regards,
Dieter
--
Dieter Spaar, Germany spaar(a)mirider.augusta.de
Hi all!
I think it's about time that we seriously think about how to handle naming
of the individual programs as well as the project itself.
OpenBSC was always a mis-nomer since what we started with is much more
than a BSC: It's an entire GSM network (excluding BTS) in one process.
This was mostly due to the fact that OpenGSM was way too generic and I
wasn't able to come up with a good name.
Meanwhile, we've started project Osmocom (Open Soruce mobile Communications),
where work is being done on the MS (phone) side of GSM. The idea was to have
a name generic enough for sub-projects. There are currently two such projects:
* OsmocomBB - the BaseBand firmware
* libosmocore - the shared library with utilities that are used accross programs
In OpenBSC, we currently have the following executables:
* bsc_hack - the gsm network-in-a-box
* bsc_msc_ip - the actual BSC-only version talking to a real MSC
* bsc_nat - the A interface NAT
* bsc_mgcp - the media control gateway
* osmo-gbproxy - the Gb interface proxy
* osmo-sgsn - the soon-to-be-working SGSN
as well as a number of utilities like bs11-config, ipaccess-find,
ipaccess-config, etc.
What Zecke and me have decided some time ago is to move everything under the
umbrella of the Osmocom project name. This menans that the homepage and git
repositories will move to openbsc.osmocom.org/bsc.osmocom.org and git.osmocom.org
(while keeping aliases/redirects in place).
What worries me most is the naming of bsc_hack and bsc_msc_ip.
I think bsc_msc_ip should be called osmo-bsc, as it is a true BSC
implementation.
For bsc_hack it's much harder. A logical name would be osmo-gnib (gsm network
in a box), but as I've already received tons of complaints about osmocom, I'm
not going to come up with even stranger acronyms. However, I want to rename
it. It should be prefixed with "osmo-" and the name should not erroneously
indicate that we're talking abuot something thats _only_ a BSC.
Does anyone on this list have an idea for a good name?
For all the other programs, I'd also advocate prefixing them with "osmo-",
but that's less of a pressing concern right now.
Regards,
Harald
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Hi all!
Thanks to the support from On-waves, I've been able to focus on my GPRS
work during recent weeks.
Today, I have managed to actually perform successful PDP context activation /
deactivation using a nanoBTS, OpenBSC, OsmoSGSN and OpenGGSN.
This is a big step forward, as it means that the GTP interface between
our SGSN and OpenGGSN is up and running. The IP addresses allocated
are from a pool defined on the GGSN side, and OpenGGSN opens a tun-device
for it.
Also, the GGSN implementation is much less proof-of-concept now, as it actually
maintains propper MM context, PDP context and other state information.
However, for reasons that I couldn't figure out (despite many hours of
debugging): There are no user/data plane packets anymore. This was already
working before I began the GTP / OpenGGSN intergration work 1-2 weeks ago.
The PDP context is established successfully on the LLC-GMM SAPI, the phone
shows that GPRS is up, but then it doesn't actually even send a single
packet (SNDCP, XID exchange, ...) over any of the user data SAPIs. The
SAPI and NSAPI have been assigned properly, and I could not find any differece
looking at packet traces for both the cases.
If you look at the NS-IP / Gb interface of the nanoBTS, not a single gprs
protocol message arrives after the PDP context is activated.
After a minute or two, the phone then simply disconnects with "Regular
Disconnect" cause, as if nothing had happened. Putting the phone in front of
an audio amplifier also doesn't reveal any noticable bursts being generated
by the phone.
For now I'm feeling a bit lost and will work on some other stuff before
returning with renewed energy to the SGSN at some later point.
In case you want to try it, the following steps are needed:
1) check out OpenGGSN from git://openbsc.gnumonks.org/openggsn.git (master
branch), run the usual autoreconf -1 && ./configure && make install
2) check out current OpenBSC master branch and build it. Only if libgtp
(installed by OpenGGSN) is found, it will build src/gprs/osmo-sgsn
3) the IP address where
4) Run OpenBSC like usual, however make sure that the followign settings
are configured in the openbsc.cfg config file:
gprs mode gprs
gprs routing area 0
gprs cell bvci 2
gprs nsei 101
gprs nsvc 0 nsvci 101
gprs nsvc 0 local udp port 23000
gprs nsvc 0 remote udp port 23000
gprs nsvc 0 remote ip 123.192.152.236
Where the last ip address is the address of the machine where you will
run OsmoSGSN.
5) Configure /etc/ggsn.cfg of your GGSN machine. Check /etc/ggsn.conf
(example attached) Run
$ sudo ./ggsn -l 192.168.100.239 -d
where that address is the local _listening_ address of the GGSN
6) Then simply fire up osmo-sgsn. The only relevant config
setting in osmo_sgsn.cfg is:
sgsn
nsip local port 23000
7) start your favorite mobile phone and register it to your network
You can telnet to osmo-sgsn on port 4245, and type the followign commands
for some interesting information:
logging enable
logging filter all 1
logging level ns info
logging level bssgp debug
logging level llc debug
logging level gprs debug
logging level mm debug
show ns
show bssgp
show llc
show mm-context all
show pdp-context all
Oh, and last, but not least: Wireshark can debug the Gb interface packets
between BTS and SGSN, you simply have to select 'Decode as .... NSIP' on port
23000 packets. It also decodes the GTP between SGSN and GGSN without any extra
setting.
Have fun!
--
- Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
