[srslte-users] Connect UE to Internet by eNB.

Piotr Kulesza piotr.kulesza.1998.praca at gmail.com
Mon Oct 7 08:55:30 UTC 2019


Hi,

Was my previous data message sufficient or should I add something else? I
ask because I still
haven't found a solution to my problem. Maybe the reason for this problem
is that the interface
connected to the internet has a static IP address set? This is unlikely in
my opinion but is it possible?
If the script indicating the internet interface for eNB worked, should any
statement show up on the eNB
or EPC console? If so, what does he look like?

I will be grateful for any help.

_____
Piotr




wt., 24 wrz 2019 o 15:50 Piotr Kulesza <piotr.kulesza.1998.praca at gmail.com>
napisał(a):

> Hi,
>
> This is what my internet-connected interface looks like:
>
> *eno1*      Link encap:Ethernet  HWaddr 1c:69:7a:00:85:96
>               inet addr:10.10.35.202  Bcast:10.10.35.255
>  Mask:255.255.255.0
>               inet6 addr: fe80::f949:d419:8309:80ad/64 Scope:Link
>               UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>               RX packets:5113 errors:0 dropped:64 overruns:0 frame:0
>               TX packets:2455 errors:0 dropped:0 overruns:0 carrier:0
>               collisions:0 txqueuelen:1000
>               RX bytes:6775521 (6.7 MB)  TX bytes:186627 (186.6 KB)
>               Interrupt:16 Memory:c0a00000-c0a20000
>
>
> This is how I start the srsepc_if_masq script:
>
> * sudo srsepc_if_masq.sh eno1*
>
> Pings printout from an UE computer:
>
> eupc01 at eupc01-All-Series:~$* ping 172.16.0.1*
> PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data.
> 64 bytes from 172.16.0.1: icmp_seq=1 ttl=64 time=495 ms
> 64 bytes from 172.16.0.1: icmp_seq=2 ttl=64 time=34.5 ms
> 64 bytes from 172.16.0.1: icmp_seq=3 ttl=64 time=32.9 ms
> ^C
> --- 172.16.0.1 ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
> rtt min/avg/max/mdev = 32.998/187.657/495.468/217.656 ms
> eupc01 at eupc01-All-Series:~$ *ping 8.8.8.8*
> connect: Network is unreachable
> eupc01 at eupc01-All-Series:~$ *ping google.com <http://google.com>*
> ping: unknown host google.com
>
> As you can see I can connect to SPGW but not to 8.8.8.8 or Google.
>
> pon., 23 wrz 2019 o 17:44 Pedro Alvarez <
> pedro.alvarez at softwareradiosystems.com> napisał(a):
>
>> Hum... If you ran the srsepc_if_masq script correctly, I would say the
>> most likely issue is either DNS or firewalling.
>>
>> To be sure, can you ping the SPGW? This will let us know if the LTE
>> connection is ok.
>> Can you ping 8.8.8.8? This will let us know if the packet forwarding is
>> ok.
>> Can you ping google.com? This will let us know if the DNS is ok.
>>
>> Regards,
>> Pedro
>>
>>
>> On Mon, Sep 23, 2019 at 11:36 AM Piotr Kulesza
>> <piotr.kulesza.1998.praca at gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > As you said, I disconnected the Ethernet cable and turned off wifi.
>> Unfortunately, the internet is still down. I would like to ask for
>> > some additional hints about what may cause the blockade of the
>> Internet. If routing is needed, could someone send a link to a
>> > simple tutorial?
>> >
>> > I additionally send a printout from ifconfig UE PC:
>> >
>> > tun_srsue Link encap:UNSPEC  HWaddr
>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>> >           inet addr:172.16.0.4  P-t-P:172.16.0.4  Mask:255.255.255.0
>> >           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>> >           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
>> >           collisions:0 txqueuelen:500
>> >           RX bytes:0 (0.0 B)  TX bytes:48 (48.0 B)
>> >
>> > Printout from UE srsLTE:
>> >
>> > Reading configuration file /home/eupc01/.config/srslte/ue.conf...
>> >
>> > Built in Release mode using commit c4bcd6e on branch master.
>> >
>> > Opening 1 RF devices with 1 RF channels...
>> > [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800;
>> UHD_3.14.1.0-release
>> > [INFO] [LOGGING] Fastpath logging disabled at runtime.
>> > Opening USRP with args: type=b200,master_clock_rate=23.04e6
>> > [INFO] [B200] Detected Device: B210
>> > [INFO] [B200] Operating over USB 3.
>> > [INFO] [B200] Initialize CODEC control...
>> > [INFO] [B200] Initialize Radio control...
>> > [INFO] [B200] Performing register loopback test...
>> > [INFO] [B200] Register loopback test passed
>> > [INFO] [B200] Performing register loopback test...
>> > [INFO] [B200] Register loopback test passed
>> > [INFO] [B200] Asking for clock rate 23.040000 MHz...
>> > [INFO] [B200] Actually got clock rate 23.040000 MHz.
>> > Waiting PHY to initialize ... done!
>> > Attaching UE...
>> > Searching cell in DL EARFCN=3400, f_dl=2685.0 MHz, f_ul=2565.0 MHz
>> > .
>> > Found Cell:  Mode=FDD, PCI=1, PRB=50, Ports=1, CFO=0.1 KHz
>> > Found PLMN:  Id=00101, TAC=7
>> > Random Access Transmission: seq=40, ra-rnti=0x2
>> > Random Access Transmission: seq=5, ra-rnti=0x2
>> > Random Access Complete.     c-rnti=0x67, ta=8
>> > RRC Connected
>> > Network attach successful. IP: 172.16.0.4
>> > Software Radio Systems LTE (srsLTE)
>> > Received RRC Connection Release
>> > RRC IDLE
>> > /home/eupc01/srsLTE/lib/src/phy/phch/ra_dl.c.660: Configuring resource
>> allocation
>> >
>> >
>> > .
>> > Found Cell:  Mode=FDD, PCI=1, PRB=50, Ports=1, CFO=-0.1 KHz
>> > ...
>> > Found Cell:  Mode=FDD, PCI=1, PRB=50, Ports=1, CFO=-0.4 KHz
>> > The condition lb <= n <= ub (0 <= 11 <= 9) was not met
>> > [/home/eupc01/srsLTE/lib/include/srslte/asn1/asn1_utils.h][753]
>> Decoding failure.
>> > [/home/eupc01/srsLTE/lib/src/asn1/rrc_asn1.cc][79954] Decoding failure.
>> > [/home/eupc01/srsLTE/lib/src/asn1/rrc_asn1.cc][80019] Decoding failure.
>> > [/home/eupc01/srsLTE/lib/include/srslte/asn1/asn1_utils.h][765]
>> Decoding failure.
>> > [/home/eupc01/srsLTE/lib/src/asn1/rrc_asn1.cc][80100] Decoding failure.
>> > [/home/eupc01/srsLTE/lib/src/asn1/rrc_asn1.cc][80255] Decoding failure.
>> > [/home/eupc01/srsLTE/lib/src/asn1/rrc_asn1.cc][80230] Decoding failure.
>> > [/home/eupc01/srsLTE/lib/src/asn1/rrc_asn1.cc][80270] Decoding failure.
>> >
>> > And printout from eNB srsLTE:
>> >
>> > Built in Release mode using commit 3d9baeb on branch agent.
>> >
>> > ---  Software Radio Systems LTE eNodeB  ---
>> >
>> > Reading configuration file enb.conf...
>> > [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800;
>> UHD_3.14.1.HEAD-0-g98c7c986
>> > [INFO] [B200] Loading firmware image:
>> /usr/local/share/uhd/images/usrp_b200_fw.hex...
>> > Opening USRP with args: type=b200,master_clock_rate=30.72e6
>> > [INFO] [B200] Detected Device: B200
>> > [INFO] [B200] Loading FPGA image:
>> /usr/local/share/uhd/images/usrp_b200_fpga.bin...
>> > [INFO] [B200] Operating over USB 3.
>> > [INFO] [B200] Detecting internal GPSDO....
>> > [INFO] [GPS] No GPSDO found
>> > [INFO] [B200] Initialize CODEC control...
>> > [INFO] [B200] Initialize Radio control...
>> > [INFO] [B200] Performing register loopback test...
>> > [INFO] [B200] Register loopback test passed
>> > [INFO] [B200] Asking for clock rate 30.720000 MHz...
>> > [INFO] [B200] Actually got clock rate 30.720000 MHz.
>> > Setting frequency: DL=2685.0 Mhz, UL=2565.0 MHz
>> > [INFO] [B200] Asking for clock rate 11.520000 MHz...
>> > [INFO] [B200] Actually got clock rate 11.520000 MHz.
>> > Setting Sampling frequency 11.52 MHz
>> >
>> > ==== eNodeB started ===
>> > Type <t> to view trace
>> > RACH:  tti=1151, preamble=7, offset=3, temp_crnti=0x46
>> > RACH:  tti=1151, preamble=10, offset=8, temp_crnti=0x49
>> > RACH:  tti=1151, preamble=13, offset=13, temp_crnti=0x4c
>> > Disconnecting rnti=0x46.
>> > Disconnecting rnti=0x4c.
>> > User 0x49 connected
>> > Disconnecting rnti=0x49.
>> > RACH:  tti=5081, preamble=44, offset=3, temp_crnti=0x4f
>> > RACH:  tti=5081, preamble=47, offset=8, temp_crnti=0x52
>> > Disconnecting rnti=0x4f.
>> > Disconnecting rnti=0x52.
>> > RACH:  tti=1951, preamble=35, offset=3, temp_crnti=0x55
>> > RACH:  tti=1951, preamble=38, offset=8, temp_crnti=0x58
>> > RACH:  tti=1951, preamble=41, offset=13, temp_crnti=0x5b
>> > RACH:  tti=1971, preamble=0, offset=8, temp_crnti=0x5e
>> > Disconnecting rnti=0x55.
>> > Disconnecting rnti=0x58.
>> > Disconnecting rnti=0x5b.
>> > User 0x5e connected
>> > RACH:  tti=6911, preamble=40, offset=8, temp_crnti=0x61
>> > RACH:  tti=6911, preamble=43, offset=13, temp_crnti=0x64
>> > Disconnecting rnti=0x61.
>> > RACH:  tti=6961, preamble=5, offset=8, temp_crnti=0x67
>> > Disconnecting rnti=0x64.
>> > User 0x67 connected
>> > Disconnecting rnti=0x5e.
>> > Disconnecting rnti=0x67.
>> >
>> > czw., 19 wrz 2019 o 10:16 Andre Puschmann <
>> andre.puschmann at softwareradiosystems.com> napisał(a):
>> >>
>> >> Hi,
>> >>
>> >> On 18/9/19 15:09, Piotr Kulesza wrote:
>> >> > Hi,
>> >> >
>> >> > I'm trying to connect my UE created via srsue to the internet. UE and
>> >> > eNB are able to see each other and I am able to ping them. For now I
>> >> > have done this:
>> >> > 1) I installed resolvconf and I saved in a
>> >> > file/etc/resolvconf/resolv.conf.d/headwhat follows:
>> >> > nameserver 8.8.4.4
>> >> > nameserver 8.8.8.8
>> >> > 2) I started ./srsepc_if_masq.sh <My Interface connected to Internet>
>> >> >
>> >> > Do I have to do anything else to connect to the Internet through the
>> UE?
>> >> > Any additional changes to the configuration files?
>> >>
>> >> No. Once you have a connection to the core it's all fine on the LTE
>> >> side. From now on, it's a Linux IP routing issue.
>> >>
>> >> Note that the default route for IPs outside of your LTE network is
>> >> probably going through Wifi or Ethernet and not through the tun that
>> the
>> >> UE creates.
>> >>
>> >> Make sure that the default route is over the tun. If you are not
>> >> familiar with route and friend, try disabling all other network
>> connections.
>> >>
>> >> Cheers
>> >> Andre
>> >
>> > _______________________________________________
>> > srslte-users mailing list
>> > srslte-users at lists.softwareradiosystems.com
>> > http://www.softwareradiosystems.com/mailman/listinfo/srslte-users
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.srsran.com/pipermail/srsran-users/attachments/20191007/23724c0f/attachment.htm>


More information about the srsran-users mailing list