Cannot connect to only certain nodes but the allstar boxes can see each other

Got a head scratcher. I had a cable cut and lost internet for a day, when reconnected I got a new IP address, though I think none of that is part of the problem but one never knows.
I normally run 28599 to 42610, the K5TRA 900 network. And my 440 node, 2360, normally to W8VT’s hub node in NJ 43015.

After I was bac up I rebooted the node PC’s. I usually wait about 20 minutes to connect, and I was able to connect 28599 to 42610. I tried 2360 to 43015. No go, connection failed on console an immediate hangup. Tried 8VT’s other node 27849. Same result. Tried W8JTW on node 42370. Works fine. N5JGX 41055, works fine. Tried 42610, works fine. Just can’t connect to W8VT nodes. I looked in rpt_extnodes, those nodes are there, correct IP address and port numbers.

I used the 2360 node PC to do an NMAP scan of W8VT’s hub looking for port 4569 there and it sees it. I tried putting the W8VT hub node info in rpt.conf to bypass a lookup. No dice, same result.

iax2 show registry:

Connected to Asterisk GIT Version currently running on repeater (pid = 12955)
repeater*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
216.244.83.154:4569 Y 2360 60 Auth. Sent

Anybody have any idea what else I can look for to figure this out?

Thanks
GeorgeC W2DB
Crowley, TX
2360|28599

Does /var/log/asterisk/messages tell you anything? Most likely, the errors will be at the bottom of the file.
So far, from what you posted, it looks like your node isn’t registering with the registration server.

successful registration example

Host dnsmgr Username Perceived Refresh State
216.244.83.154:4569 Y 29997 216.98.194.41:4569 60 Registered

It looks like (From looking at my own node) that the registration server is occasionally unreachable.

Jeremy [W0JRL]

Except…I can connect to anything else I try, just not his nodes.

messages has nothing significant (and none of these are at the time of a connect attempt):

[Oct 6 01:01:23] NOTICE[12967] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.72.21.13 to 44.135.121.22
[Oct 6 01:02:14] NOTICE[12964] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 178.32.160.85
[Oct 6 01:02:17] NOTICE[12957] dnsmgr.c: host ‘register.allstarlink.org’ changed from 178.32.160.85 to 44.135.121.22
[Oct 6 01:02:42] WARNING[12971] chan_iax2.c: Received unsolicited registry authenticate request from ‘178.32.160.85’
[Oct 6 01:04:44] NOTICE[12969] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 44.72.21.13
[Oct 6 01:05:00] WARNING[12977] app_rpt.c: Scheduler could not find macro 9
[Oct 6 01:07:17] NOTICE[12957] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.72.21.13 to 44.135.121.22
[Oct 6 01:08:51] NOTICE[12965] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 44.72.21.13
[Oct 6 01:09:41] NOTICE[12971] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.72.21.13 to 44.135.121.22
[Oct 6 01:11:21] NOTICE[12965] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 216.244.83.154
[Oct 6 01:12:11] NOTICE[12972] dnsmgr.c: host ‘register.allstarlink.org’ changed from 216.244.83.154 to 44.72.21.13
[Oct 6 01:12:17] NOTICE[12957] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.72.21.13 to 216.244.83.154
[Oct 6 01:12:26] WARNING[12968] chan_iax2.c: Received unsolicited registry authenticate request from ‘44.72.21.13’
[Oct 6 01:17:17] NOTICE[12957] dnsmgr.c: host ‘register.allstarlink.org’ changed from 216.244.83.154 to 44.135.121.22
[Oct 6 01:19:27] NOTICE[12966] dnsmgr.c: host ‘register.allstarlink.org’ changed from 44.135.121.22 to 216.244.83.154

GeorgeC

One other point, if I wasn’t able to register I wouldn’t be in the rpt_extnodes file, but I am, so is W8VT
GeorgeC

Maybe the far end hasn’t updated with your new IP address. Don’t forget that the station you are connecting to has to have your node with the correct IP and port in their rpt_extnodes list.

