Test worked great now that I know what to look for, 100% fixed. Sorry I made it hard on you, but I learned a lot and thanks for that. I never have programed in C, C+, or linux. I was an old FORTRAN

On Fri, Apr 5, 2019 at 12:09 PM, Basil Gunn wrote: Thanks for the answers and Basil for the scrips. I tried the beacmin.sh script and it does beacon but I am not getting a location on my TH-D74 or

It only saves the values, not the selected radio. E.g. if you select ft-817 AF, note the values. Then save. When you restart the selected values should be what you saved, but the radio pre-select

I may have found my problem. I am running a device that protects my server it is call RECON SENTENEL so I checked it and found that it had blocked the raspberry pi. I unblocked it and did an update.

I have a UDRC-II running with Beta-11 and it works well. I have one VHF/UHF radio connected to the 6 pin din connector, nothing connected to the 15 pin. But today when I did a "listen -cart" I

Set nameservers to 1.1.1.1 and 8.8.8.8 and verified they took, but ping gitHub.com came back with a name recognition problem. ping google.com worked fine. I better have my son on site get the fix.

See notes below What I would try is editing /etc/resolv.conf cd /etc cp resolv.conf resolv.conf.backup sudo nano resolv.conf In the editor delete or comment out (comments are lines starting with a #

domain Home nameserver 192.168.0.1 nameserver 295.1/1.2.25

Sorry if this email is a little elementary from some readers. It seems like we have a few folks out there not yet familiar with networking. Hope this helps. If everything is setup the

John, I am taking up too much of your time. My son is a professional programmer I will have him look into it when he next visits. Tried the N7nix command git pull, comes back with unable to access

You escape ping with a control-c Send me the results of cat /etc/resolv.conf on the Raspberry Pi -- John D. Hays Edmonds, WA K7VE

Tnx Basil will use your commands.

You need to figure out why you are not resolving the address. This is a local network administration issue, not a draws-manager specific issue. Try the ping tests I listed earlier. You can also try,

Yes, that command brings up the DRAWS MANAGER on the pi Webb browser.

ping google.com came back with info but did not go back to the command prompt. ping GitHub.com came back with "Temporary failure of name recognition. The IP address of the DRAWS here is

I used https://draws.local:8080 and received the same error message several second after commanding Update DRAWS Manager

John D. Hays Edmonds, WA K7VE

Your DNS resolution isn't working, you will need to sort that out in the OS, if you are using DHCP to get an IP address it should be setting your DNS resolver. Open a terminal a try pinging some

On the pi, in a browser it's http://localhost:8080 On another computer on the LAN, use the LAN IP (ifconfig to find it on the pi) of the pi, e.g. ip address 192.168.0.40 would be

Is your RPi connected to the Internet? You can upgrade all your files including draws-manager by: cd cd n7nix git pull cd bin ./prog_refresh.sh /Basil n7nix Fred Hirsch via Groups.Io