- linux-dect - lists.osmocom.org

libnl compile error: "usr/bin/ld: cannot find -lnl-route"

by komkon555

Hallo. So I experienced an issue with libnl-compilation. The error is: make[2]: Entering directory `/usr/src/libnl/src' CCLD nl-pktloc-lookup /usr/bin/ld: cannot find -lnl-route collect2: error: ld returned 1 exit status make[2]: *** [nl-pktloc-lookup] Error 1 make[2]: Leaving directory `/usr/src/libnl/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/libnl/src' make: *** [all-recursive] Error 1 The compilation is tried on Debian Wheezy. The osmocom-linux-kernel/headers (kernel:git://dect.osmocom.org/git/linux-2.6.git) are successfully compiled and installed as in manual. I have tried also all native libnl debian-packages with source. Unfortunately they are not suitable for libdect. Please help. Best regards.

6 years, 10 months

1
1
0 0

Dect Kernel Stack for Kernel 4.9

by Newsy Paper

Hi! I tried to port the kernel stack provided by Patrick McHardy to Kernel 4.9 It is compiling for me and the module also loads, however I'm unable to getthe netlink device working. So there is still no way to get the dectmon working again using a modern linux kernel :( Anyone able to help? I put my patch here: https://paste2.org/F9CImF8x kind regards Newspaperman

7 years, 1 month

1
0
0 0

osmocom dect PP-mode

by Pavel Nakonechny

Hello, I am currently playing with Osmocom DECT software stack using COM-ON-AIR PCI card. What I am trying to achieve is to configure test PC as portable part and connect it to DECT base station. I have cloned and successfully compiled the following repos: git://dect.osmocom.org/linux-2.6.git git://dect.osmocom.org/libnl.git git://dect.osmocom.org/libdect.git Following instructions on dect.osmocom.org/wiki/Configuration page I configured PP. However, the example app dect-llme-scan was able to work only after uncommenting line: //nl_dect_llme_mac_info_set_pari(lmsg, pari); With the line above uncommented, dect-llme-scan returns the list of available base stations. So I assume, that hardware and most part of software works. Then I tried to use example pp-access-rights to connect to the test base station. This app fails immediately after launch for the same reason as dect-llme-scan. Thus, I have added nl_dect_llme_mac_info_set_pari(lmsg, pari); with empty PARI to dect_netlink_mac_me_info_req(struct dect_handle *dh) function. With this modification, the example moves farther, but fails anyway with "No such file or directory" message on this line: if (connect(ddl->dfd->fd, (struct sockaddr *)&ddl->dlei, sizeof(ddl->dlei)) < 0 && errno != EAGAIN) goto err3; in file lce.c All in all. May I at first ask about how to properly configure portable part? Here I have to specify EMC and FPN of the base station? # dect-cluster-add --name cluster0 --mode fp --emc 0x1182 --fpn 0x0fac3 # dect-cell-add --name cell0 --cluster cluster0 # dect-transceiver-bind --transceiver trx0 --cell cell0 What should I use here as IPUI? Some random identifier of my PP? # pp-access-rights --cluster cluster0 --pin 0000 --ipui 0x11830fac4 And, in general, are the sources in repos I listed previously were tested in PP mode or they are not fully functional yet? Thanks in advance. :) -- WBR, Pavel

7 years, 11 months

1
1
0 0

OsmocomDECT for Fritzbox router

by Thomas Schmiedl

