Todays update seems to have issues with netmetr

Software SW bugs discussion
1 
Device	Turris Omnia
Serial number	12345678910
reForis version	1.0.8
Turris OS version	5.2.7
Turris OS branch	HBS
Kernel version	4.14.245

root@turris:~# netmetr 
Checking uuid on the control server...
Traceback (most recent call last):
  File "/usr/bin/netmetr", line 11, in <module>
    load_entry_point('netmetr==1.6.0', 'console_scripts', 'netmetr')()
  File "/usr/lib/python3.7/site-packages/netmetr/__main__.py", line 625, in main
  File "/usr/lib/python3.7/site-packages/netmetr/__main__.py", line 127, in load_uuid
  File "/usr/lib/python3.7/site-packages/netmetr/__main__.py", line 145, in download_uuid
  File "/usr/lib/python3.7/site-packages/netmetr/__main__.py", line 102, in send_request
  File "/usr/lib/python3.7/urllib/request.py", line 222, in urlopen
  File "/usr/lib/python3.7/urllib/request.py", line 531, in open
  File "/usr/lib/python3.7/urllib/request.py", line 641, in http_response
  File "/usr/lib/python3.7/urllib/request.py", line 569, in error
  File "/usr/lib/python3.7/urllib/request.py", line 503, in _call_chain
  File "/usr/lib/python3.7/urllib/request.py", line 649, in http_error_default
urllib.error.HTTPError: HTTP Error 502: Bad Gateway

In re-foris neither start test, nor Redownload data seem to work. Not a big deal, but it seems like a regression…

On the plus side, I did not need to run /etc/init.d/firewall restart after the reboot to get internet access from my LAN. Win some, loose some (and I happily trade netmetr issues for not being able to remotly reboot the router without loosing access to it :wink: )

Mmmh, it seems I have connection issues with netmetr.cz, browsing to https://websites.pages.nic.cz/netmetr.cz/en/ gives:
" For some unknown reason we failed to connect to the NetMetr measurement servers. Please check that the connection is not blocked and try it again later. In the meantime, you can use a test from colleagues at CESNET to measure speed."

2 Likes
2

Speedest by me from interface not work and the same error in terminal ---- ended HTTP Error 502: Bad Gateway

1 Like
3

Hi guys,

Thanks for reporting. I was able to reproduce it also on my end. I forwarded your findings to the NetMetr team to take a look. If there is anything new, I will let you know.

4 Likes
4

Issue has been found, it’s fixed! You can try it now, if it works on your end.

2 Likes
5

Thanks, works again:

root@turris:~# netmetr
Checking uuid on the control server...
Requesting test config from the control server...
Starting ping test...
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
ping: unknown host ipv6.speed.netmetr.cz
Starting speed test...
==== rmbt e30eb64d7 ====
connecting...
connected with 3 flow(s) for dl; 3 flow(s) for ul
pretest downlink start... (min 1s)
pretest downlink end.
rtt_tcp_payload start... (11 times)
rtt_tcp_payload end.
downlink test start... (5s)
downlink test end.
pretest uplink start... (min 1s)
pretest uplink end.
uplink test start... (5s)
uplink test end.
disconnecting.
dl_throughput_mbps = 87.203477
ul_throughput_mbps = 28.426162
Exiting.
uci: Parse error (invalid command) at line 5, byte 0
Your Sync code is: **************

That is, the old IPv4/IPv6 issue with the latency probe is still waiting for a fix…

1 Like
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.