Network discovery takes very long time

Bigtroll001

NEBULA NR5101.

Server in speedtest.net takes extremely long time to discover. 30 - 45 seconds. Sometimes it also take very long time to connect to a new random URL.

It is not the 5G network taking the time.

The same 5G network is testet on my Samsung S21 5G. Server discovery on speedtest.net and connecting to a new / random URL takes less than a second.

Once the NEBULA NR5101 is connected, the DL/UL speed is a little slower than the Samsung S21. Usually it's between 150-500mbit DL / 75-150mbit UL. I have a few times seen download speed exceeding 1Gbit on the Samsung.

The 2 units runs on same 5G NR-NSA network
The 2 units gets the same DNS1/DNS2 server addresses.

I have tried swapping SIM between units and the same result occurs.

Any ideas why the NEBULA NR5101 takes so long time for network connection / server discovery and why its slower than the Samsung S21?

Zyxel_Bella

Hi @Bigtroll001

 

Although they both supports 5G NR/4G LTE, but service band is based on device’s supports frequencies when you did test on two devices may be not the same. We will consider its really time signal to measure if the result is expectable.

 

And NR5101 is not only network router, but it also combines WLAN AP, LAN gateway. The purpose of the products definition are quite different, the difference will be there between hardware specifications such as antenna design/pattern. In general, mobile phones are usually have better performance than mobile routers.

 

The speedtest website uses random server for each test and user couldn’t get the path information of the hops within device and server. The value can be easily interfered by lots of factors, and cause users not to look at results objectively. We suggest to consider the result as a reference.

 

Thank you

 

Regards,

Bella

 

Bigtroll001

"We suggest to consider the result as a reference."

I dont buy the explanation

The 2 unit are operating on same band 78 (3500Mhz). 
Test on Nebula NR5101 is performed without any load from other units than the one performing the test
Test on NR5101 has also been performed with WiFi on unit disabled. Same result
Same result on NR5101 connected via LAN and via WiFi
No impact from distance disturbances as Mobile Operators Gateway antenne is app. 200meters away
I have also tried to alter the security level on the firewall. Result stays the same.

It is rather obvious to me that the NR5101 is blocking the connection. I just cannot figure out how.

Bigtroll001

Further elemination of possible errors.

Tests performed against 2 different speed testing sites on 2 different browsers. Same results on all 4 scenarios.

Nebula NR5101 takes 30 - 45 seconds for server discovery. My Samsung S21 takes less than 1 second.

The 2 sites could however potentially use same server discovery method

Zyxel_Bella

Hi @Bigtroll001

 

If you could confirm two devices are using same band for example n78, could you get the signal value of RSRP, RSRQ, SINR and RSSI on each device?

Or Screenshot web GUI Cellular WAN Status page including above information let we check it.  (access GUI > System Monitor > Cellular WAN Status)

Thank you

 

Regards,

Bella

Bigtroll001

The information have been obtained while the units were in exact samt location 5cm apart.

The info from the Samsung were from APP "LTE discovery"

Zyxel_Bella

Hi @Bigtroll001

 

Both devices signal look fine at the moment.

If you’re both using OiSTER ISP SIM card, ensure each test connecting to same based station.

Do a trace route to help clarify destination IP address, hops information.

 

Thank you

 

Regards,

Bella

 

Bigtroll001

Attached a trace router to support.zyxel.eu. Timeout after 192.168.1.1. I have tried several other locations, and they all time out after 192.168.1.1

Bigtroll001

And here's the trace route to speedtest including the nslookup. Same problem with timeout after 192.168.1.1

Bigtroll001

And heres the trace router executed from nebula admin URL

• traceroute to speedtest.net (151.101.194.219), 32 hops max, 38 byte packets
• 1 * * *
• 2 10.66.201.33 (10.66.201.33) 24.666 ms 10.406 ms 15.789 ms
• 3 172.18.82.33 (172.18.82.33) 10.239 ms 11.488 ms 11.330 ms
• 4 10.66.199.1 (10.66.199.1) 10.754 ms 15.088 ms 14.221 ms
• 5 10.66.201.170 (10.66.201.170) 10.585 ms 9.660 ms 16.318 ms
• 6 95.209.204.252 (95.209.204.252) 11.114 ms 9.660 ms 15.771 ms
• 7 10.66.190.9 (10.66.190.9) 17.728 ms * 30.013 ms
• 8 * * *
• 9 151.101.194.219 (151.101.194.219) 18.598 ms 17.092 ms 17.261 ms
• Standard output only
• Finished

Zyxel_Bella

Hi @Bigtroll001

 

In the first post you mentioned the DNS on both mobile router and phone, but the nslookup and trace route looks like not.

Could you firstly point to DNS to 8.8.8.8 and test again?

Thank you

 

Regards,

Bella