If you have access to both nodes tail /var/lib/asterisk/rpt_extnodes and check for the current timestamp in UTC. Also grep node number /var/lib/asterisk/rpt_extnodes and check for the correct IP address and port.

1 Like

OK. We got it working but it pointed at another issue related. My 28599 is running ACID and has /etc/rc.d/rc.updatenodelist running and uppdating every 10 or 20 minutes or whatever it is, and I assumed that was still happening. But its not. The newer installations like mu 2360 and Ed’s 43015 and 27849 are running the newer distros. They all pull a rpt_extnodes when they reboot. Period, no updating. So that’s why his nodes were not connecting, one was as recent as Saturday but before I got a new IP address, his hub node 43015 had a file dated last July. These are not updating. What initiates the update???

GeorgeC W2DB 2360, 28599

More on this. Perhaps someone caan explain how asterisk starts. I’ve looked thru init, init.d, etc, all rc files and cannot see what makes asterisk run, and of course also cannot see what makes rc.updatenodelist run. The wiki is pretty useless for anything other than extremely basic stuff.

GeorgeC W2DB

George,

It runs as a systemd service (daemon). Look in /usr/lib/systemd/system/asterisk.service to see how it is defined.

Tom

···

From: George Csahanin via AllStarLink Discussion Groups noreply@community.allstarlink.org
Sent: Tuesday, October 6, 2020 7:17 PM
To: tom@k5tra.net
Subject: [AllStarLink Discussion Groups] [App_rpt-users] Cannot connect to only certain nodes but the allstar boxes can see each other







George_Csahanin
October 7

More on this. Perhaps someone caan explain how asterisk starts. I’ve looked thru init, init.d, etc, all rc files and cannot see what makes asterisk run, and of course also cannot see what makes rc.updatenodelist run. The wiki is pretty useless for anything other than extremely basic stuff.

GeorgeC W2DB


Visit Topic or reply to this email to respond.


In Reply To







George_Csahanin
October 6

OK. We got it working but it pointed at another issue related. My 28599 is running ACID and has /etc/rc.d/rc.updatenodelist running and uppdating every 10 or 20 minutes or whatever it is, and I assumed that was still happening. But its not. The newer installations like mu 2360 and Ed’s 43015 and 278…


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

Problem…here’s the /usr/lib/systemd directory:

root@repeater:/usr/lib/systemd# ll
total 28
drwxr-xr-x 7 root 4096 Feb 26 2020 .
drwxr-xr-x 70 root 4096 May 17 18:28 …
drwxr-xr-x 3 root 4096 Feb 26 2020 boot
drwxr-xr-x 2 root 4096 Feb 26 2020 catalog
drwxr-xr-x 2 root 4096 Jul 5 2017 network
drwxr-xr-x 4 root 4096 Mar 2 2020 user
drwxr-xr-x 2 root 4096 Jul 5 2017 user-generators
root@repeater:/usr/lib/systemd#

Just found it in /lib/systemd/system. Here’s what’s inside:

root@repeater:/lib/systemd/system# more asterisk.service
#/usr/lib/systemd/system/asterisk.service
[Unit]
Description=Asterisk PBX and telephony daemon
Documentation=man:asterisk(8)
Wants=network.target
After=network-online.target
BindsTo=dev-dahdi-pseudo.device

Below requires a addition to udev rules

See /etc/udev/rules.d/dahdi.rules

After=dev-dahdi-pseudo.device

[Service]
Type=simple
StandardOutput=null
ExecStart=/usr/sbin/asterisk -g -f -C /etc/asterisk/asterisk.conf
ExecStop=/usr/sbin/asterisk -rx ‘stop now’
ExecReload=/usr/sbin/asterisk -rx ‘module reload’

safe_asterisk emulation

Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

root@repeater:/lib/systemd/system#


GeorgeC

I think I just found the problem. in /lib/systemd/system there is a file “updatenodelist.service”
Contents:

