Jim, Are you still having problems? Marshall From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Jim Korenz Sent: Wednesday, August 14, 2019 7:33 AM To: app_rpt-users@lists.allstarlink.org Subject: [App_rpt-users] Setup Problems OK, I've been having problems with setting AllStar. I had a working link till it died about a month ago. I replaced the PI and SD card and started a new install. I've run into multiple problems on the way. In the setup script, I didn't notice that the demo node no. 19999 didn't erase as I typed my node no. 28674. After setup,it wouldn't login to the Allstar server. I checked the config files and found the node no was 1999928674. OK, now rerun the setup script. Still no luck. On further examination, the node no was now 28767428674. OK, reburn the SD card and start over. Now we get to the setup screen for the network. I select static IP. I enter my IP 192.168.0.100. Now the netmask, 255.255.255.000. ERROR, bad entry. Now instead of looping back and asking again, the setup exits the network setup screen. Worse yet, reruning the asl-menu doesn't enter the network setup screen. Reburn the SD card and try again. Next time try netmask of 255.255.255.128, no go. Reburn SD try again. This time try 255.255.255.192 , yea, this works, but afterwards Allstar doesn't because 192.168.0.100 can't be reached with this mask. OK, I finally manually edit the dhcpcd.conf file and get the internet access working and am logged into the Allstar server. I've setup the EchoLink also. The last problem is no one can connect to the EchoLink node. I would like someone to test the Allstar link and the Echolink node, 745361. Also, I had to use the alternate AllStar port of 4566 since I have AT&T and they blocked 4569. Any help would be appreciated. JimK N8PXW