Hello, would it be possible to use OsmocomDECT with the Fritzbox router? I try to extend my router Fritzbox 7312 with an application called "Callmonitor" (http://freetz.org/wiki/packages/callmonitor; sorry german only), which has a reverse-search (via internet-telephone-books) to query the name of the caller (query by caller's phone number). I want to transfer this name to my DECT cordless phone. Unfortunately, the manufacturer of the router, AVM in Berlin, does not provide any information about DECT (closed-source). Or could someone help me tracing the software dect_manager (http://www.wehavemorefun.de/fritzbox/Dect_manager) or libdect (http://www.wehavemorefun.de/fritzbox/Libdect.so), because I am not a developer. Best regards, Thomas

9 years, 1 month

1
0
0 0

OsmocomDECT for Fritzbox router

by Thomas Schmiedl

Hello, would it be possible to use OsmocomDECT with the Fritzbox router? I try to extend my router Fritzbox 7312 with an application called "Callmonitor" (http://freetz.org/wiki/packages/callmonitor; sorry german only), which has a reverse-search (via internet-telephone-books) to query the name of the caller (query by caller's phone number). I want to transfer this name to my DECT cordless phone. Unfortunately, the manufacturer of the router, AVM in Berlin, does not provide any information about DECT (closed-source). Thanks for the reply. Best regards, Thomas

9 years, 1 month

1
0
0 0

Announcing OsmoDevCon 2015

by Harald Welte

Dear Osmocom.org project members, I'm happy to be able to announce the annual incarnation of OsmoDevCon. The Date is set for March 27 through 30. Venue: As usual, IN-Berlin e.V. in Berlin, Germany. Further details can be obtained from http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2015 Attendance, as usual, is restricted to people with an active history in the Project by contributions in terms of code, patches, discussions, documentation or in other form. = Registration = If you have wiki access, please add yourself to the #Requested section. Alternatively, you can send me private e-mail about it. After review, your (nick)name will be listed in the #Confirmed section. Looking forward to meeting all of you again soon! -- - 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)

9 years, 2 months

1
0
0 0

DECT MitM Attack

by Tobias XY

Hello, how can i start a "Man in the middle attack", to decrypt encrypted phone calls of the DECT standard? I read something about it on the internet. Here, however, I lack the software and I do not know what hardware do I need to do so. The normal DECT Sniff attack I have already stated. However, one can hereby decode only unencrypted packets. Anyone have an idea? Greetings. Tobi

9 years, 3 months

1
0
0 0

error trying to make module under kernel 3.11.7 / gcc-4.7.3

by Atom2

Hi List, I am trying to compile the kernel driver module for 3.11.7 (gentoo hardened sources) using gcc-4.7.3. The card I am planning to use is a Dosch&Amnand Com-On-Air PCI. So far I have been able to change the patch file provided for the 3.0 kernels (http://dect.osmocom.org/attachment/wiki/Patches/linux-3.0.diff) to apply to my kernel sources. There were a few changes required, but nothing too drastic. However, when I start the 'make' for the kernel the compiler issues an error as follows: [... snip ...] CC kernel/module.o In file included from include/net/dect/mac_ccf.h:12:0, from include/net/dect/dect.h:148, from drivers/dect/coa/sc1442x.c:19: include/net/dect/mac.h:622:8: error: duplicate member ‘lbn’ include/net/dect/mac.h:624:9: error: duplicate member ‘pmid’ CC arch/x86/pci/bus_numa.o CC fs/ext4/super.o CC arch/x86/pci/amd_bus.o make[3]: *** [drivers/dect/coa/sc1442x.o] Error 1 make[2]: *** [drivers/dect/coa] Error 2 make[1]: *** [drivers/dect] Error 2 make: *** [drivers] Error 2 make: *** Waiting for unfinished jobs.... CC arch/x86/power/cpu.o [... snip ...] Given that the related code within include/net/dect/mac.h looks as follows (comments added by me), this seems to be a valid complaint of the compiler: [... snip ...] struct dect_cctrl { enum dect_cctrl_cmds cmd; union { struct { u16 fmid; u32 pmid; /* <=== pmid */ }; struct { u8 lbn; /* <=== lbn */ u8 ecn; u8 type; u8 service; u8 slot; bool cf; u8 a_mod; u8 bz_mod; u8 bz_ext_mod; u8 acr; }; struct { u8 lbn; /* <=== lbn */ u8 reason; u32 pmid; /* <=== pmid */ }; }; }; [... snip ...] lbn and pmid are indeed defined twice. A research on the internet for similar errors suggested that those constructs were tolerated (I don't know how) by gcc versions prior to 4.5, but are no longer valid. Is there any patch available or a suggestion on what I need to change in order to successfully compile the driver. Many thanks and regards, KK

10 years, 1 month

1
0
0 0

dect.osmocom.org back up

by Patrick McHardy

Just FYI: thanks to Holger dect.osmocom.org is back up again (and hopefully will stay up). I might merge the code with the 3.13 kernel during the next days.

10 years, 1 month

1
0
0 0

[RFC] [ADMIN] Making lists subscriber-only?

by Harald Welte

Dear all, so far the osmocom.org mailing lists have always been in a 'non-members are manually moderated' mode. This has created a lot of work for manual list moderation, where a lot of the messages caught are simply spam, and only the occasional valid message is being received. I'd like to thank the list moderators for taking care of this. However, in more recent discussions, we were considering to move the lists to a completely closed mode, i.e. postings would automatically be rejected from non-members. The automatic response would contain a description of how to subscribe in 'nomail' mode, i.e. to subscribe in a way to be able to post to the list, while still not receiving any incoming traffic. The latter should be fine for occasional posters who don't want the bulk e-mail that goes with a full/regular subscription. Please provide feedback in case you disagree with that change. Unless there is major opposition, we will likely transition to the 'closed' mode within one month. Thanks, 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)

10 years, 3 months

1
0
0 0

Osmo/DECT unreachable

by mario phoenix

http://dect.osmocom.org/ Any clue ? Mario

10 years, 6 months

3
2
0 0

Buy COM-ON-AIR PCMCIA Type 2

by Blago Blagoev

Buy COM-ON-AIR PCMCIA Type 2. Suggestions are welcome to e-mail.

10 years, 7 months

1
0
0 0

Compile of libdect fails

by Stephan Meier

Hi, sorry to be a bit of a nag, but libdect fails, too. The configure script fails while trying to find libnl. The fix is to replace "nl" with "nl-3" in configure.ac:36 (the first param of the AC_CHECK_LIB macro). Cheers, Stephan

10 years, 9 months

2
1
0 0

Compile of libnl failed

by Stephan Meier

Hi, after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried to compile it. It breaks while trying to compile the "nl-pktloc-lookup" binary. It seems to be caused by line 131 in src/Makefile.am (LDADD statement that overwrites the linker flags set before). Removing this line and thus using the "old" linker flags works. Is this the desired behavior or did anybody just forget to delete this line? Cheers, Stephan

10 years, 9 months

4
12
0 0

New version of libnl

by C470IP

Hello! Has anyone succeeded in compiling the latest version of libnl? After executing 'sh autogen.sh' it takes quite a while, then the following messages appear: Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 (yes they are double). Am I doing something wrong? Or maybe there are some new installation instructions regarding the latest version of OsmocomDECT software? With best regards, C470IP. E-mail: c470ip(a)yandex.ru

10 years, 10 months

1
0
0 0

Linux 3.8 merged but some wishes...

by Blago Blagoev

Hi! Good news http://dect.osmocom.org/trac/dect/blog/kaber-2013/03/31/linux_38_merged But: Asterisk wideband support is still unfinished. Asterisk do not work in PP-mode. How about working to bring to the state? It seems these problems are much more interesting and important. Anyone agree with me?

11 years

4
5
0 0

[ANNOUNCE] OsmoDevCon 2013-04-04 till 2013-04-07, Berlin

by Harald Welte

Dear fellow Osmcoom developers, it is my pleasure to finally announce the date + venue of OsmoDevCon 2013: Date: April 04 through April 07, 2013 Place: IN-Berlin, Lehrter Str. 53, Berlin Like last year, this is an event for developers of the various Osmocom proejects. Reservation and confirmation of reservation is required. The event is free of charge. The Room is made available by IN-Berlin e.V., an Internet related non-profit organization. Lunch catering will be sponsored (so far by sysmocom GmbH, but if any other sponsors come up, we are happy to share the cost). So all you have to cover is your own travel + accomodation costs, as well as breakfast and dinner. If you are an active developer and cannot afford travel/accomodation, please let me know and I'll see if we can do something about it. If you would like to attend, please send a message to laforge(a)gnumonks.org applying for registration of the event. The registration deadline is March 5, i.e. one week from now. There is no detailed schedule of talks yet. I will start a separate discussion suggesting / collecting topics in the next couple of days. More information is (and will be made) available at http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2013 Further discussion regarding the event should be directed at the osmocom-event-orga(a)lists.osmocom.org mailing list, to avoid cross-posting over the various project-specific lists. Best regards and happy hacking, 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)

11 years, 1 month

1
0
0 0

Unable to load module chan_dect.so in Asterisk

by Blago Blagoev

Hi! I do all instructions of http://dect.osmocom.org/trac/dect/wiki/Build%20instructions#kernel with last versions kernel, libnl, libdect, dectmon. When finish all configurations I got a dect-stack of hard-working But chan_dect.so module asterisk would not load correctly. Here http://dect.osmocom.org/trac/dect/blog/kaber-2011/11/04/linux_31_merged I read that the module is still not should work for P640j (Wideband) So I went back to version kernel 2.6.39-DECT and older versions of the libnl and libdect. As far as I understand, these versions do not support P640j (Wideband) and an asterisk to them should work fine? I have successfully created DECT cluster, cell, transceiver on the old-version soft: root@debian:~/dect/old/work# ./dect-cluster-list 1: DECT Cluster cluster0: Mode: FP PARI: class A (residential) EMC: 045d FPN: 00d1c root@debian:~/dect/old/work# ./dect-cell-list 1: DECT Cell cell0@cluster0: root@debian:~/dect/old/work# ./dect-transceiver-list DECT Transceiver trx0@cell0: Type: sc1442x RF-band: 00008 Events: busy: 0 late: 0 root@debian:~/dect/old/work# When I start the daemon Asterix in debug mode i can see the next: root@debian:/var/log/asterisk# asterisk -vvvc . .. . == Registered channel type 'DECT' (Digital Enhanced Cordless Telecommunications (DECT)) == Registered application 'DectUserAuth' == Parsing '/etc/asterisk/dect.conf': == Found -- Registered extension context 'dect_register'; registrar: DECT dect_netlink_init: Protocol mismatch [Nov 1 13:55:45] ERROR[1734]: chan_dect.c:2336 dect_load_module: Unable to initialize DECT handle == Unregistered channel type 'DECT' Who can help?

11 years, 5 months

1
0
0 0

Unable to load module chan_dect in Asterisk

by Blago Blagoev

Hi! I do all instructions of http://dect.osmocom.org/trac/dect/wiki/Build%20instructions#kernel with last versions kernel, libnl, libdect, dectmon. When finish all configurations I got a dect-stack of hard-working But chan_dect.so module asterisk would not load correctly. Here http://dect.osmocom.org/trac/dect/blog/kaber-2011/11/04/linux_31_merged I read that the module is still not should work for P640j (Wideband) So I went back to version kernel 2.6.39-DECT and older versions of the libnl and libdect. As far as I understand, these versions do not support P640j (Wideband) and an asterisk to them should work fine? I have successfully created DECT cluster, cell, transceiver on the old-version soft: root@debian:~/dect/old/work# ./dect-cluster-list 1: DECT Cluster cluster0: Mode: FP PARI: class A (residential) EMC: 045d FPN: 00d1c root@debian:~/dect/old/work# ./dect-cell-list 1: DECT Cell cell0@cluster0: root@debian:~/dect/old/work# ./dect-transceiver-list DECT Transceiver trx0@cell0: Type: sc1442x RF-band: 00008 Events: busy: 0 late: 0 root@debian:~/dect/old/work# When I start the daemon Asterix in debug mode i can see the next: root@debian:/var/log/asterisk# asterisk -vvvc . .. . == Registered channel type 'DECT' (Digital Enhanced Cordless Telecommunications (DECT)) == Registered application 'DectUserAuth' == Parsing '/etc/asterisk/dect.conf': == Found -- Registered extension context 'dect_register'; registrar: DECT dect_netlink_init: Protocol mismatch [Nov 1 13:55:45] ERROR[1734]: chan_dect.c:2336 dect_load_module: Unable to initialize DECT handle == Unregistered channel type 'DECT' Who can help?

11 years, 5 months

1
0
0 0

Re: DECT + GNU Radio?

by Patrick McHardy

Patrick McHardy <kaber(a)trash.net> schrieb: > > >Joel Mayer <joelm_armillary(a)msn.com> schrieb: > >>Dear Mister Patrick McHardy- >> >>Here is a link to the EZTV 668 dongle. I have an EZTV 666 dongle >>working in windows >>(Ubuntu is in the near future on my lap top). I cannot vouch for the >>668 dongle in >>any personal way, but I have read comments in the various forums >>testifying to >>the utility of the 668. >> >>http://www.nooelec.com/store/software-defined-radio/eztv668-dvb-t-usb-set-f…<http://www.nooelec.com/store/software-defined-radio/eztv668-dvb-t-usb-set-f…> >> >>The install script I mentioned beneath these lines only works in >>Windows. To install >>the GNU radio software in Ubuntu you need to use a script written by a >>certain Mister >>Marcus Leech (he is a radio astronomer). See: >> >>http://gnuradio.org/redmine/projects/gnuradio/wiki/InstallingGR<http://gnuradio.org/redmine/projects/gnuradio/wiki/InstallingGR> >> >>Make certain you use Mister Leech's script! The GNU radio people have >>pulled >>their packages out of the repositories. The only way to get a fresh >new >>GNU >>radio is from the GNU radio people! >> >>My suggestion is, you install the SDR# radio in windows using the >>script I mentioned >>at the bottom of this note. Then install the SDR# scanner radio built >>by k5dev >>(below). Here is a link to a useful quick start guide for windows: >>http://www.atouk.com/SDRSharpQuickStart.html<http://www.atouk.com/SDRSharpQuickStart.html> >> >>To install the SDR# radio in Ubuntu on top of your GNU radio go here: >>http://rtlsdr.org/<http://rtlsdr.org/> Scroll down to the bottom of >the >>first page and visit: >>http://rtlsdr.org/softwarelinux<http://rtlsdr.org/softwarelinux> >> >>I'm going to journey to my pay pal account and try to send forty >>dollars to you at "kaber" at "trash dot net" without the quotes. >> >>Have A Nice Day! > >Thanks a lot, didn't expect that :-) I'll order one of these devices >and will give it a shot. Dropped CC, sorry.

11 years, 5 months

3
3
0 0

Trying to fill some gaps in documentation

by C470IP

Hello! Recently I've managed to install all Osmocom-DECT components (except Asterisk, which will be installed later). Everything seem to be working fine, at least I could try examples from the website without any error. Many thanks to the authors for this extraordinary job. Now I want to go further and to configure some useful system using these tools, but I feel some gaps in documentation/description which need to be clarified. I would be very thankful to anybody who would bother to answer the following questions: 1) When a DECT cluster is configured in FP mode (like first example here: http://dect.osmocom.org/trac/dect/wiki/Configuration ), how can we use it to attach handsets? Or for what this mode is for? Also I've found that in this mode beacon frames are sent very seldom and with minimal power, is this normal? 2) Where one can find the list of keywords for dectmon command line? Or if not keywords, what is dectmon awaiting after its > character? 3) In which program can we open raw dump files created by dectmon? Is it possible to dump pcap from dectmon? 4) How can we extract audio from the monitored stream? For example I created a cluster in PP mode locked to my unencrypted phone, then created a cell and bound the transceiver, then ran dectmon with '-a yes' keys. No success at all. 5) Is it possible to extract audio from raw dumps of dectmon with some ready-to use software? 6) BTW does dectmon support seamless channel hopping to make smooth audio streams without noise interrupts like those happening in dect_cli software? Would be grateful for any response. With best regards, C470IP. E-mail: c470ip(a)yandex.ru