root@repeater:/lib/systemd/system# more updatenodelist.service
#/usr/lib/systemd/system/updatenodelist.service
[Unit]
Description=AllStar NodeList updater
Wants=network.target
After=network-online.target
BindsTo=asterisk.service

[Service]
Type=simple
StandardOutput=null
ExecStart=/usr/local/bin/rc.updatenodelist &
ExecStop=/usr/bin/killall -9 rc.updatenodelist

safe_emulation

Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

root@repeater:/lib/systemd/system#


So not sure why it wasn’t starting unless network.target is an issue somehow

I have a hard time wrapping my head around systemd. Used only Slackware Linux since pre-version 1 back to 1994. Much easier to understand.

GeorgeC W2DB

I’ve run into this also, and I find the updatenodelist dies at times, but I thought I was the only one :slight_smile:

Do systemctl enable updatenodelist to enable it on server boot.

Here are other useful systemd commands:
systemctl start updatenodelist
systemctl restart updatenodelist
systemctl status updatenodelist
systemctl stop updatenodelist
systemctl is-active --quite updatenodelist

That last command is useful in a script. For example I rewrote astup.sh, astdn.sh and asters.sh to use it.

#!/bin/bash

# N4IRS 07/26/2017
# WD6AWP 09/09/2020

systemctl is-active --quiet asterisk.service
err=$?
if [ $err -eq 0 ]; then
   echo "Asterisk is currently running!"
else
   echo "Starting asterisk..."
   systemctl start asterisk.service
fi

You use that (or write a similar script) and call it with cron to start it once a day if dead.

BTW, here’s the service file if you need it. Put this in the directory with filename shown then do a systemctl daemond-reload.

#/lib/systemd/system/updatenodelist.service
[Unit]
Description=AllStar NodeList updater
Wants=network.target
After=network-online.target
BindsTo=asterisk.service
[Service]
Type=simple
StandardOutput=null
ExecStart=/usr/bin/rc.updatenodelist &
ExecStop=/usr/bin/killall -9 rc.updatenodelist
# safe_emulation
Restart=always
RestartSec=10
[Install]
WantedBy=multi-user.target

Hi There,
Probably easy answer. You can’t get into W8VT’s hub node in NJ 43015.
That is because he probably is using a firewall to screen unknown IP’s.
So ring him up or email him and tell him you got a new IP address.
Because DNCP on your ISP gave you a new one.
Problem solved.

See my last post. We figured it out. His rc.updatenodelist wasn’t running so he didn;t get my new (as of Sunday) IP address. My Inet connection was down a day due to a cable cut and when re-established I got a new IP address

GeorgeC

George,

Great work on finding the issue!

So, the most important question to answer is, Why was his rc.updatenodelist not running / working?

What was/is the cause?

Any ideas so that we can learn from this issue.

73

Marshall - ke6pcv

···

From: George Csahanin via AllStarLink Discussion Groups [mailto:noreply@community.allstarlink.org]
Sent: Friday, October 09, 2020 10:35 AM
To: ke6pcv@cal-net.org
Subject: [AllStarLink Discussion Groups] [App_rpt-users] Cannot connect to only certain nodes but the allstar boxes can see each other







George_Csahanin
October 9

See my last post. We figured it out. His rc.updatenodelist wasn’t running so he didn;t get my new (as of Sunday) IP address. My Inet connection was down a day due to a cable cut and when re-established I got a new IP address

GeorgeC


Visit Topic or reply to this email to respond.


In Reply To







jfall
October 9

Hi There, Probably easy answer. You can’t get into W8VT’s hub node in NJ 43015. That is because he probably is using a firewall to screen unknown IP’s. So ring him up or email him and tell him you got a new IP address. Because DNCP on your ISP gave you a new one. Problem solved.

Previous Replies







jfall
October 9

Hi There,
Probably easy answer. You can’t get into W8VT’s hub node in NJ 43015.
That is because he probably is using a firewall to screen unknown IP’s.
So ring him up or email him and tell him you got a new IP address.
Because DNCP on your ISP gave you a new one.
Problem solved.







wd6awp ASL Admin
October 7

