On 22/03/2019 13:38, Roby wrote:
> On 22/03/2019 The Natural Philosopher wrote:
>> On 22/03/2019 11:15, Roby wrote:
>>> Roby wrote, on 22/03/2019:
>>>> Roby wrote, on 22/03/2019:
>>>> ---- cut
>>>>> This is my /etc/apt/sources.list:
>>>>> -----
>>>>> deb http://mirrordirector.raspbian.org/raspbian/ jessie main
>>>>> contrib non-free rpi
>>>>> # Uncomment line below then 'apt-get update' to enable 'apt-get
>>>>> source'
>>>>> #deb-src http://archive.raspbian.org/raspbian/ jessie main contrib
>>>>> non-free rpi
>>>>> --------
>>>> ---- 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!
>>>> :-?
>>>
>>> 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..........
>>>
>>
>> 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.
>
> 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 ?

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 http://raspbian.raspberrypi.org/raspbian/ 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


>
> Thank you
>


--
There’s a mighty big difference between good, sound reasons and reasons
that sound good.

Burton Hillis (William Vaughn, American columnist)

--- SoupGate-Win32 v1.05