11 years, 5 months

2
1
0 0

Unable to load module chan_dect in Asterisk

by Blago Blagoev

*Hi!** Asterisk got a problem with load the chan_dect module.** in my /var/log/asterisk/messages i see: [Oct 22 17:17:52] WARNING[1049] loader.c: Error loading module 'chan_dect.so': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get [Oct 22 17:17:52] WARNING[1049] loader.c: Module 'chan_dect.so' could not be loaded. * Who can recommend? **

11 years, 6 months

1
0
0 0

Cannot make libnl

by C470IP

Hello! While compiling libnl I get the following errors: route/cls/ematch_grammar.c:773:5: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:816:1: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:818:23: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:931:17: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:954:1: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:2433:1: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:2439:23: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:1766:26: warning: 'yy_get_previous_state' defined but not used [-Wunused-function] route/cls/ematch_grammar.c:1799:26: warning: 'yy_try_NUL_trans' defined but not used [-Wunused-function] route/cls/ematch_grammar.c:1631:12: warning: 'yy_get_next_buffer' defined but not used [-Wunused-function] make[2]: *** [route/cls/ematch_grammar.lo] Error 1 make[2]: Exiting `/libnl/lib' make[1]: *** [all] Error 2 make[1]: Exiting `/libnl/lib' make: *** [all-recursive] Error 1 I've tried bison 2.2, 2.3 and 2.6.2 with no success. Byacc and flex are also installed. Is it possible to fix these errors somehow? Unfortunately my knowledge of source syntax is not sufficient. With best regards, C470IP.

