This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/linux-dect@lists.osmocom.org/.
Patrick McHardy kaber at trash.netOn 14.11.2010 14:04, Patrick McHardy wrote: > On 14.11.2010 01:55, Erik Tews wrote: >> I now switched that to: >> >> >> dect-cluster-add --name cluster0 --emc $EMC --fpn $FPN --mode pp >> dect-cell-add --name cell0 --cluster cluster0 --flags monitor >> dect-transceiver-bind --transceiver trx0 --cell cell0 >> >> But I still have the same problem. >> >> Do I need a newer kernel than commit >> 75a0d091dc8074ef940932cf6027fcdf59277070 to run the kernel in >> monitoring-mode? > > No, that one should be fine. If you're still seeing > >> netlink: message group: 4 > > without FPC and HLC following, that means that the PP lost lock > with the FP. If you enable debugging for mac_csf.c, you should > see the reason in the logs. > BTW: > netlink: message group: 4 > netlink: FPC: full_slot,page_repetition,basic_a_field_setup,in_min_delay > netlink: HLC: adpcm_g721_voice,gap_pap_basic_speech,standard_authentication,location_registration It seems your FP doesn't support ciphering, so its possible that it doesn't broadcast the multi-frame number, which my stack expects. It shouldn't have locked to the FP in that case though. Perhaps the FP broadcasts the MFN at a lesser frequency than defined in the standard - if the stack doesn't receive the MFN at least every 8 multiframes (T216), it unlocks from the FP.