RPI3 speedtest-cli and 'sudo apt-get update' problems

Using RASPBERRI PI3 with RASPBIAN Jessie WITH PIXEL
KERNELL: 4.4.26-v7+ #915 SMP Thu Oct 20 17:08:44 BST 2016 armv7l
GNU/Linux
I use a 4G mobile connection but it is a fixed location as I use an AVM
3390 router with a Huawei E392 USB
The internet connection works perfectly, thanks also to the two
external antennas connected to Huawei E392.
I have problems with speedtest-cli
This is the result of the tests, whatever the selected server:
----------------
sudo speedtest-cli --secure
Retrieving speedtest.net configuration...
Testing from XXXX Mobile (xxx.yyy.zzz.www)...
Retrieving speedtest.net server list...
Selecting best server based on ping...
Hosted by xxxxxxxxxx [37.71 km]: 1800000.0 ms
Testing download
speed................................................................................
Download: 0.00 Mbit/s
Testing upload
speed................................................................................................
Upload: 5.41 Mbit/s
------------------
Can any expert help me to solve the problem?
Unfortunately I can't update the RPI3 with sudo apt-get update
because I have many mistakes like this:
Failed to fetch
formatting link

404 Not Found [IP: 93.93.128.211 80]
?
W: Failed to fetch
formatting link

404 Not Found [IP: 93.93.128.211 80]
Some ideas to solve the problems highlighted above
Many thanks
Bob
--
Roby
Reply to
Roby
Loading thread data ...
Roby ha spiegato il 18/03/2019 :
For the same problems highlighted with 'sudo apt-get update' (...error 404....) I can't even install iperf3 (sudo apt-get install iperf3) :'(
--
Roby
Reply to
Roby
Roby 18/03/2019:
----cut
Could it be a flow control problem on the USB port ??? The Huawei E392 USB is connected to AVM 3390 USB port via D-Link DUB-H4 Hub...... Does the D-Link DUB-H4 Hub manage the flow control ??? Can it be configured ???
--
Roby
Reply to
Roby
Roby wrote, on 18-03-2019 11:37:
Not an explanation for the 404 errors, probably; but there aren't many updates for Jessie anymore. Move up to Stretch. Well, if you promise not to kill anyone or yourself over systemd.
Reply to
A. Dumas
Switching to Stretch is not easy .... this RPI3 is not at home but at a distance of 500 km :'(
--
Roby
Reply to
Roby
That site is working fine for me via several different routes. Something up with your internet connection?
Reply to
mm0fmf
Updating in place went fine for me on half a dozen headless Pi's.
---druck
Reply to
druck
I use a 4G mobile connection but it is a fixed location as I use an AVM 3390 router with a Huawei E392 USB The internet connection seems to work well. I have two external antennas connected to Huawei E392......and video surveillance also works. But even in this case the upload is used more than the download ....
Only when I go to this remote location (500 km from where I usually am) will I be able to verify ... but having problems only with the download is strange. Maybe it's just speedtest-cli that has problems ? ;-) And are the 404 errors (sudo apt-get update) only due to download problems ? I don't think, because doing PING to these servers don't respond....
--
Roby
Reply to
Roby
Two important functions for me in the RPI3 are the management of the APC UPS (with APCUPSD) and the authentication of the RPI3 through RSA public KEY. Do you also use these two things ? I would be interested to know if with Stretch the APCUPSD and RSA KEY authentication continue to work without problems..... and if after the update some changes need to be made.... Thank you
--
Roby
Reply to
Roby
Roby wrote, on 21/03/2019: --- cut
No, I wrote something untrue ... At PING the server 93.93.128.211 responds correctly So I guess the folder paths have changed ... :/
--
Roby
Reply to
Roby
I used the link you posted.
Reply to
mm0fmf
Then I just don't understand what's going on....
I do a little analysis... This is my /etc/apt/sources.list: ----- deb
formatting link
jessie main contrib non-free rpi # Uncomment line below then 'apt-get update' to enable 'apt-get source' #deb-src
formatting link
jessie main contrib non-free rpi -------- If I go here with the browser:
formatting link
I see that the folders do not match because there is no jessie folder but only Parent Directory, dists, poll, non-free, rpi To find the Jessie folder (and than also main, contrib...) I must first enter to dists !!!! Could this be the problem ? Can you please post your /etc/apt/sources.list
Maybe I need to edit my /etc/apt/sources.list or some other list ?? Thank you
--
Roby
Reply to
Roby
Roby wrote, on 22/03/2019: ---- cut
---- cut
What does not work is the RPI3 that I have in the remote location 500 km away from here (internet with router and 4G USB key) The second RPI3 that I have here at home with ADSL/FTTH has the exact same /etc/apt/sources.list as the remote one and IT WORKS! :-?
--
Roby
Reply to
Roby
Then probably something is messing with your internet connection, perhaps a "transparent" http proxy.
Reply to
Roger Bell_West
Roby wrote, on 22/03/2019:
Not being able to install new functions to manage eth0, such as iperf3 (...as already written also in this case I have error 404...), I checked how it works eth0 with sudo mii-tool This is the result: eth0: negotiated 1000baseT-HD flow-control, link ok So it seems that the problem is not caused by eth0..... ;-) I do not know what to do..........
--
Roby
Reply to
Roby
Ergo for whatever reason the "router and 4G USB key" is not giving you the same access as you have 'here at home'.
Might be a DNS issue, or a firewall issue..
--
You can get much farther with a kind word and a gun than you can with a  
kind word alone. 
 Click to see the full signature