I’ve run into this also, and I find the updatenodelist dies at times, but I thought I was the only one :slight_smile:

Do systemctl enable updatenodelist to enable it on server boot.

Here are other useful systemd commands:
systemctl start updatenodelist
systemctl restart updatenodelist
systemctl status updatenodelist
systemctl stop updatenodelist
systemctl is-active --quite updatenodelist

That last command is useful in a script. For example I rewrote astup.sh, astdn.sh and asters.sh to use it.

#!/bin/bash



# N4IRS 07/26/2017

# WD6AWP 09/09/2020



systemctl is-active --quiet asterisk.service

err=$?

if [ $err -eq 0 ]; then

   echo "Asterisk is currently running!"

else

   echo "Starting asterisk..."

   systemctl start asterisk.service

fi

You use that (or write a similar script) and call it with cron to start it once a day if dead.

BTW, here’s the service file if you need it. Put this in the directory with filename shown then do a systemctl daemond-reload.

#/lib/systemd/system/updatenodelist.service

[Unit]

Description=AllStar NodeList updater

Wants=network.target

After=network-online.target

BindsTo=asterisk.service

[Service]

Type=simple

StandardOutput=null

ExecStart=/usr/bin/rc.updatenodelist &

ExecStop=/usr/bin/killall -9 rc.updatenodelist

# safe_emulation

Restart=always

RestartSec=10

[Install]

WantedBy=multi-user.target







George_Csahanin
October 7

I think I just found the problem. in /lib/systemd/system there is a file “updatenodelist.service”
Contents:

root@repeater:/lib/systemd/system# more updatenodelist.service
#/usr/lib/systemd/system/updatenodelist.service
[Unit]
Description=AllStar NodeList updater
Wants=network.target
After=network-online.target
BindsTo=asterisk.service

[Service]
Type=simple
StandardOutput=null
ExecStart=/usr/local/bin/rc.updatenodelist &
ExecStop=/usr/bin/killall -9 rc.updatenodelist

safe_emulation

Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

root@repeater:/lib/systemd/system#


So not sure why it wasn’t starting unless network.target is an issue somehow

I have a hard time wrapping my head around systemd. Used only Slackware Linux since pre-version 1 back to 1994. Much easier to understand.

GeorgeC W2DB







George_Csahanin
October 7

Problem…here’s the /usr/lib/systemd directory:

root@repeater:/usr/lib/systemd# ll

total 28
drwxr-xr-x 7 root 4096 Feb 26 2020 .
drwxr-xr-x 70 root 4096 May 17 18:28 …
drwxr-xr-x 3 root 4096 Feb 26 2020 boot
drwxr-xr-x 2 root 4096 Feb 26 2020 catalog
drwxr-xr-x 2 root 4096 Jul 5 2017 network
drwxr-xr-x 4 root 4096 Mar 2 2020 user
drwxr-xr-x 2 root 4096 Jul 5 2017 user-generators
root@repeater:/usr/lib/systemd#

Just found it in /lib/systemd/system. Here’s what’s inside:

root@repeater:/lib/systemd/system# more asterisk.service
#/usr/lib/systemd/system/asterisk.service
[Unit]
Description=Asterisk PBX and telephony daemon
Documentation=man:asterisk(8)
Wants=network.target
After=network-online.target
BindsTo=dev-dahdi-pseudo.device

Below requires a addition to udev rules# See /etc/udev/rules.d/dahdi.rules

After=dev-dahdi-pseudo.device

[Service]
Type=simple
StandardOutput=null
ExecStart=/usr/sbin/asterisk -g -f -C /etc/asterisk/asterisk.conf
ExecStop=/usr/sbin/asterisk -rx ‘stop now’
ExecReload=/usr/sbin/asterisk -rx ‘module reload’

safe_asterisk emulation

Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

root@repeater:/lib/systemd/system#


GeorgeC







Tom
October 7

George,

It runs as a systemd service (daemon). Look in /usr/lib/systemd/system/asterisk.service to see how it is defined.

Tom

··· (click for more details)


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.