openlte-discuss Mailing List for openLTE
An open source 3GPP LTE implementation.
Status: Alpha
Brought to you by:
bwojtowi
Menu
▾
▴
openlte-discuss — Technical discussion
You can subscribe to this list here.
| 2012 |
Jan
(2) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(9) |
Jun
(4) |
Jul
(14) |
Aug
(1) |
Sep
|
Oct
(5) |
Nov
(1) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(17) |
Feb
(13) |
Mar
(23) |
Apr
(12) |
May
(8) |
Jun
(7) |
Jul
(22) |
Aug
(7) |
Sep
(16) |
Oct
(30) |
Nov
(14) |
Dec
(14) |
| 2014 |
Jan
(7) |
Feb
(6) |
Mar
(16) |
Apr
(4) |
May
(15) |
Jun
(28) |
Jul
(20) |
Aug
(6) |
Sep
(59) |
Oct
(57) |
Nov
(26) |
Dec
(86) |
| 2015 |
Jan
(67) |
Feb
(62) |
Mar
(21) |
Apr
(19) |
May
(8) |
Jun
(17) |
Jul
(5) |
Aug
(25) |
Sep
(13) |
Oct
(2) |
Nov
(8) |
Dec
(23) |
| 2016 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(1) |
May
(1) |
Jun
(3) |
Jul
(13) |
Aug
(5) |
Sep
(7) |
Oct
(7) |
Nov
(12) |
Dec
(13) |
| 2017 |
Jan
(2) |
Feb
(7) |
Mar
(3) |
Apr
(4) |
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(16) |
Sep
(1) |
Oct
(3) |
Nov
(2) |
Dec
(2) |
| 2018 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|
From: Dan Dole-M. <dan...@bs...> - 2021-12-10 21:06:57
|
Hello everyone,
I have been hoping to use openLTE v21 as a jumping-off point for an
LTE-related project, but have run into errors with the physical layer
library. Presently, it appears as though neither the scanner or generator
programs work due to this. I have tried this installation both on Ubuntu
20.04, and 18.04 and on the PiSDR image (only the PiSDR image installation
was possible with minor edits to the source code).
Specifically, compiling with gcc 8.3 returned an error:
In file included from
/home/pi/Desktop/openLTE/v21/openlte_v00-21-00/liblte/tests/liblte_mac_tests.cc:34:
/home/pi/Desktop/openLTE/v21/openlte_v00-21-00/liblte/hdr/liblte_mac.h:428:114:
error: narrowing conversion of ‘-6’ from ‘int’ to ‘int8’ {aka ‘char’}
inside { } [-Wnarrowing]
static const int8
liblte_mac_rar_tpc_command_num[LIBLTE_MAC_RAR_TPC_COMMAND_N_ITEMS] = {-6,
-4, -2, 0, 2, 4, 6, 8};
I was able to fix the compiler error by replacing that line with the
following:
static const int8
liblte_mac_rar_tpc_command_num[LIBLTE_MAC_RAR_TPC_COMMAND_N_ITEMS] =
{(int8) -6, (int8) -4, (int8) -2, 0, 2, 4, 6, 8};
I was able to satisfy my compiler this way, but I'm unsure if this has
unintended side effects--especially as this header is referenced by several
files.
I've included my make log here
<https://drive.google.com/file/d/1Fkt1cSeMJ8_gibq4ZPcNEbCKthbHx8IB/view?usp=sharing>
or those interested in seeing the full gamut of errors and warnings. Some
appear to state changes in gcc 7.1 may affect the code--but this particular
version of gcc was released in May 2017, what version of gcc have people
used to successfully compile openLTE v21?
That said, when I run the liblte_phy_test, the following tests fail:
pusch_channel_encode_decode_test
pdsch_channel_encode_decode_test
pdcch_channel_encode_decode_test
pss_sss_test
I have been stepping through the code trying to find the source of the
error for the PUSCH test, below are a couple of interesting things I've
discovered thus far--will update you again when I have more.
- Fails because msg.msg[i] and alloc.msg[0].msg[i] are unequal when checked
at the end of the test
- alloc.msg[0] is populated at start of pusch_channel_encode_decode_test with
alternating 0s and 1s, put through the encoder, put back through the
decoder and the resulting msg.msg[i] is all 0s
- msg.msg[i] is returned by liblte_phy_pusch_channel_decode, within the
function it's defined as out_bits
- out_bits in turn is populated by a_bits (within ulsch_channel_decode),
which is in turn populated by ulsch_b_bits, which are reset to 0 at the
start of ulsch_channel_decode
- This is because in order to decode an ULSCH message, the NULL bit
pattern must be determined by encoding a sequence of 0s
- However, when the ulsch_b_bits are later “recovered” later on as a_bits
and p_bits, both end up as 0s
- ulsch_b_bits are modified both in liblte_phy_code_block_segmentation and
liblte_phy_code_block_desegmentation, perhaps the error is here? Or,
perhaps the rabbit hole goes deeper--this is as far as I've gotten, though
my work continues…
Lastly, I had some concerns about the osmoSDR device selection. The check
for a hackRF device in the code prior to rtl-sdr/other SDRs exits the
program with a no-device-detected error. I was able to bypass this and
utilize our rtl-sdr by checking for that device before the other supported
peripheral SDRs (by rearranging the if statement), and I recommend that we
consider making this change in a future release.
I would love to hear any thoughts on these matters--currently the physical
layer library issues are the most pressing, though I'm certainly curious to
hear about the other issues mentioned as well.
Thanks for your time, this is an excellent project and I would love to
build on it!
Best,
Dan Dole-Muinos
|
|
From: Mario L. <mar...@ma...> - 2020-09-11 08:38:26
|
Dear community, Could you please advise me if openLTE works on limeSDR? Thank you -- Mario Lucas |
|
From: billy.peter <bil...@pr...> - 2019-02-25 07:26:53
|
Hi all, I have successfully installed OpenLTE but whenever I start it with USRP B205 Mini , it crashes with segmentation fault with lots of 'LLL', 'OOO', 'UUU'. I am operating over USB 3.0 but not able to sort out the cause of this issue. Any help in this regard is appreciated. Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email. |
|
From: billy.peter <bil...@pr...> - 2019-02-20 07:36:18
|
Hello I am trying to setup OpenLTE. My system specs are Core I-7 with Ubuntu 16.04 and USRP B205mini but I have USB 2.0 connectivity supported in my CPU. When I start openlte i see following debug logs and application exits. Logs are attached in file Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. 02/20/2019 12:08:10.873624 info iface LTE_fdd_enb_interface.cc 779 *** LTE FDD ENB DEBUG INTERFACE *** 02/20/2019 12:08:15.465008 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_gw circular buffer empty on receive 02/20/2019 12:08:19.230328 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_phy circular buffer empty on receive 02/20/2019 12:08:19.230382 warning msgq LTE_fdd_enb_msgq.cc 234 phy_to_mac circular buffer empty on receive 02/20/2019 12:08:19.230437 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_mac circular buffer empty on receive 02/20/2019 12:08:19.230479 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_timer circular buffer empty on receive 02/20/2019 12:08:19.230538 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_pdcp circular buffer empty on receive 02/20/2019 12:08:19.230593 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rlc circular buffer empty on receive 02/20/2019 12:08:19.230622 warning msgq LTE_fdd_enb_msgq.cc 234 rlc_to_pdcp circular buffer empty on receive 02/20/2019 12:08:19.230675 warning msgq LTE_fdd_enb_msgq.cc 234 mac_to_rlc circular buffer empty on receive 02/20/2019 12:08:19.230704 warning msgq LTE_fdd_enb_msgq.cc 234 gw_to_pdcp circular buffer empty on receive 02/20/2019 12:08:19.230733 warning msgq LTE_fdd_enb_msgq.cc 234 pdcp_to_rrc circular buffer empty on receive 02/20/2019 12:08:19.230753 warning msgq LTE_fdd_enb_msgq.cc 234 mme_to_rrc circular buffer empty on receive 02/20/2019 12:08:19.230785 warning msgq LTE_fdd_enb_msgq.cc 234 rrc_to_mme circular buffer empty on receive 02/20/2019 12:08:33.115278 info radio LTE_fdd_enb_radio.cc 424 RX modifying recv_size to sync 15329877 15329280 02/20/2019 12:08:33.115324 info radio LTE_fdd_enb_radio.cc 410 RX synced 15329280 15329280 02/20/2019 12:08:33.122800 error radio LTE_fdd_enb_radio.cc 443 RX packet size issue 1690 1920 15377280 15377280 02/20/2019 12:08:33.122846 error radio LTE_fdd_enb_radio.cc 560 RX error 8 02/20/2019 12:08:33.123712 error radio LTE_fdd_enb_radio.cc 464 RX overrun 15466351 15382810 02/20/2019 12:08:33.126132 info radio LTE_fdd_enb_radio.cc 424 RX modifying recv_size to sync 15483631 15482880 02/20/2019 12:08:33.126150 info radio LTE_fdd_enb_radio.cc 410 RX synced 15482880 15482880 02/20/2019 12:08:33.128941 error phy LTE_fdd_enb_phy.cc 709 PDSCH current_tti from MAC (1) does not match PHY (11) 02/20/2019 12:08:33.129194 info mac LTE_fdd_enb_mac.cc 409 MAC_dl_tti - PHY_dl_tti != 2 (-5), skipping 8 subframes 02/20/2019 12:08:33.130822 error radio LTE_fdd_enb_radio.cc 443 RX packet size issue 1780 1920 15507840 15507840 02/20/2019 12:08:33.130843 error radio LTE_fdd_enb_radio.cc 560 RX error 8...... Why is it so? Is it due to lack of USB 3.0connectivity? but in next logs, I can see that its actually getting the required clock rate. Then what could be the reason for failure in stable start? $ sudo LTE_fdd_enodeb [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.11.0.1-16-g34fc6362 *** LTE FDD ENB *** Please connect to control port 30000 [INFO] [B200] Detected Device: B205mini [INFO] [B200] Operating over USB 2. [INFO] [B200] Initialize CODEC control... [INFO] [B200] Initialize Radio control... [INFO] [B200] Performing register loopback test... [INFO] [B200] Register loopback test passed [INFO] [B200] Setting master clock rate selection to 'automatic'. [INFO] [B200] Asking for clock rate 16.000000 MHz... [INFO] [B200] Actually got clock rate 16.000000 MHz. [INFO] [MULTI_USRP] Setting master clock rate selection to 'manual'. [INFO] [B200] Asking for clock rate 30.720000 MHz... [INFO] [B200] Actually got clock rate 30.720000 MHz. OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOULLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLLLLLOLLLLLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLOLLLLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLOLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLOLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLOLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLOLLLLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLLOLLLLLLLLLLLLLOLLLLLLLLLLLOSegmentation fault (core dumped) terminal@terminal-All-Series:~$ sudo LTE_fdd_enodeb Thanks Sent with [ProtonMail](https://protonmail.com) Secure Email. |
|
From: William D. <wil...@gm...> - 2018-08-21 12:56:30
|
Hi everyone, I’m trying to use OpenLTE on an USRP and i wanted to test it after the installation When I run the following command : LTE_fdd_dl_file_scan.py LTE_test_file_int8.bin I have the following error : AttributeError: module ‘LTE_fdd_dl_fs’ has no attribute ‘samp_buf’ I don’t really know what to do... Thanks in advance, William |
|
From: iSignal R. <isi...@gm...> - 2018-08-01 15:00:42
|
Hi Ben, i want to setup openLTE with limeSDR. Can you let me know whether openLTE supports LimeSDR, if yes, let me know the versions of ubuntu , gnuRadio, 1eNB Configurations to take for testing till attach of LTE. Thanks, Ram. |
|
From: <gui...@or...> - 2018-03-13 12:09:54
|
You're right. I installed only libmbedtls-dev but forgot libmbedtls10 library. It works perfectly now ! Thank you ! Le 13/03/2018 à 10:26, Oscar Llerena a écrit : > Hi, I think your problem is related to MBEDTLS library. > "mbedtls_aes_crypt_ecb" > It is possible that you might not find it on your distribution (you > should do "apt-cache search mbedtls) and try to install the suggested > answers (here be wise, read the descriptions) ... > > If the above does not work, then try to download MBEDTLS from github: > https://tls.mbed.org/download/start/mbedtls-2.7.0-apache.tgz and > follow the installation README. Compile OpenLTE again. > > If that does not work then you have to use this version: > https://tls.mbed.org/download/start/polarssl-1.3.9-gpl.tgz. > Polarssl is original name of MBEDTLS. > > 2018-03-13 5:26 GMT-05:00 <gui...@or... > <mailto:gui...@or...>>: > > Hello, > > I have the following errors : > > [ 77%] Linking CXX executable LTE_fdd_enodeb > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_asme(unsigned char*, unsigned char*, > unsigned char*, unsigned char*, unsigned short, unsigned short, > unsigned char*) » : > liblte_security.cc:(.text+0x1c4) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x1e2) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_enb(unsigned char*, unsigned int, > unsigned char*) » : > liblte_security.cc:(.text+0x2aa) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x2c6) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_nas(unsigned char*, > LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, > LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, > unsigned char*) » : > liblte_security.cc:(.text+0x36d) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x389) : référence indéfinie vers > « mbedtls_md_hmac » > liblte_security.cc:(.text+0x3b5) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x3d1) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_rrc(unsigned char*, > LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, > LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, > unsigned char*) » : > liblte_security.cc:(.text+0x47d) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x499) : référence indéfinie vers > « mbedtls_md_hmac » > liblte_security.cc:(.text+0x4c5) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x4e1) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_up(unsigned char*, > LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, > LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, > unsigned char*) » : > liblte_security.cc:(.text+0x58d) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x5a9) : référence indéfinie vers > « mbedtls_md_hmac » > liblte_security.cc:(.text+0x5d5) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x5f1) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_128_eia2(unsigned char*, unsigned int, unsigned > char, unsigned char, unsigned char*, unsigned int, unsigned char*) » : > liblte_security.cc:(.text+0x6d6) : référence indéfinie vers > « mbedtls_aes_setkey_enc » > liblte_security.cc:(.text+0x6ef) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0xbbd) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0xd46) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_128_eia2(unsigned char*, unsigned int, unsigned > char, unsigned char, LIBLTE_BIT_MSG_STRUCT*, unsigned char*) » : > liblte_security.cc:(.text+0x1007) : référence indéfinie vers > « mbedtls_aes_setkey_enc » > liblte_security.cc:(.text+0x101c) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0x1e9e) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0x2033) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > collect2: error: ld returned 1 exit status > LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/build.make:545 : la > recette pour la cible « LTE_fdd_enodeb/LTE_fdd_enodeb » a échouée > make[2]: *** [LTE_fdd_enodeb/LTE_fdd_enodeb] Erreur 1 > CMakeFiles/Makefile2:961 : la recette pour la cible > « LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/all » a échouée > make[1]: *** [LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/all] > Erreur 2 > Makefile:138 : la recette pour la cible « all » a échouée > make: *** [all] Erreur 2 > > > > Le 12/03/2018 à 18:40, Tomcsányi, Domonkos a écrit : >> Hi >> >> It is hard to help you without seeing the error message itself. >> >> Cheers, >> Domi >> >> >> 2018. márc. 12. dátummal, 17:43 időpontban guillaume tochou >> <gui...@or... >> <mailto:gui...@or...>> írta: >> >>> Hello, >>> >>> I'm new on the the mailing list and I'm trying to install openlte. >>> >>> I downloaded the last version (openlte_v00-20-05) and I also >>> used the patch >>> (https://sourceforge.net/p/openlte/mailman/message/35039389/ >>> <https://sourceforge.net/p/openlte/mailman/message/35039389/>) >>> that allows to replace the polarssl package by the mbedtls >>> package (I'm using Ubuntu 16.04). But I'm having an error when >>> doing make. >>> >>> Is anyone who succeed to install openlte with the patch on >>> Ubuntu 16.04 ? >>> >>> Thanks >>> >>> Guillaume >>> >>> <https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download><https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download> >>> >>> _________________________________________________________________________________________________________________________ >>> >>> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc >>> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler >>> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, >>> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. >>> >>> This message and its attachments may contain confidential or privileged information that may be protected by law; >>> they should not be distributed, used or copied without authorisation. >>> If you have received this email in error, please notify the sender and delete this message and its attachments. >>> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. >>> Thank you. >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://Slashdot.org>! >>> http://sdm.link/slashdot >>> _______________________________________________ >>> Openlte-discuss mailing list >>> Ope...@li... >>> <mailto:Ope...@li...> >>> https://lists.sourceforge.net/lists/listinfo/openlte-discuss >>> <https://lists.sourceforge.net/lists/listinfo/openlte-discuss> > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > <mailto:Ope...@li...> > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > <https://lists.sourceforge.net/lists/listinfo/openlte-discuss> > > _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. |
|
From: Oscar L. <jar...@gm...> - 2018-03-13 10:26:31
|
Hi, I think your problem is related to MBEDTLS library. "mbedtls_aes_crypt_ecb" It is possible that you might not find it on your distribution (you should do "apt-cache search mbedtls) and try to install the suggested answers (here be wise, read the descriptions) ... If the above does not work, then try to download MBEDTLS from github: https://tls.mbed.org/download/start/mbedtls-2.7.0-apache.tgz and follow the installation README. Compile OpenLTE again. If that does not work then you have to use this version: https://tls.mbed.org/download/start/polarssl-1.3.9-gpl.tgz. Polarssl is original name of MBEDTLS. 2018-03-13 5:26 GMT-05:00 <gui...@or...>: > Hello, > > I have the following errors : > > [ 77%] Linking CXX executable LTE_fdd_enodeb > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_asme(unsigned char*, unsigned char*, > unsigned char*, unsigned char*, unsigned short, unsigned short, unsigned > char*) » : > liblte_security.cc:(.text+0x1c4) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x1e2) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_enb(unsigned char*, unsigned int, unsigned > char*) » : > liblte_security.cc:(.text+0x2aa) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x2c6) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_nas(unsigned char*, > LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, > unsigned char*, unsigned char*) » : > liblte_security.cc:(.text+0x36d) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x389) : référence indéfinie vers > « mbedtls_md_hmac » > liblte_security.cc:(.text+0x3b5) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x3d1) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_rrc(unsigned char*, > LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, > unsigned char*, unsigned char*) » : > liblte_security.cc:(.text+0x47d) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x499) : référence indéfinie vers > « mbedtls_md_hmac » > liblte_security.cc:(.text+0x4c5) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x4e1) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_generate_k_up(unsigned char*, LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, > LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, unsigned > char*) » : > liblte_security.cc:(.text+0x58d) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x5a9) : référence indéfinie vers > « mbedtls_md_hmac » > liblte_security.cc:(.text+0x5d5) : référence indéfinie vers > « mbedtls_md_info_from_type » > liblte_security.cc:(.text+0x5f1) : référence indéfinie vers > « mbedtls_md_hmac » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_128_eia2(unsigned char*, unsigned int, unsigned char, > unsigned char, unsigned char*, unsigned int, unsigned char*) » : > liblte_security.cc:(.text+0x6d6) : référence indéfinie vers > « mbedtls_aes_setkey_enc » > liblte_security.cc:(.text+0x6ef) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0xbbd) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0xd46) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction > « liblte_security_128_eia2(unsigned char*, unsigned int, unsigned char, > unsigned char, LIBLTE_BIT_MSG_STRUCT*, unsigned char*) » : > liblte_security.cc:(.text+0x1007) : référence indéfinie vers > « mbedtls_aes_setkey_enc » > liblte_security.cc:(.text+0x101c) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0x1e9e) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > liblte_security.cc:(.text+0x2033) : référence indéfinie vers > « mbedtls_aes_crypt_ecb » > collect2: error: ld returned 1 exit status > LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/build.make:545 : la recette > pour la cible « LTE_fdd_enodeb/LTE_fdd_enodeb » a échouée > make[2]: *** [LTE_fdd_enodeb/LTE_fdd_enodeb] Erreur 1 > CMakeFiles/Makefile2:961 : la recette pour la cible > « LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/all » a échouée > make[1]: *** [LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/all] Erreur 2 > Makefile:138 : la recette pour la cible « all » a échouée > make: *** [all] Erreur 2 > > > > Le 12/03/2018 à 18:40, Tomcsányi, Domonkos a écrit : > > Hi > > It is hard to help you without seeing the error message itself. > > Cheers, > Domi > > > 2018. márc. 12. dátummal, 17:43 időpontban guillaume tochou < > gui...@or...> írta: > > Hello, > > I'm new on the the mailing list and I'm trying to install openlte. > > I downloaded the last version (openlte_v00-20-05) and I also used the > patch (https://sourceforge.net/p/openlte/mailman/message/35039389/) that > allows to replace the polarssl package by the mbedtls package (I'm using > Ubuntu 16.04). But I'm having an error when doing make. > > Is anyone who succeed to install openlte with the patch on Ubuntu 16.04 ? > > Thanks > > Guillaume > > > <https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download> > <https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download> > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > |
|
From: <gui...@or...> - 2018-03-13 09:26:30
|
Hello, I have the following errors : [ 77%] Linking CXX executable LTE_fdd_enodeb ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_generate_k_asme(unsigned char*, unsigned char*, unsigned char*, unsigned char*, unsigned short, unsigned short, unsigned char*) » : liblte_security.cc:(.text+0x1c4) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x1e2) : référence indéfinie vers « mbedtls_md_hmac » ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_generate_k_enb(unsigned char*, unsigned int, unsigned char*) » : liblte_security.cc:(.text+0x2aa) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x2c6) : référence indéfinie vers « mbedtls_md_hmac » ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_generate_k_nas(unsigned char*, LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, unsigned char*) » : liblte_security.cc:(.text+0x36d) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x389) : référence indéfinie vers « mbedtls_md_hmac » liblte_security.cc:(.text+0x3b5) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x3d1) : référence indéfinie vers « mbedtls_md_hmac » ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_generate_k_rrc(unsigned char*, LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, unsigned char*) » : liblte_security.cc:(.text+0x47d) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x499) : référence indéfinie vers « mbedtls_md_hmac » liblte_security.cc:(.text+0x4c5) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x4e1) : référence indéfinie vers « mbedtls_md_hmac » ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_generate_k_up(unsigned char*, LIBLTE_SECURITY_CIPHERING_ALGORITHM_ID_ENUM, LIBLTE_SECURITY_INTEGRITY_ALGORITHM_ID_ENUM, unsigned char*, unsigned char*) » : liblte_security.cc:(.text+0x58d) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x5a9) : référence indéfinie vers « mbedtls_md_hmac » liblte_security.cc:(.text+0x5d5) : référence indéfinie vers « mbedtls_md_info_from_type » liblte_security.cc:(.text+0x5f1) : référence indéfinie vers « mbedtls_md_hmac » ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_128_eia2(unsigned char*, unsigned int, unsigned char, unsigned char, unsigned char*, unsigned int, unsigned char*) » : liblte_security.cc:(.text+0x6d6) : référence indéfinie vers « mbedtls_aes_setkey_enc » liblte_security.cc:(.text+0x6ef) : référence indéfinie vers « mbedtls_aes_crypt_ecb » liblte_security.cc:(.text+0xbbd) : référence indéfinie vers « mbedtls_aes_crypt_ecb » liblte_security.cc:(.text+0xd46) : référence indéfinie vers « mbedtls_aes_crypt_ecb » ../liblte/liblte.a(liblte_security.cc.o) : Dans la fonction « liblte_security_128_eia2(unsigned char*, unsigned int, unsigned char, unsigned char, LIBLTE_BIT_MSG_STRUCT*, unsigned char*) » : liblte_security.cc:(.text+0x1007) : référence indéfinie vers « mbedtls_aes_setkey_enc » liblte_security.cc:(.text+0x101c) : référence indéfinie vers « mbedtls_aes_crypt_ecb » liblte_security.cc:(.text+0x1e9e) : référence indéfinie vers « mbedtls_aes_crypt_ecb » liblte_security.cc:(.text+0x2033) : référence indéfinie vers « mbedtls_aes_crypt_ecb » collect2: error: ld returned 1 exit status LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/build.make:545 : la recette pour la cible « LTE_fdd_enodeb/LTE_fdd_enodeb » a échouée make[2]: *** [LTE_fdd_enodeb/LTE_fdd_enodeb] Erreur 1 CMakeFiles/Makefile2:961 : la recette pour la cible « LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/all » a échouée make[1]: *** [LTE_fdd_enodeb/CMakeFiles/LTE_fdd_enodeb.dir/all] Erreur 2 Makefile:138 : la recette pour la cible « all » a échouée make: *** [all] Erreur 2 Le 12/03/2018 à 18:40, Tomcsányi, Domonkos a écrit : > Hi > > It is hard to help you without seeing the error message itself. > > Cheers, > Domi > > > 2018. márc. 12. dátummal, 17:43 időpontban guillaume tochou > <gui...@or... <mailto:gui...@or...>> írta: > >> Hello, >> >> I'm new on the the mailing list and I'm trying to install openlte. >> >> I downloaded the last version (openlte_v00-20-05) and I also used the >> patch (https://sourceforge.net/p/openlte/mailman/message/35039389/) >> that allows to replace the polarssl package by the mbedtls package >> (I'm using Ubuntu 16.04). But I'm having an error when doing make. >> >> Is anyone who succeed to install openlte with the patch on Ubuntu >> 16.04 ? >> >> Thanks >> >> Guillaume >> >> <https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download><https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download> >> >> _________________________________________________________________________________________________________________________ >> >> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc >> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler >> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, >> Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. >> >> This message and its attachments may contain confidential or privileged information that may be protected by law; >> they should not be distributed, used or copied without authorisation. >> If you have received this email in error, please notify the sender and delete this message and its attachments. >> As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. >> Thank you. >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://Slashdot.org>! >> http://sdm.link/slashdot >> _______________________________________________ >> Openlte-discuss mailing list >> Ope...@li... >> <mailto:Ope...@li...> >> https://lists.sourceforge.net/lists/listinfo/openlte-discuss _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. |
|
From: Tomcsányi, D. <do...@to...> - 2018-03-12 18:40:37
|
Hi It is hard to help you without seeing the error message itself. Cheers, Domi 2018. márc. 12. dátummal, 17:43 időpontban guillaume tochou <gui...@or...> írta: > Hello, > > I'm new on the the mailing list and I'm trying to install openlte. > I downloaded the last version (openlte_v00-20-05) and I also used the patch (https://sourceforge.net/p/openlte/mailman/message/35039389/) that allows to replace the polarssl package by the mbedtls package (I'm using Ubuntu 16.04). But I'm having an error when doing make. > Is anyone who succeed to install openlte with the patch on Ubuntu 16.04 ? > Thanks > Guillaume > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > Thank you. > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss |
|
From: <gui...@or...> - 2018-03-12 16:42:50
|
Hello, I'm new on the the mailing list and I'm trying to install openlte. I downloaded the last version (openlte_v00-20-05) and I also used the patch (https://sourceforge.net/p/openlte/mailman/message/35039389/) that allows to replace the polarssl package by the mbedtls package (I'm using Ubuntu 16.04). But I'm having an error when doing make. Is anyone who succeed to install openlte with the patch on Ubuntu 16.04 ? Thanks Guillaume <https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download><https://sourceforge.net/projects/openlte/files/openlte_v00-20-05.tgz/download> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. |
|
From: Eugene B. <eug...@gm...> - 2017-12-21 16:09:23
|
Hi!
variable N_neg_RA_shift declared as uint32
and expression if(N_neg_RA_shift < 0) always false!
Maybe it's mistake ?
---------------------------------------------------------------
void prach_preamble_seq_gen(
...
uint32 N_neg_RA_shift;
...
// Determine N_RA_shift, d_start, N_RA_group, and N_neg_RA_shift
if(d_u >= N_cs && d_u < phy_struct->prach_N_zc/3)
{
N_RA_shift = d_u/N_cs;
d_start = 2*d_u + N_RA_shift*N_cs;
N_RA_group = phy_struct->prach_N_zc/d_start;
N_neg_RA_shift = (phy_struct->prach_N_zc - 2*d_u -
N_RA_group*d_start)/N_cs;
if(N_neg_RA_shift < 0)
{
N_neg_RA_shift = 0;
}
}
else
{
N_RA_shift = (phy_struct->prach_N_zc - 2*d_u)/N_cs;
d_start = phy_struct->prach_N_zc - 2*d_u +
N_RA_shift*N_cs;
N_RA_group = d_u/d_start;
N_neg_RA_shift = (d_u - N_RA_group*d_start)/N_cs;
if(N_neg_RA_shift < 0)
{
N_neg_RA_shift = 0;
}
if(N_neg_RA_shift > N_RA_shift)
{
N_neg_RA_shift = N_RA_shift;
}
}
--
*Yours faithfully,*
*Eugene Bogush.*
|
|
From: tides a. <tid...@ya...> - 2017-12-18 10:53:09
|
Hi List, I already have a working OpenLTE base station, and i can see that it's transmitting the signal. I'm using spectrum analyzer to see the graphical view of the signal. My question is, how the phone see the OpenLTE base station when i'm using manual search to the network selection. At this moment, i just want to see the OpenLTE network when i'm doing manual search with my phone. I'm following this link to configure the OpenLTE: https://sourceforge.net/p/openlte/wiki/Configuring%20OpenLTE%20eNodeB/ and i'm using USRP B200. Thanks & regards, Tides |
|
From: Tomcsányi D. <do...@to...> - 2017-11-09 20:29:36
|
Hi Pham, Hm, that is weird. In that case I guess we need to wait until Ben or someone else chimes in with their opinion. I use a software called srsUE which is partially based on openLTE and experience the same kind of "late"s, so if there is a fix for that it would be great. Cheers, Domi > 2017. nov. 9. dátummal, 19:51 időpontban V Pham <lc...@ou...> írta: > > Hi Domi. > > I am aware of the importance of CPU and PC power, and like you said, in general, SDR related SWs do need a lot of CPU power. > > However I have used the same laptop with i7 cpu to successfully run OAI, and achieved much higher data traffic throughput than in the case of OpenLTE. > > I believe there may be some logical issues with the openLTE code causing all these L's and Late DL/UL subframes from MAC to PHY. > > More discussions on this topic is appreciated > > Fra: Tomcsányi, Domonkos <do...@to...> > Sendt: 9. november 2017 19:19 > Til: V Pham > Emne: Re: [Openlte-discuss] Late DL/UL subframes and L's > > Hi, > > This is usually related to not enough powerful hardware. > > Cheers, > Domi > > > > 2017. nov. 9. dátummal, 10:34 időpontban V Pham <lc...@ou... <mailto:lc...@ou...>> írta: > >> Hi all >> >> I have done a lot of tests on OpenLTE lately, and experienced very poor performance on data traffic. Even just sending ping packets are difficult. >> >> What I observe is: >> >> 1) There are a lot of "error phy LTE_fdd_enb_phy.cc <http://lte_fdd_enb_phy.cc/> Late DL/UL subframe from MAC..." in the debug window. >> >> 2) There are a lot of L's in the application window. >> >> I believe these errors are the reason for the poor performance on data traffic, is this correct? And my question is what are the reason for 1) and 2), and are they related in anyway to each other? >> >> "Late DL subframe" is due late scheduling for DL packets from MAC to PHY, but what is actually "Late UL subframe"? From the source code, i.e. LTE_fdd_enb_phy.cc <http://lte_fdd_enb_phy.cc/>, the "Late UL subrame" is occuring inside the handle_phy_schedule function, which handles downlink traffic, is this correct? >> >> Hope someone can shed light on these questions. >> >> Best regards >> >> Pham >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot <http://sdm.link/slashdot>_______________________________________________ >> Openlte-discuss mailing list >> Ope...@li... <mailto:Ope...@li...> >> https://lists.sourceforge.net/lists/listinfo/openlte-discuss <https://lists.sourceforge.net/lists/listinfo/openlte-discuss> |
|
From: V P. <lc...@ou...> - 2017-11-09 09:33:43
|
Hi all I have done a lot of tests on OpenLTE lately, and experienced very poor performance on data traffic. Even just sending ping packets are difficult. What I observe is: 1) There are a lot of "error phy LTE_fdd_enb_phy.cc Late DL/UL subframe from MAC..." in the debug window. 2) There are a lot of L's in the application window. I believe these errors are the reason for the poor performance on data traffic, is this correct? And my question is what are the reason for 1) and 2), and are they related in anyway to each other? "Late DL subframe" is due late scheduling for DL packets from MAC to PHY, but what is actually "Late UL subframe"? From the source code, i.e. LTE_fdd_enb_phy.cc, the "Late UL subrame" is occuring inside the handle_phy_schedule function, which handles downlink traffic, is this correct? Hope someone can shed light on these questions. Best regards Pham |
|
From: Brien C. <xco...@gm...> - 2017-10-18 22:16:55
|
Hi, I'm looking for sample packet captures with LTE message so that I can see real message sequences. If anyone can share with me I would really appreciate it. Best, Brien |
|
From: Eugene B. <eug...@gm...> - 2017-10-13 09:02:05
|
Hi,
in func "liblte_rrc_pack_ue_capability_enquiry_msg" missed bit
"nonCriticalExtension"
Standard Specification Version: 3GPP TS36.331 Rel14 V14.1.0
Message name: DL-DCCH-Message
Message PDU(3octets):3A0000
DL-DCCH-Message:
message(DL-DCCH-MessageType):
3A 0....... DL-DCCH-MessageType = 0 :c1
.0111... c1 = 7 :ueCapabilityEnquiry
UECapabilityEnquiry:
RRC-TransactionIdentifier:
.....01. RRC-TransactionIdentifier = 1
.......0 criticalExtensions = 0 :c1
00 00...... c1 = 0 :ueCapabilityEnquiry-r8
UECapabilityEnquiry-r8-IEs:
..0..... nonCriticalExtension = 0 :Absent
UE-CapabilityRequest:
...000.. No. of UE-CapabilityRequest = 0 :0 + 1 = 1
RAT-Type:
......0. RAT-Type ENUMERATED value from = 0 :before
Extension marker
.......0 RAT-Type = 0 :eutra
00 00......
..000000 Spare Bits = 000000b
--
*Yours faithfully,*
*Eugene Bogush.*
|
|
From: Eugene B. <eug...@gm...> - 2017-10-02 18:38:18
|
In current time, func LTE_fdd_enb_gw::receive_thread(void *inputs) not work
correctly if input packet is IPv6.
If discarded ip-fragmentation next patch resolves it issue:
diff --git a/LTE_fdd_enodeb/src/LTE_fdd_enb_gw.cc
b/LTE_fdd_enodeb/src/LTE_fdd_enb_gw.cc
index df3d3ca..5f7eb17 100755
--- a/LTE_fdd_enodeb/src/LTE_fdd_enb_gw.cc
+++ b/LTE_fdd_enodeb/src/LTE_fdd_enb_gw.cc
@@ -278,7 +278,7 @@ void* LTE_fdd_enb_gw::receive_thread(void *inputs)
while(gw->is_started())
{
N_bytes = read(gw->tun_fd, &msg.msg[idx], LIBLTE_MAX_MSG_SIZE);
-
+ if(msg.msg[0]!=0x45) continue;//skip non ipv4 packets
if(N_bytes > 0)
{
msg.N_bytes = idx + N_bytes;
2017-09-29 12:14 GMT+03:00 V Pham <lc...@ou...>:
> Hi all.
>
>
> I have managed to install openLTE. The UE (smart phone) can successfully
> connect to the eNB, however it cannot reach the Internet.
>
>
> Looking at the LTE_fdd_enodeb_ip.pcap file, there are DNS requests sent
> from the UE, but no reply is returned back. I guess this is due to
> the traffic from openlte GW (tun_openlte) is not forwarded or bridged to
> the host computers network interface (enp0s25) with Internet connectivity.
> Can anyone who managed to connect UE to the Internet through openLTE please
> help.
>
>
> Any reply is greatly appreciated.
>
>
> Regards
>
>
> V. Pham
>
>
>
> Settings for my system is as follows:
>
>
> My system is as follows:
>
> Ubuntu 16.04
>
> Latest version of openLTE.
>
> SDR: USRP B210
>
> IP-address of host: 192.168.1.8
>
> IP-address of tun-openlte: 10.0.0.1
>
>
>
>
> iptables:
>
>
> Chain INPUT (policy ACCEPT 35510 packets, 28M bytes)
> pkts bytes target prot opt in out source
> destination
>
> Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
> pkts bytes target prot opt in out source
> destination
> 0 0 ACCEPT all -- tun_openlte enp0s25 0.0.0.0/0
> 0.0.0.0/0 ctstate NEW
> 0 0 ACCEPT all -- * * 0.0.0.0/0
> 0.0.0.0/0 ctstate RELATED,ESTABLISHED
>
> Chain OUTPUT (policy ACCEPT 35768 packets, 5413K bytes)
> pkts bytes target prot opt in out source
> destination
>
>
>
> routing table:
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> default 192.168.1.1 0.0.0.0 UG 100 0 0
> enp0s25
> link-local * 255.255.0.0 U 1000 0 0
> enp0s25
> 192.168.1.0 * 255.255.255.0 U 100 0 0
> enp0s25
>
>
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Openlte-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlte-discuss
>
>
--
*Yours faithfully,*
*Eugene Bogush.*
|
|
From: V P. <lc...@ou...> - 2017-09-29 09:14:34
|
Hi all.
I have managed to install openLTE. The UE (smart phone) can successfully connect to the eNB, however it cannot reach the Internet.
Looking at the LTE_fdd_enodeb_ip.pcap file, there are DNS requests sent from the UE, but no reply is returned back. I guess this is due to the traffic from openlte GW (tun_openlte) is not forwarded or bridged to the host computers network interface (enp0s25) with Internet connectivity. Can anyone who managed to connect UE to the Internet through openLTE please help.
Any reply is greatly appreciated.
Regards
V. Pham
Settings for my system is as follows:
My system is as follows:
Ubuntu 16.04
Latest version of openLTE.
SDR: USRP B210
IP-address of host: 192.168.1.8
IP-address of tun-openlte: 10.0.0.1
iptables:
Chain INPUT (policy ACCEPT 35510 packets, 28M bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- tun_openlte enp0s25 0.0.0.0/0 0.0.0.0/0 ctstate NEW
0 0 ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED
Chain OUTPUT (policy ACCEPT 35768 packets, 5413K bytes)
pkts bytes target prot opt in out source destination
routing table:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.1 0.0.0.0 UG 100 0 0 enp0s25
link-local * 255.255.0.0 U 1000 0 0 enp0s25
192.168.1.0 * 255.255.255.0 U 100 0 0 enp0s25
|
|
From: V P. <lc...@ou...> - 2017-08-29 09:05:59
|
Hi all. In the final step when installing openlte, i.e. using the "sudo make install" command, the following messages appear: Install the project... -- Install configuration: "Release" -- Installing: /usr/local/lib/libLTE_fdd_dl_fg.so -- Installing: /usr/local/lib/libLTE_fdd_dl_fs.so -- Installing: /usr/local/bin/LTE_fdd_dl_scan -- Set runtime path of "/usr/local/bin/LTE_fdd_dl_scan" to "" -- Installing: /usr/local/bin/LTE_file_recorder -- Set runtime path of "/usr/local/bin/LTE_file_recorder" to "" -- Installing: /usr/local/bin/LTE_fdd_enodeb Using interface : enp0s25 net.ipv4.ip_forward = 1 iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. Are the last 3 lines a problem? In case yes, what should I do? Regards Vinh |
|
From: Oscar L. <jar...@gm...> - 2017-08-28 14:08:11
|
Hi guys I was helping a friend to install openlte on his laptop and we got the error on the attached file after doing the make command. UHD and Gnuradio installation was done according to https://kb.ettus.com/Building_and_Installing_the_USRP_Open-Source_Toolchain_(UHD_and_GNU_Radio)_on_Linux And UHD version is 3.10 and Gnuradio 3.7.10. Also we first installed polarssl 1.3.0 version and then last mbedtls version from tls.mbed.org I should quote that cmake output is clean ... it claims not to find polarssl package but it finds it because it shows the path to polarssl file. However, from the log on the attached file, it seems that there is some problem with polarssl. Any help will be appreciated Thanks |
|
From: Eugene B. <eug...@gm...> - 2017-08-23 17:58:47
|
ubuntu 16.04/b210 linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_003.010.001.001-79- g7ac01c7f *** LTE FDD ENB *** Please connect to control port 30000 ... -- Performing timer loopback test... pass Segmentation fault (core dumped) ----------------------------------------------------------------------- [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `./LTE_fdd_enodeb'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00000000004c8bc8 in to_string[abi:cxx11](unsigned char*, unsigned int) () [Current thread is 1 (Thread 0x7f6f031a2700 (LWP 6635))] (gdb) bt #0 0x00000000004c8bc8 in to_string[abi:cxx11](unsigned char*, unsigned int) () #1 0x0000000000409def in LTE_fdd_enb_interface::send_ debug_msg(LTE_FDD_ENB_DEBUG_TYPE_ENUM, LTE_FDD_ENB_DEBUG_LEVEL_ENUM, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, LIBLTE_BYTE_MSG_STRUCT*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, ...) () #2 0x0000000000456b35 in LTE_fdd_enb_gw::handle_gw_ data(LTE_FDD_ENB_GW_DATA_READY_MSG_STRUCT*) () #3 0x0000000000457079 in void LTE_fdd_enb_msgq_cb_wrapper<LTE_fdd_enb_gw, <E_fdd_enb_gw::handle_pdcp_msg>(void*, LTE_FDD_ENB_MESSAGE_STRUCT&) () #4 0x000000000041d061 in LTE_fdd_enb_msgq::receive_thread(void*) () #5 0x00007f6f097426ba in start_thread (arg=0x7f6f031a2700) at pthread_create.c:333 #6 0x00007f6f079a33dd in clone () at ../sysdeps/unix/sysv/linux/ x86_64/clone.S:109 ------------------------------------------------------------------------------------------------- 08/23/2017 12:56:18.044508 info mac LTE_fdd_enb_mac.cc 532 Clearing HARQ info RNTI=62 TTI=3641 08/23/2017 12:56:18.044529 info mac LTE_fdd_enb_mac.cc 596 PUCCH SR received for 3641 RNTI=62 08/23/2017 12:56:18.044538 info mac LTE_fdd_enb_mac.cc 1140 UL scheduled (mcs=0, tbs=88, N_prb=4) for RNTI=62, UL_QUEUE_SIZE=1 08/23/2017 12:56:18.044624 info mac LTE_fdd_enb_mac.cc 1407 DL allocation (mcs=0, tbs=32, N_prb=2) sent for RNTI=62 CURRENT_TTI=3648 3F030074 08/23/2017 12:56:18.044641 info mac LTE_fdd_enb_mac.cc 1500 UL allocation sent for RNTI=62 CURRENT_TTI=3652 08/23/2017 12:56:18.055586 info mac LTE_fdd_enb_mac.cc 521 PUCCH ACK/NACK received for 3652 RNTI=62 08/23/2017 12:56:18.055611 info mac LTE_fdd_enb_mac.cc 561 Resending HARQ info RNTI=62 TTI=3652 (1) 08/23/2017 12:56:18.055793 info mac LTE_fdd_enb_mac.cc 1407 DL allocation (mcs=0, tbs=32, N_prb=2) sent for RNTI=62 CURRENT_TTI=3659 3F030074 08/23/2017 12:56:18.066500 info mac LTE_fdd_enb_mac.cc 521 PUCCH ACK/NACK received for 3663 RNTI=62 08/23/2017 12:56:18.066518 info mac LTE_fdd_enb_mac.cc 532 Clearing HARQ info RNTI=62 TTI=3663 08/23/2017 12:56:19.344564 info mac LTE_fdd_enb_mac.cc 596 PUCCH SR received for 4941 RNTI=62 08/23/2017 12:56:19.344589 info mac LTE_fdd_enb_mac.cc 1140 UL scheduled (mcs=0, tbs=88, N_prb=4) for RNTI=62, UL_QUEUE_SIZE=1 08/23/2017 12:56:19.344655 info mac LTE_fdd_enb_mac.cc 1500 UL allocation sent for RNTI=62 CURRENT_TTI=4952 08/23/2017 12:56:19.355527 info mac LTE_fdd_enb_mac.cc 624 PUSCH decode for RNTI=62 CURRENT_TTI=4952 3D0399981F79056170706C 08/23/2017 12:56:19.355546 info mac LTE_fdd_enb_mac.cc 957 Received short BSR for LCG_ID=2 (376 < Buffer Size <= 440), C_RNTI=62 08/23/2017 12:56:19.355556 info mac LTE_fdd_enb_mac.cc 1140 UL scheduled (mcs=2, tbs=424, N_prb=10) for RNTI=62, UL_QUEUE_SIZE=1 08/23/2017 12:56:19.355563 info mac LTE_fdd_enb_mac.cc 844 Handling ULSCH DCCH_SDU for RNTI=62, LCID=3 981F79056170706C 08/23/2017 12:56:19.355591 error mac LTE_fdd_enb_mac.cc 1134 Can't schedule UL 08/23/2017 12:56:19.355614 info rlc LTE_fdd_enb_rlc.cc 273 Received PDU for RNTI=62 and RB=DRB1 981F79056170706C 08/23/2017 12:56:19.355629 info rlc LTE_fdd_enb_rlc.cc 488 Received AMD PDU for RNTI=62, RB=DRB1, VR(R)=29, SN=31, VR(MR)=512, VR(H)=29, RF=AMD PDU, P=Status Report Not Requested, FI=Middle SDU Segment 79056170706C 08/23/2017 12:56:19.355640 info rlc LTE_fdd_enb_rlc.cc 835 Sending STATUS PDU for RNTI=62, RB=DRB1 00820EC0F0 08/23/2017 12:56:19.355660 info mac LTE_fdd_enb_mac.cc 1500 UL allocation sent for RNTI=62 CURRENT_TTI=4963 08/23/2017 12:56:19.355694 info mac LTE_fdd_enb_mac.cc 693 Received SDU for RNTI=62 and RB=DRB1 00820EC0F0 08/23/2017 12:56:19.355709 info mac LTE_fdd_enb_mac.cc 750 PDU scheduled for RNTI=62, DL_QUEUE_SIZE=1 08/23/2017 12:56:19.356518 info mac LTE_fdd_enb_mac.cc 1407 DL allocation (mcs=0, tbs=56, N_prb=3) sent for RNTI=62 CURRENT_TTI=4960 3F0300820EC0F0 08/23/2017 12:56:19.366898 info mac LTE_fdd_enb_mac.cc 624 PUSCH decode for RNTI=62 CURRENT_TTI=4963 039C2000A06503636F6D0000010001 80124500004C1D3C000040118BAAC0A8010308080808CFBA003500386AEE830E010000010000 08/23/2017 12:56:19.366918 info mac LTE_fdd_enb_mac.cc 844 Handling ULSCH DCCH_SDU for RNTI=62, LCID=3 9C2000A06503636F6D000001000180 124500004C1D3C000040118BAAC0A8010308080808CFBA003500386AEE830E010000010000 08/23/2017 12:56:19.366950 info mac LTE_fdd_enb_mac.cc 1140 UL scheduled (mcs=2, tbs=424, N_prb=10) for RNTI=62, UL_QUEUE_SIZE=1 08/23/2017 12:56:19.366970 info rlc LTE_fdd_enb_rlc.cc 273 Received PDU for RNTI=62 and RB=DRB1 9C2000A06503636F6D000001000180 124500004C1D3C000040118BAAC0A8010308080808CFBA003500386AEE830E010000010000 08/23/2017 12:56:19.366986 info rlc LTE_fdd_enb_rlc.cc 488 Received AMD PDU for RNTI=62, RB=DRB1, VR(R)=29, SN=32, VR(MR)=512, VR(H)=32, RF=AMD PDU, P=Status Report Not Requested, FI=Last SDU Segment 6503636F6D0000010001 08/23/2017 12:56:19.366997 info rlc LTE_fdd_enb_rlc.cc 835 Sending STATUS PDU for RNTI=62, RB=DRB1 00860EC0F0 08/23/2017 12:56:19.367021 info mac LTE_fdd_enb_mac.cc 1500 UL allocation sent for RNTI=62 CURRENT_TTI=4974 08/23/2017 12:56:19.367045 info mac LTE_fdd_enb_mac.cc 693 Received SDU for RNTI=62 and RB=DRB1 00860EC0F0 08/23/2017 12:56:19.367062 info mac LTE_fdd_enb_mac.cc 750 PDU scheduled for RNTI=62, DL_QUEUE_SIZE=1 08/23/2017 12:56:19.367071 info rlc LTE_fdd_enb_rlc.cc 488 Received AMD PDU for RNTI=62, RB=DRB1, VR(R)=29, SN=32, VR(MR)=512, VR(H)=32, RF=AMD PDU, P=Status Report Not Requested, FI=First SDU Segment 80124500004C1D3C000040118BAAC0A8010308080808CFBA003500386AEE830E010000010000 08/23/2017 12:56:19.367096 info rlc LTE_fdd_enb_rlc.cc 835 Sending STATUS PDU for RNTI=62, RB=DRB1 00860EC0F0 08/23/2017 12:56:19.367140 info mac LTE_fdd_enb_mac.cc 693 Received SDU for RNTI=62 and RB=DRB1 00860EC0F0 08/23/2017 12:56:19.367156 info mac LTE_fdd_enb_mac.cc 750 PDU scheduled for RNTI=62, DL_QUEUE_SIZE=2 08/23/2017 12:56:19.367392 info mac LTE_fdd_enb_mac.cc 521 PUCCH ACK/NACK received for 4964 RNTI=62 08/23/2017 12:56:19.367401 info mac LTE_fdd_enb_mac.cc 532 Clearing HARQ info RNTI=62 TTI=4964 08/23/2017 12:56:19.367487 info mac LTE_fdd_enb_mac.cc 1407 DL allocation (mcs=0, tbs=56, N_prb=3) sent for RNTI=62 CURRENT_TTI=4971 3F0300860EC0F0 08/23/2017 12:56:19.367505 info mac LTE_fdd_enb_mac.cc 1407 DL allocation (mcs=0, tbs=56, N_prb=3) sent for RNTI=62 CURRENT_TTI=4971 3F0300860EC0F0 08/23/2017 12:56:19.377811 info mac LTE_fdd_enb_mac.cc 624 PUSCH decode for RNTI=62 CURRENT_TTI=4974 039C1D00606D000001000180114500 004063E700004011450BC0A8010308080808F88D0035002C5CD6123201000001000000000000 08/23/2017 12:56:19.377831 info mac LTE_fdd_enb_mac.cc 844 Handling ULSCH DCCH_SDU for RNTI=62, LCID=3 9C1D00606D00000100018011450000 4063E700004011450BC0A8010308080808F88D0035002C5CD6123201000001000000000000 08/23/2017 12:56:19.377863 info mac LTE_fdd_enb_mac.cc 1140 UL scheduled (mcs=2, tbs=424, N_prb=10) for RNTI=62, UL_QUEUE_SIZE=1 08/23/2017 12:56:19.377883 info rlc LTE_fdd_enb_rlc.cc 273 Received PDU for RNTI=62 and RB=DRB1 9C1D00606D00000100018011450000 4063E700004011450BC0A8010308080808F88D0035002C5CD6123201000001000000000000 08/23/2017 12:56:19.377898 info rlc LTE_fdd_enb_rlc.cc 488 Received AMD PDU for RNTI=62, RB=DRB1, VR(R)=29, SN=29, VR(MR)=512, VR(H)=33, RF=AMD PDU, P=Status Report Not Requested, FI=Last SDU Segment 6D0000010001 08/23/2017 12:56:19.377936 info mac LTE_fdd_enb_mac.cc 1500 UL allocation sent for RNTI=62 CURRENT_TTI=4985 08/23/2017 12:56:19.377962 info pdcp LTE_fdd_enb_pdcp.cc 239 Received PDU for RNTI=62 and RB=DRB1 8010450000478356000040112595C0 A8010308080808DEC100350033E4452C02010000010000000000000A696E 69742D70303173740470757368056170706C6503636F6D0000010001 08/23/2017 12:56:19.377984 info rlc LTE_fdd_enb_rlc.cc 835 Sending STATUS PDU for RNTI=62, RB=DRB1 00860F4100 08/23/2017 12:56:19.378014 info rlc LTE_fdd_enb_rlc.cc 488 Received AMD PDU for RNTI=62, RB=DRB1, VR(R)=29, SN=29, VR(MR)=512, VR(H)=33, RF=AMD PDU, P=Status Report Not Requested, FI=First SDU Segment 80114500004063E700004011450BC0A8010308080808F88D0035002C5CD6 123201000001000000000000 08/23/2017 12:56:19.378034 info pdcp LTE_fdd_enb_pdcp.cc 239 Received PDU for RNTI=62 and RB=DRB1 6503636F6D0000010001 08/23/2017 12:56:19.378050 info gw LTE_fdd_enb_gw.cc 238 Received GW data message for RNTI=62 and RB=DRB1 450000478356000040112595C0A801 0308080808DEC100350033E4452C02010000010000000000000A696E6974 2D70303173740470757368056170706C6503636F6D0000010001 08/23/2017 12:56:19.378074 info rlc LTE_fdd_enb_rlc.cc 835 Sending STATUS PDU for RNTI=62, RB=DRB1 00860F4100 08/23/2017 12:56:19.378086 info mac LTE_fdd_enb_mac.cc 693 Received SDU for RNTI=62 and RB=DRB1 00860F4100 Connection closed by foreign host. -- *Yours faithfully,* *Eugene Bogush.* -- *Yours faithfully,* *Eugene Bogush.* |
|
From: Ben W. <bwo...@gm...> - 2017-08-06 00:14:08
|
+openlte-discuss HI Mateusz, I am not currently pursuing this at this time. But I'd be happy to accept patches if you are interested in pursing the work. Thanks, Ben On Mon, Mar 13, 2017 at 1:02 AM, Mateusz Kramarczyk <kra...@gm...> wrote: > Hi Ben, > > Do you consider adding LimeSDR (limesdr.org) to supported devices? > Lime is a new OSHW SDR, relatively cheap with parameters similar to USRP > B2XX. > It is also UHD-enabled. > Thanks. > > -- > Best Regards, > Mateusz Kramarczyk > |
|
From: Ben W. <bwo...@gm...> - 2017-08-06 00:13:13
|
Kia, Currently LTE_fdd_enodeb is FDD only, so band 42 will not work. I recommend trying to run one of the FDD bands that your Galaxy S7 supports. Monitoring the output on localhost TCP port 30001 will provide more details for debugging. Thanks, Ben On Mon, Apr 3, 2017 at 11:26 AM, Kia Rodriguez <kro...@fi...> wrote: > Hi, > > I am testing a Galaxy S7 on band 42, but it seems as though there is no > connectivity with the eNodeB. I have the IMSI, MNC,MCC, and ki from the > SIM card. It appears to say that there is an error between the MAC and > PHY. I have to test later today, so I can reply with a formal log. > > Has anyone been able to resolve this issue? > > -- > > *Kia* > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > |
|
From: Ben W. <bwo...@gm...> - 2017-08-06 00:11:35
|
Hi David, The LTE_fdd_enodeb and LTE_fdd_dl_scan applications both write pcap files out (/tmp/LTE_fdd_enodeb.pcap and /tmp/LTE_fdd_enodeb_ip.pcap for LTE_fdd_enodeb and /tmp/LTE_fdd_dl_scan.pcap for LTE_fdd_dl_scan), but they do not currently support live sending messages to localhost. Thanks, Ben On Wed, Apr 5, 2017 at 7:14 AM, David <da...@sl...> wrote: > Hello, > > I read that openlte is capable of sending MAC messages (live) to 127.0.0.1 > with GSMTAP header > https://sourceforge.net/p/openlte/mailman/message/33252654/ > > I just cannot figure out how to activate this ...? like in OpenBTS, one > can simply activate the feature by doing > config Control.GSMTAP.GSM 1 > > Thanks > Regards > > -- > David > PGP Fingerprint: A682 0841 3CAB E1C3 99BF 9D66 92F0 C5B7 0FBE 4A22 > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Openlte-discuss mailing list > Ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlte-discuss > > |
31 messages has been excluded from this view by a project administrator.