11 years, 6 months

1
0
0 0

How to use the audio-option in dektmon?

by Blago Blagoev

Hi! Computer with dektmon must have a sound card and installed drivers for it? When i run dectmon with option "audio" and loke to the FP, (which is a conversation) I need to hear the sound on the computer on-line? Is it possible to record the sound in a file?

11 years, 6 months

1
0
0 0

Anyone using dect in production?

by henrik hansen

Hey folks, Is anyone out there who is using xom-on-air cards in productional environment? Von meinem iPhone gesendet

11 years, 7 months

2
1
0 0

DECT + GNU Radio?

by Joel Mayer

Dear Fans of DECT- What about the GNU Radio Project? Is anyone working on a version of DECT as an element of, say the SDR# radio? How about the SDR# scanner radio? (1) http://sdrsharp.com/<http://sdrsharp.com/> (2) http://www.k5dev.com/<http://www.k5dev.com/> If you want to try this flavor of radio all you need is a suitable USB Dongle. For easy install with a script use: http://rtlsdr.org/softwarewindows<http://rtlsdr.org/softwarewindows> (The Automated method mentioned at the top of the page, specifically sdr-install.zip) Have A Nice Day! ----- Original Message ----- From: linux-dect-request(a)lists.osmocom.org<mailto:linux-dect-request@lists.osmocom.org> To: linux-dect(a)lists.osmocom.org<mailto:linux-dect@lists.osmocom.org> Sent: Friday, September 21, 2012 5:00 AM Subject: linux-dect Digest, Vol 40, Issue 1 Send linux-dect mailing list submissions to linux-dect(a)lists.osmocom.org<mailto:linux-dect@lists.osmocom.org> To subscribe or unsubscribe via the World Wide Web, visit https://lists.osmocom.org/mailman/listinfo/linux-dect<https://lists.osmocom.org/mailman/listinfo/linux-dect> or, via email, send a message with subject or body 'help' to linux-dect-request(a)lists.osmocom.org<mailto:linux-dect-request@lists.osmocom.org> You can reach the person managing the list at linux-dect-owner(a)lists.osmocom.org<mailto:linux-dect-owner@lists.osmocom.org> When replying, please edit your Subject line so it is more specific than "Re: Contents of linux-dect digest..."

11 years, 7 months

2
1
0 0

Problems building libdect

by Blago Blagoev

Hi I have Problem: When I try to Build libdect: root@debian:~/dect/libdect# ~~~~~~~~~~ bash: ~~~~~~~~~~: command not found root@debian:~/dect/libdect# ./configure checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a thread-safe mkdir -p... /bin/mkdir -p checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed configure: Documentation build disabled checking for nl_socket_alloc in -lnl... yes checking for nl_dect_cluster_alloc in -lnl-dect... yes checking for event_init in -lev... yes checking for bfd_init in -lbfd... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether to enable assertions... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for inttypes.h... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdint.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking for linux/dect.h... yes checking for linux/dect_netlink.h... yes checking event.h usability... yes checking event.h presence... yes checking for event.h... yes checking bfd.h usability... yes checking bfd.h presence... yes checking for bfd.h... yes checking checking whether event.h is compatible with libev... configure: error: incompatible event.h header for libev root@debian:~/dect/libdect#

11 years, 7 months

2
3
0 0

"incompatible event.h header" message when configure libdect

by Blago Blagoev

