WB4IZC
January 12, 2025, 3:32pm
1
I have built a new ASL3 image and all is working fine. Now to add additional features but, I am unable to download files from Github like this one “sudo wget https://raw.githubusercontent.com/KD5FMU/Time-Weather-Announce/refs/heads/main/time_weather.sh ” Upon running this line, I receive the following error message:
I am able to download this same file from both of my HamVoip nodes.
I was also unable to install “sudo apt install bc” again I receive an error message
I would appreciate receiving any suggestions to how I might be able to fix this issue. 73, Steve WB4IZC
Mike
January 12, 2025, 3:46pm
2
It would be a guess but I think it a dns issue at your location.
Try restarting you modem then router.
WB4IZC
January 12, 2025, 4:20pm
3
I have done that with the same results. I don’t understand why I can download Github files from the same IP address when I switch over to a Hamvoip image.
N2DYI
January 12, 2025, 5:35pm
4
It’s worth noting that HamVoIP is set up to use a local resolver (127.0.0.1) and that local resolver is homing on 8.8.8.8 and 8.8.4.4, not whatever your network is telling clients to use. That could make a difference.
WB4IZC
January 12, 2025, 6:14pm
5
I attempted to update my asl3 image from cockpit and obtained the following error message:
Loading available updates failed
E: Index of /debian bookworm InRelease is not (yet) available (Temporary failure resolving ‘deb.debian.org ’) E: Index of /debian bookworm InRelease is not (yet) available (Temporary failure resolving ‘archive.raspberrypi.com ’) E: Index of /public/ bookworm InRelease is not (yet) available (Temporary failure resolving ‘repo.allstarlink.org ’) E: Index of /debian-security bookworm-security InRelease is not (yet) available (Temporary failure resolving ‘deb.debian.org ’) E: Index of /debian bookworm-updates InRelease is not (yet) available (Temporary failure resolving ‘deb.debian.org ’)
WB4IZC
January 12, 2025, 6:42pm
6
I have also learned that asl3 is not updating node lists:
12:37 PM
Failed to start asl3-update-nodelist.service - Update ASL3 on-disk nodelist db.
systemd
12:37 PM
asl3-update-nodelist.service: Failed with result ‘exit-code’.
systemd
12:37 PM
asl3-update-nodelist.service: Main process exited, code=exited, status=1/FAILURE
systemd
12:37 PM
failed to download from http://snodes.allstarlink.org/diffnodes.php
asl3-update-nodelist
12:37 PM
Starting asl3-update-nodelist.service - Update ASL3 on-disk nodelist db…
N2DYI
January 12, 2025, 7:22pm
7
Yep, definitely a DNS problem.
What happens if you type
dig allstarlink.org
from bash?
WB4IZC
January 12, 2025, 8:09pm
8
Not good news
asl3@Node552252:~ $ dig allstarlink.org
;; communications error to ::1#53: connection refused
;; communications error to ::1#53: connection refused
;; communications error to ::1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
; <<>> DiG 9.18.28-1~deb12u2-Debian <<>> allstarlink.org
;; global options: +cmd
;; no servers could be reached
N8EI
January 13, 2025, 1:35pm
9
This is most definitely a local DNS problem. Is this an ASL3 Appliance or are you installing ASL3 on a standard Debian host.
The ASL3 Appliance uses the DNS handed out by your DHCP Server - you can see this in the contents of the file /etc/resolv.conf
.
In any case, your system it trying to look at itself for DNS which isn’t likely to work unless you’ve made other configurations.
WB4IZC
January 13, 2025, 2:29pm
10
This is an ASL3 pi build. I will take a look at that file when I get back home tonight. Thanks for the info. Steve