Reply to
The Natural Philosopher
start by doing a DNS looukpo ON the REMOTE machine - I assume you have at least ssh access - to see if it can understnd what IP address the repository is on.
If that fails, fix DNS.
If it works try maybe pinging the repository address - Failure is not necessarily an issue but success shows its visible over the internet.
--
Gun Control: The law that ensures that only criminals have guns.
Reply to
The Natural Philosopher
Good idea ! The remote router used the provider's DNS. Now I have entered google DNS (8.8.8.8) but nothing in the RPI3 has changed. The default gateway in the RPI3 is correct (ip route | grep default | cut -d' ' -f3) and corresponds to the router address. But I can't verify which DNS uses the RPI3 because I don't have the nslookup command available and cause error 404 the 'sudo apt-get install dnsutils' does not work Do you have suggestions to check which DNS uses rpi3 ?
Thank you
--
Roby
Reply to
Roby
Roby wrote, on 22/03/2019: ---cut
----cut
PING is OK: sudo ping archive.raspberrypi.org PING lb.raspberrypi.org (46.235.227.11) sudo ping mirrordirector.raspbian.org PING mirrordirector.raspbian.org (93.93.128.193) ----- These are the 404 errors with 'sudo apt-get update': Ign
formatting link
jessie InRelease Ign
formatting link
jessie InRelease Ign
formatting link
jessie Release.gpg Ign
formatting link
jessie Release.gpg Ign
formatting link
jessie Release Ign
formatting link
jessie Release Err
formatting link
jessie/main armhf Packages 404 Not Found [IP: 46.235.227.11 80] Err
formatting link
jessie/ui armhf Packages 404 Not Found [IP: 46.235.227.11 80] Ign
formatting link
jessie/main Translation-en Ign
formatting link
jessie/ui Translation-en Err
formatting link
jessie/main armhf Packages 404 Not Found [IP: 93.93.128.193 80] Err
formatting link
jessie/contrib armhf Packages 404 Not Found [IP: 93.93.128.193 80] Err
formatting link
jessie/non-free armhf Packages 404 Not Found [IP: 93.93.128.193 80] Err
formatting link
jessie/rpi armhf Packages 404 Not Found [IP: 93.93.128.193 80] Ign
formatting link
jessie/contrib Translation-en Ign
formatting link
jessie/main Translation-en Ign
formatting link
jessie/non-free Translation-en Ign
formatting link
jessie/rpi Translation-en W: Failed to fetch
formatting link
404 Not Found [IP: 93.93.128.193 80]
W: Failed to fetch
formatting link
404 Not Found [IP: 93.93.128.193 80]
--
Roby
Reply to
Roby
Umm. yes. You have the bootstrap problem.
One way you can eliminate DNS is to actually put the repository IP in /etc/hosts
so: more /etc/apt/sources.list:
deb
formatting link
stretch main contrib non-free rpi
...shows my PI looks for "raspbian.raspberrypi.org"
and my desktop here shows:
raspbian.raspberrypi.org. 278 IN CNAME mirrordirector.raspbian.org. mirrordirector.raspbian.org. 578 IN A 93.93.128.193
So an enetry like
93.93.128.193 raspbian.raspberrypi.org
in /etc/hosts on te remote pi will sidestep any DNS issues
My Pi here shows that I can indeed ping that address
root@MiPiFi:/etc/apt# ping 93.93.128.193 PING 93.93.128.193 (93.93.128.193) 56(84) bytes of data. 64 bytes from 93.93.128.193: icmp_seq=1 ttl=55 time=14.8 ms 64 bytes from 93.93.128.193: icmp_seq=2 ttl=55 time=18.1 ms 64 bytes from 93.93.128.193: icmp_seq=3 ttl=55 time=18.0 ms 64 bytes from 93.93.128.193: icmp_seq=4 ttl=55 time=18.7 ms 64 bytes from 93.93.128.193: icmp_seq=5 ttl=55 time=17.6 ms 64 bytes from 93.93.128.193: icmp_seq=6 ttl=55 time=17.7 ms 64 bytes from 93.93.128.193: icmp_seq=7 ttl=55 time=18.0 ms 64 bytes from 93.93.128.193: icmp_seq=8 ttl=55 time=17.8 ms ^C --- 93.93.128.193 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7010ms rtt min/avg/max/mdev = 14.889/17.641/18.749/1.093 ms
So unless your ISP prohibits pinging you SHOULD be able to get a response.
The two techniques should help narrow down the problem a bit more
--
There?s a mighty big difference between good, sound reasons and reasons  
that sound good. 
 Click to see the full signature
Reply to
The Natural Philosopher

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.