Good day! When i run the configure script from libdect, i obtain the following. error: configure: error: incompatible event.h header for libev installed: libev 4.11-1 libevent 2.0.20-1 on last version ArchLinux Also tested library libevent 2.0.19 and libevent 2.0.10 and OpenSUSE 12.1 But the error still remains :( Who can recommend?

11 years, 7 months

1
0
0 0

US DECT 6.0

by Frédéric LECAILLE

Hello Patrick, I had a look at the net/dect/mac_csf.c file source code. dect_bc_si_cycle_complete() often returns false with "incomplete: SSI" kernel logs: Aug 15 15:33:25 amanda kernel: [18609.133852] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.143816] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.153819] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.163822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.173820] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.183821] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.193820] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.203820] page: RFPI: d7ce8 bearer description: bt: 50000000 sn: 2 sp: 0 cn: 23 Aug 15 15:33:26 amanda kernel: [18609.213817] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.233819] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.243822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.253821] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.263822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.273818] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.283820] extended fixed part capabilities: fpc: 01000 hlc: 000000 Aug 15 15:33:26 amanda kernel: [18609.283826] incomplete: SSI Aug 15 15:33:26 amanda kernel: [18609.293831] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.303818] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.323822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.333823] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.343819] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.353817] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.363819] page: RFPI: d7ce8 blind full slots: 8aa Aug 15 15:33:26 amanda kernel: [18609.373820] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.383816] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.393842] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.403823] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.413822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.433816] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.443818] multi-frame number: 4282678 Aug 15 15:33:26 amanda kernel: [18609.443825] incomplete: SSI As far as I understand the code, in this case, the driver never locks, this would be the reason why dectmon never displays any message… The driver never logs any DBC message. This was the case before patching for US DECT. It seems there are EU DECT stations where I am testing this driver. [ 1112.263021] DBC slot 4 carrier 8: quality control: confirm quality [ 1112.267631] DBC slot 4 carrier 8: RSSI: selection: 60 now: 64 [ 1112.272821] DBC slot 4 carrier 8: quality control: wait [ 1112.272884] TX 17.00.04: FT T-MUX: N-channel [ 1112.272890] TX 17.00.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 2 [ 1112.283008] RX 17.00.16: trx0: Q1: 0 Q2: 0 A/B: 2a carrier: 2 A-CRC: 0 X-CRC: 0 Z-CRC: 0 TX 17.01.04: FT T-MUX: N-channel [ 1112.283017] TX 17.01.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 3 [ 1112.292781] TX 17.02.04: FT T-MUX: N-channel [ 1112.292786] TX 17.02.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 4 [ 1112.302781] TX 17.03.04: FT T-MUX: N-channel [ 1112.302785] TX 17.03.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 5 [ 1112.312813] TX 17.04.04: FT T-MUX: N-channel [ 1112.312817] TX 17.04.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 6 [ 1112.322783] TX 17.05.04: FT T-MUX: N-channel [ 1112.322789] TX 17.05.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 7 [ 1112.332781] TX 17.06.04: FT T-MUX: N-channel [ 1112.332785] TX 17.06.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 8 [ 1112.342780] TX 17.07.04: FT T-MUX: N-channel [ 1112.342784] TX 17.07.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 9 [ 1112.352813] TX 17.08.04: FT T-MUX: Q-channel [ 1112.352817] TX 17.08.04: trx0: Q1: 0 Q2: 0 A/B: 8e carrier: 8 PSCN: 0 [ 1112.362797] TX 17.09.04: FT T-MUX: N-channel [ 1112.362803] TX 17.09.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 1 [ 1112.372794] TX 17.10.04: FT T-MUX: N-channel[ 1112.372800] TX 17.10.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 2 [ 1112.382788] TX 17.11.04: FT T-MUX: N-channel [ 1112.382794] TX 17.11.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 3 [ 1112.392821] TX 17.12.04: FT T-MUX: N-channel [ 1112.392827] TX 17.12.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 4 [ 1112.395383] RX 17.11.20: trx0: Q1: 0 Q2: 0 A/B: a0 carrier: 3 A-CRC: 0 X-CRC: 0 Z-CRC: 0 On Aug 14, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > Send linux-dect mailing list submissions to > linux-dect(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/linux-dect > or, via email, send a message with subject or body 'help' to > linux-dect-request(a)lists.osmocom.org > > You can reach the person managing the list at > linux-dect-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linux-dect digest..." > Today's Topics: > > 1. Re: linux-dect Digest, Vol 37, Issue 6 (Fr?d?ric LECAILLE) > 2. Re: linux-dect Digest, Vol 37, Issue 6 (henrik hansen) > > From: Frédéric LECAILLE <frednews78(a)free.fr> > Subject: Re: linux-dect Digest, Vol 37, Issue 6 > Date: August 13, 2012 9:53:23 PM GMT+02:00 > To: linux-dect(a)lists.osmocom.org > > > Hello Henrik, > > If you type this command in a terminal this will give you an idea about your issue: > > ldd /usr/lib/asterisk/modules/chan_dect.so > > > On Aug 11, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > >> Send linux-dect mailing list submissions to >> linux-dect(a)lists.osmocom.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.osmocom.org/mailman/listinfo/linux-dect >> or, via email, send a message with subject or body 'help' to >> linux-dect-request(a)lists.osmocom.org >> >> You can reach the person managing the list at >> linux-dect-owner(a)lists.osmocom.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of linux-dect digest..." >> Today's Topics: >> >> 1. undefined symbol: dect_mm_endpoint_get (henrik hansen) >> 2. Re: undefined symbol: dect_mm_endpoint_get (Patrick McHardy) >> >> From: henrik hansen <hhansen06(a)googlemail.com> >> Subject: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:35:09 PM GMT+02:00 >> To: linux-dect(a)lists.osmocom.org >> >> >> Hey, >> my Asterisk got a problem with the chan_dect module. >> I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >> >> debian*CLI> module load chan_dect >> Unable to load module chan_dect >> Command 'module load chan_dect' failed. >> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get >> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. >> >> Could someone help me, getting this fixed? >> >> -- >> -- >> Mit freundlichen Grüßen >> Henrik Hansen >> >> >> >> >> From: Patrick McHardy <kaber(a)trash.net> >> Subject: Re: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:37:12 PM GMT+02:00 >> To: henrik hansen <hhansen06(a)googlemail.com> >> Cc: linux-dect(a)lists.osmocom.org >> >> >> On Fri, 10 Aug 2012, henrik hansen wrote: >> >>> Hey, >>> my Asterisk got a problem with the chan_dect module. >>> I build it like it's written here: >>> http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >>> >>> debian*CLI> module load chan_dect >>> Unable to load module chan_dect >>> Command 'module load chan_dect' failed. >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error >>> loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: >>> undefined symbol: dect_mm_endpoint_get >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module >>> 'chan_dect' could not be loaded. >>> >>> Could someone help me, getting this fixed? >> >> Its basically that chan_dect hasn't been converted to use the new API >> for wideband audio support yet. Just fixing this problem without actually adding wideband support should be relatively easy, I'll try to have a look during the weekend. >> >> >> >> >> _______________________________________________ >> linux-dect mailing list >> linux-dect(a)lists.osmocom.org >> https://lists.osmocom.org/mailman/listinfo/linux-dect > > > > > From: henrik hansen <hhansen06(a)googlemail.com> > Subject: Re: linux-dect Digest, Vol 37, Issue 6 > Date: August 13, 2012 10:50:52 PM GMT+02:00 > To: Frédéric LECAILLE <frednews78(a)free.fr> > Cc: linux-dect(a)lists.osmocom.org > > > Hey Frédéric, > for me it looks like there are no problems: > > root@debian:~# ldd /usr/lib/asterisk/modules/chan_dect.so > linux-gate.so.1 => (0xb77a6000) > libdect.so.0 => /usr/lib/libdect.so.0 (0xb7765000) > libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb774c000) > libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7604000) > libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7600000) > libnl-dect.so.3 => /usr/local/lib/libnl-dect.so.3 (0xb75f5000) > libnl.so.3 => /usr/local/lib/libnl.so.3 (0xb75e1000) > /lib/ld-linux.so.2 (0xb77a7000) > libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb75bb000) > > My System is a Debian 6.0 x86 > > > 2012/8/13 Frédéric LECAILLE <frednews78(a)free.fr> > Hello Henrik, > > If you type this command in a terminal this will give you an idea about your issue: > > ldd /usr/lib/asterisk/modules/chan_dect.so > > > On Aug 11, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > >> Send linux-dect mailing list submissions to >> linux-dect(a)lists.osmocom.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.osmocom.org/mailman/listinfo/linux-dect >> or, via email, send a message with subject or body 'help' to >> linux-dect-request(a)lists.osmocom.org >> >> You can reach the person managing the list at >> linux-dect-owner(a)lists.osmocom.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of linux-dect digest..." >> Today's Topics: >> >> 1. undefined symbol: dect_mm_endpoint_get (henrik hansen) >> 2. Re: undefined symbol: dect_mm_endpoint_get (Patrick McHardy) >> >> From: henrik hansen <hhansen06(a)googlemail.com> >> Subject: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:35:09 PM GMT+02:00 >> To: linux-dect(a)lists.osmocom.org >> >> >> Hey, >> my Asterisk got a problem with the chan_dect module. >> I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >> >> debian*CLI> module load chan_dect >> Unable to load module chan_dect >> Command 'module load chan_dect' failed. >> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get >> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. >> >> Could someone help me, getting this fixed? >> >> -- >> -- >> Mit freundlichen Grüßen >> Henrik Hansen >> >> >> >> >> From: Patrick McHardy <kaber(a)trash.net> >> Subject: Re: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:37:12 PM GMT+02:00 >> To: henrik hansen <hhansen06(a)googlemail.com> >> Cc: linux-dect(a)lists.osmocom.org >> >> >> On Fri, 10 Aug 2012, henrik hansen wrote: >> >>> Hey, >>> my Asterisk got a problem with the chan_dect module. >>> I build it like it's written here: >>> http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >>> >>> debian*CLI> module load chan_dect >>> Unable to load module chan_dect >>> Command 'module load chan_dect' failed. >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error >>> loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: >>> undefined symbol: dect_mm_endpoint_get >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module >>> 'chan_dect' could not be loaded. >>> >>> Could someone help me, getting this fixed? >> >> Its basically that chan_dect hasn't been converted to use the new API >> for wideband audio support yet. Just fixing this problem without actually adding wideband support should be relatively easy, I'll try to have a look during the weekend. >> >> >> >> >> _______________________________________________ >> linux-dect mailing list >> linux-dect(a)lists.osmocom.org >> https://lists.osmocom.org/mailman/listinfo/linux-dect > > > > > -- > -- > Mit freundlichen Grüßen > Henrik Hansen > > Waldstr 29 > 28816 Stuhr > > Tel.: 04206 6698 > Mobil: 0170 2350 222 > Mail: hhansen06(a)googlemail.com > > > > _______________________________________________ > linux-dect mailing list > linux-dect(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/linux-dect

11 years, 8 months

2
5
0 0

Re: linux-dect Digest, Vol 37, Issue 6

by Frédéric LECAILLE

Hello Henrik, If you type this command in a terminal this will give you an idea about your issue: ldd /usr/lib/asterisk/modules/chan_dect.so On Aug 11, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > Send linux-dect mailing list submissions to > linux-dect(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/linux-dect > or, via email, send a message with subject or body 'help' to > linux-dect-request(a)lists.osmocom.org > > You can reach the person managing the list at > linux-dect-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linux-dect digest..." > Today's Topics: > > 1. undefined symbol: dect_mm_endpoint_get (henrik hansen) > 2. Re: undefined symbol: dect_mm_endpoint_get (Patrick McHardy) > > From: henrik hansen <hhansen06(a)googlemail.com> > Subject: undefined symbol: dect_mm_endpoint_get > Date: August 10, 2012 4:35:09 PM GMT+02:00 > To: linux-dect(a)lists.osmocom.org > > > Hey, > my Asterisk got a problem with the chan_dect module. > I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions > > debian*CLI> module load chan_dect > Unable to load module chan_dect > Command 'module load chan_dect' failed. > [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get > [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. > > Could someone help me, getting this fixed? > > -- > -- > Mit freundlichen Grüßen > Henrik Hansen > > > > > From: Patrick McHardy <kaber(a)trash.net> > Subject: Re: undefined symbol: dect_mm_endpoint_get > Date: August 10, 2012 4:37:12 PM GMT+02:00 > To: henrik hansen <hhansen06(a)googlemail.com> > Cc: linux-dect(a)lists.osmocom.org > > > On Fri, 10 Aug 2012, henrik hansen wrote: > >> Hey, >> my Asterisk got a problem with the chan_dect module. >> I build it like it's written here: >> http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >> >> debian*CLI> module load chan_dect >> Unable to load module chan_dect >> Command 'module load chan_dect' failed. >> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error >> loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: >> undefined symbol: dect_mm_endpoint_get >> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module >> 'chan_dect' could not be loaded. >> >> Could someone help me, getting this fixed? > > Its basically that chan_dect hasn't been converted to use the new API > for wideband audio support yet. Just fixing this problem without actually adding wideband support should be relatively easy, I'll try to have a look during the weekend. > > > > > _______________________________________________ > linux-dect mailing list > linux-dect(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/linux-dect

11 years, 8 months

2
2
0 0

undefined symbol: dect_mm_endpoint_get

by henrik hansen

Hey, my Asterisk got a problem with the chan_dect module. I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions debian*CLI> module load chan_dect Unable to load module chan_dect Command 'module load chan_dect' failed. [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. Could someone help me, getting this fixed? -- -- Mit freundlichen Grüßen Henrik Hansen

11 years, 8 months

2
1
0 0

Re: debt 6.0 rf band

by Frédéric LECAILLE

On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote: > Updated patch attached > <usdect.diff> Ok thank you a lot Patrick. Here are the results: with your last patch: dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 *The frequency is always 0 MHz* The kernel logs seems to be OK: [15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27 So I have tried your last patch with mine to force the rf_band to 1: dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on... About trx2: dect-transceiver-list --name trx2 DECT Transceiver trx2: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0 slot 0: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 (no a-crc-errors) If I remember well, with only my patch which forces the rf_band to 3 we got for trx2: dect-transceiver-list --name trx2 I see that slot0 is scanning: DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0

11 years, 8 months

2
7
0 0

debt 6.0 rf band

by Frédéric LECAILLE

Hello, I am trying to use a dosh&amand PCI card… this one: 01:03.0 Communication controller: Quicklogic Corporation COM-ON-AIR Dosch&Amand DECT (rev 32) Subsystem: Device 1786:0001 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 20 Region 0: Memory at ddefe000 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: com_on_air_pci with the dect kernel stack… I have managed to compile the kernel 3.2.0 with this config: CONFIG_DECT=m CONFIG_DECT_DEBUG=y CONFIG_DECT_CSF=m CONFIG_DECT_RAW=m CONFIG_DECT_CCF=m CONFIG_DECT_LU1_SAP=m CONFIG_DECTDEVICES=y CONFIG_DECT_VTRX=m CONFIG_DECT_COA_PCI=m CONFIG_DECT_COA=m CONFIG_DECT_COA_U2785=y CONFIG_DECT_COA_FIRMWARE=y CONFIG_DECT_COA_P64=y The driver seems to work but the issue is that I am trying to use it in USA for an American client, and I did not managed to make this card use the 1.9Mhz band (rf band 3 I guess). When I run this command: dect-transceiver-list --name trx2 I see that slot0 is scanning: DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0 but it nevers uses RF band 3 channel. For you information I have patch the driver this way to set the default debt rf band to 3: [root@localhost linux-2.6]# git diff diff --git a/drivers/dect/coa/sc1442x.c b/drivers/dect/coa/sc1442x.c index 73b9869..89b0a55 100644 --- a/drivers/dect/coa/sc1442x.c +++ b/drivers/dect/coa/sc1442x.c @@ -698,6 +698,7 @@ static u64 sc1442x_set_band(const struct dect_transceiver *t { struct coa_device *dev = dect_transceiver_priv(trx); +printk("setting band %d\n", band->band); return dev->radio_ops->map_band(dev, band); } diff --git a/net/dect/transceiver.c b/net/dect/transceiver.c index 706899d..25278af 100644 --- a/net/dect/transceiver.c +++ b/net/dect/transceiver.c @@ -19,6 +19,8 @@ #include <net/dect/mac_csf.h> #include <net/dect/transceiver.h> +static int rf_band = 3; +module_param(rf_band, int, 0); static LIST_HEAD(dect_transceiver_list); static int dect_transceiver_notify(struct dect_transceiver *trx, unsigned long event); @@ -651,7 +653,7 @@ int dect_register_transceiver(struct dect_transceiver *trx) if (err < 0) goto out; - err = dect_transceiver_set_band(trx, DECT_DEFAULT_BAND); + err = dect_transceiver_set_band(trx, rf_band); if (err < 0) goto out; Thank you in advance for any help. Fred

11 years, 8 months

2
3
0 0

anyone for hire for dedected install and config for PCI card?

by Jeff Doucette

Is there anyone available for hire to help me get Dedected like CLI tools working with OcmocomDECT. I have the Com on Air PCI card and can't figure out how to get the driver to work. I need some guidence and willing to pay for it. Please advise, J BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }

11 years, 8 months

1
0
0 0

State of Work?

by henrik hansen

Hello List, I'm new to the osmocomDECT project and just bought 2 com-on-air PCI Cards. After reading the list archive, i have some questions about the state of the project. What features do we suport at the moment? Can i build a dect cell with asterisk support? is handover within a cell about multiple basestations supported? if i can help, test or support the project with hardware, so please tell ;) -- -- Mit freundlichen Grüßen Henrik Hansen

11 years, 8 months

1
0
0 0

The LMX3161 still not supported ?

by ol ol

Hi! Is there any news on the chipset support LMX3161? COA card III-type of still does not work with osmocom soft? Thanks, Blago.

11 years, 9 months

1
0
0 0

How to build Wireshark-1.6.7 against patched libpcap

by chiccus2003＠libero.it

Hi, I do not know how to build Wireshark-1.6.7 against patched libpcap. The Kernel 3.2.0+ is built and installed in directory: umberto@umberto-desktop:/usr/src The patched libpcap + libnl +libdect are built and installed in directory: umberto@umberto-desktop:/usr/src/tools Also the source directory wireshark-1.6.7 is in directory: umberto@umberto-desktop:/usr/src/tools I do: cd wireshark-1.6.7$ sudo ./configure --with-pcap=/usr/local/lib and I get the error: ........ checking for connect... yes checking whether to use libpcap for packet capture... yes checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... no checking for pcap_open_live in -lpcap with -lcfg -lodm... no checking for pcap_open_live in -lpcap with -lpfring... no configure: error: Can't link with library libpcap. andrea@andrea-desktop:/usr/src/tools/wireshark-1.6.7$ What should I do? (Pci card installed) With best regards, Umberto

11 years, 10 months

4
19
0 0

How to build Wireshark-1.6.7 against patched libpcap

by chiccus2003＠libero.it

Hi, I do not know how to build Wireshark-1.6.7 against patched libpcap. The Kernel 3.2.0+ is built and installed in directory: umberto@umberto-desktop:/usr/src The patched libpcap + libnl +libdect are built and installed in directory: umberto@umberto-desktop:/usr/src/tools Also the source directory wireshark-1.6.7 is in directory: umberto@umberto-desktop:/usr/src/tools I do: cd wireshark-1.6.7$ sudo ./configure --with-pcap=/usr/local/lib and I get the following error: ........ checking for connect... yes checking whether to use libpcap for packet capture... yes checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... no checking for pcap_open_live in -lpcap with -lcfg -lodm... no checking for pcap_open_live in -lpcap with -lpfring... no configure: error: Can't link with library libpcap. andrea@andrea-desktop:/usr/src/tools/wireshark-1.6.7$ But if I run “./configure”, then when I run “sudo wireshark” can not find the interface dect. There are only interfaces: "any" - "lo" - "usb0". What should I do? (Pci card installed) With best regards, Umberto

11 years, 11 months

2
1
0 0

Problems Building DECT Stack

by Sebastian ---

Hi First Problem: When I try to Build libdect (libnl was build and Installed without any critical errors): root@bt:/home/libdect# sh configure checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a thread-safe mkdir -p... /bin/mkdir -p checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed configure: Documentation build disabled checking for nl_socket_alloc in -lnl... no configure: error: No suitable version of libnl found Second Problem: When I Put in my com-on-air PCMCIA Card, and look in Kern.log: Apr 19 19:06:26 bt kernel: [ 13.847922] com_on_air_cs 0.0: DECTDataDevice PCMCIA F22 Apr 19 19:06:26 bt kernel: [ 13.888290] com_on_air_cs 0.0: Radio type U2785B Apr 19 19:06:26 bt kernel: [ 13.901784] com_on_air_cs 0.0: Loading firmware ... Apr 19 19:06:26 bt kernel: [ 13.996529] pcmcia 0.1: pcmcia: registering new device pcmcia0.1 (IRQ: 3) Apr 19 19:06:26 bt kernel: [ 13.996740] com_on_air_cs 0.1: DECTDataDevice PCMCIA F22 Apr 19 19:06:26 bt kernel: [ 13.996818] com_on_air_cs 0.1: failed to enable PCMCIA device Apr 19 19:06:26 bt kernel: [ 13.996880] com_on_air_cs: probe of 0.1 failed with error -13

11 years, 12 months

4
9
0 0

Protocol mismatch error

by Tasha

Hello Patrick, I am currently working on my master thesis in computer science in which I'm trying to exploit you great open source software linux DECT-Stack. I plan to use it for controlling a Com-On-Air PCI ISDN card (Dosch&Amand). However, I'm facing problems with operating libdect, dectmon. To be more precise, after installing software and trying to run it I always get the following error message: dect_netlink_init: Protocol mismatch dect_init: Bad file descriptor root@dect:~/dectmon# valgrind src/dectmon ==4479== Memcheck, a memory error detector ==4479== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==4479== Using Valgrind-3.6.1-Debian and LibVEX; rerun with -h for copyright info ==4479== Command: src/dectmon ==4479== dectmon > ==4479== Warning: invalid file descriptor -1 in syscall close() dect_netlink_init: Protocol mismatch dectmon > dect_open_handle: Bad file descriptor ==4479== ==4479== HEAP SUMMARY: ==4479== in use at exit: 65,329 bytes in 189 blocks ==4479== total heap usage: 305 allocs, 116 frees, 74,326 bytes allocated ==4479== ==4479== LEAK SUMMARY: ==4479== definitely lost: 0 bytes in 0 blocks ==4479== indirectly lost: 0 bytes in 0 blocks ==4479== possibly lost: 0 bytes in 0 blocks ==4479== still reachable: 65,329 bytes in 189 blocks ==4479== suppressed: 0 bytes in 0 blocks ==4479== Rerun with --leak-check=full to see details of leaked memory ==4479== ==4479== For counts of detected and suppressed errors, rerun with: -v ==4479== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 39 from 6) root@dect:~/dectmon# and for any dect-command in asterisk: No such command 'dect show portables' Since my master degree depends highly on successful usage of your software I want to ask you for help and would very appreciate it. It would be very nice if you could give me an advise on how the problem can be solved. Please let me know if you need additional info, esp. in case the error text is not enough for you to be able to analyze the error. Thank you in advance! Best Regards, Tasha

12 years, 1 month

2
3
0 0

libnl 'make' fails

by DeDecTed

Hi, I've been trying to compile 'libnl' on my Ubuntu 11.10 and I got the error: CC route/cls/ematch_grammar.lo route/cls/ematch_grammar.c:773:5: error: unknown type name 'YYSTYPE' The needed libs like byacc, bison or flex had been previously installed. Any clue what might cause the problem?

12 years, 1 month

1
0
0 0

Using the DECT stack in PP mode

by Matthew Hess

Hi there, I would appreciate it if you could post this question to the linux-dect mailing list. I've been playing with the Osmocom DECT stack for a while now, trying to make it work in PP mode against a base station I've got. My goal right now is just to be able to run the pp-location-update example in libdect. So far, I've managed to compile, run and configure everything (I'm using the COA PCI card). dect-llme-scan shows my base station, and it has the "location_registration" higher layer capability. However, running the pp-location-update example results in the following output: "FP does not support location registration". The debug output from the kernel shows the following (apparently) interesting things: 1. "incomplete:SARI" is repeated a few times. 2. After a while, "timeout" 3. This repeats forever, with lots of seemingly "redundant" (and uninteresting) debug output in between. I'm guessing that the MAC layer doesn't want to lock on to the base station for some reason. I found the code that does this in mac_csf.c, but I'm clueless as to what I can actually do about it. I wonder if you could help me with this somehow. Perhaps you could point me to the right direction as to what could be changed in order for this to work? Or why does the stack not lock onto the base station? The base station does work with commercial DECT PPs, so some changes to the mac_csf code should probably make it work. I'm pretty good at playing with kernel code, I'm just not sure what is the right thing to do. I appreciate the help. Matt Hess

12 years, 2 months

1
0
0 0

can we please make spammers harder to post new tickets?

by Allard Dijk

Hi, On avg. we get 2 spam tickets a day on Trac. Can you add some level of spam protection to add a ticket? *CAPTCHA *login required < this barrier is the quickest... (and is the same as other osmocom tracs) *changed ticket flow ( ticket not visible before approval) Best, Allard

12 years, 7 months

3
4
0 0

compile failure

by Joe Freeman

Greetings- I'm trying to compile from the git sources, based on the 2.6 kernel included on the website. This is an an x86_64 install (originally CentOS 6, but I've got kernel 3.0.4 running on it now)... I'm having a heck of a time getting the DECT stuff to compile in the kernel. my make keeps failing- In file included from /home/jfreeman/linux-2.6/include/net/dect/dect.h:147, from /home/jfreeman/linux-2.6/drivers/dect/coa/sc1442x.c:19: /home/jfreeman/linux-2.6/include/net/dect/identities.h:55: error: field âarcâ has incomplete type make[4]: *** [drivers/dect/coa/sc1442x.o] Error 1 make[3]: *** [drivers/dect/coa] Error 2 make[2]: *** [drivers/dect] Error 2 make[1]: *** [drivers] Error 2 make: *** [sub-make] Error 2 That's the most recent failure, after I removed the enum dect_ari_classes from dect_netlink.h Anyone have any thoughts or suggestions? Thanks- Joe

12 years, 7 months

2
1
0 0

Will the LMX3161 be supported in the future?

by luca bongiorni

Hi guys, have you find a solution for LMX3161 to be fully supported? Regards Luca

12 years, 8 months

5
14
0 0

dect.osmocom.org Wiki accounts

by Patrick McHardy

Since Romain already asked for it, if someone wants Wiki accounts on dect.osmocom.org for adding new content, just send me an email.

12 years, 8 months

1
0
0 0

Siemens proprietary protocol

by Romain Fliedel

Hi, I'm trying to understand siemens proprietary protocol and I'd like to add some data on the wiki (add new pcap, and dumps). How do I create an account on the wiki ? (it asks for a login/password) Does someone have pcaps for other siemens phones ? Thanks

12 years, 8 months

2
1
0 0

dectmon how to ?

by Fliedel Romain

Hi again, Since I got the pcap to work with dect I'm trying to capture traffic between a handset and its base. I've been able to find my FP with dect-llme-scan (as specified here http://dect.osmocom.org/trac/dect/wiki/Configuration), but now I'd like to lock to this FP and capture the traffic with wireshark. I've used the dectmon utility but it's locking to other FP. Is there a way to lock to a specific FP ? Is there a how to somewhere for capturing traffic ? Thanks again, Romain

12 years, 8 months

2
1
0 0

pairing problem

by Tobias Seufert

12 years, 8 months

2
1
0 0

problem building kernel

by Fliedel Romain

Hi, I'm trying to build a kernel from the git repository with dect stack enabled but i get this error : net/dect/ccp.c:25:27: fatal error: net/tipc/tipc.h: it appears that this file has been removed in kernel 2.6.36 Do you have any idea to solve this problem ? Thanks

12 years, 8 months

3
9
0 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linux-dect