Dropping of all outbound connections

A few times in the last few weeks I have seen one of my hub nodes drop all outbound initiated connections. It happened today at 1513 hours and here’s the ast log. Any thoughts as to what is going on?

[Aug 25 15:10:34] WARNING[647] chan_iax2.c: Received unsolicited registry authenticate request from ‘44.135.121.22’
[Aug 25 15:13:03] WARNING[646] chan_iax2.c: Max retries exceeded to host 70.31.40.142 on IAX2/70.31.40.142:4569-13490 (type = 6, subclass = 11, ts=4859868, seqno=157)
[Aug 25 15:13:03] WARNING[645] chan_iax2.c: Max retries exceeded to host 70.65.75.86 on IAX2/70.65.75.86:4569-7525 (type = 7, subclass = 0, ts=192515933, seqno=73)
[Aug 25 15:13:03] WARNING[648] chan_iax2.c: Max retries exceeded to host 44.135.121.14 on IAX2/44.135.121.14:4569-1702 (type = 7, subclass = 0, ts=177024159, seqno=62)
[Aug 25 15:13:03] WARNING[650] chan_iax2.c: Max retries exceeded to host 50.98.124.121 on IAX2/50.98.124.121:4569-10984 (type = 7, subclass = 0, ts=192595379, seqno=117)
[Aug 25 15:13:03] WARNING[653] chan_iax2.c: Max retries exceeded to host 104.168.211.40 on IAX2/104.168.211.40:4569-13631 (type = 7, subclass = 0, ts=801636321, seqno=228)
[Aug 25 15:13:03] WARNING[649] chan_iax2.c: Max retries exceeded to host 206.212.236.193 on IAX2/206.212.236.193:4569-8323 (type = 7, subclass = 0, ts=876001353, seqno=85)
[Aug 25 15:13:03] WARNING[646] chan_iax2.c: Max retries exceeded to host 70.66.88.111 on IAX2/70.66.88.111:4569-14204 (type = 7, subclass = 0, ts=962733696, seqno=97)
[Aug 25 15:13:03] WARNING[650] chan_iax2.c: Max retries exceeded to host 173.182.77.182 on IAX2/173.182.77.182:4569-11085 (type = 7, subclass = 0, ts=801646013, seqno=236)
[Aug 25 15:13:03] WARNING[649] chan_iax2.c: Max retries exceeded to host 204.83.243.250 on IAX2/204.83.243.250:4569-10207 (type = 7, subclass = 0, ts=450784179, seqno=164)
[Aug 25 15:13:03] WARNING[651] chan_iax2.c: Max retries exceeded to host 155.138.201.254 on IAX2/155.138.201.254:4569-6950 (type = 7, subclass = 0, ts=486388310, seqno=242)
[Aug 25 15:13:03] WARNING[649] chan_iax2.c: Max retries exceeded to host 70.50.41.195 on IAX2/70.50.41.195:4569-9380 (type = 7, subclass = 0, ts=64141852, seqno=249)
[Aug 25 15:13:03] WARNING[645] chan_iax2.c: Max retries exceeded to host 24.150.16.176 on IAX2/24.150.16.176:4569-3101 (type = 7, subclass = 0, ts=192943272, seqno=22)
[Aug 25 15:13:04] WARNING[654] chan_iax2.c: Max retries exceeded to host 99.249.237.183 on IAX2/99.249.237.183:4567-11009 (type = 7, subclass = 0, ts=188435638, seqno=216)
[Aug 25 15:13:04] WARNING[651] chan_iax2.c: Max retries exceeded to host 99.225.50.119 on IAX2/99.225.50.119:4569-10992 (type = 7, subclass = 0, ts=10246497, seqno=79)
[Aug 25 15:13:04] WARNING[650] chan_iax2.c: Max retries exceeded to host 73.178.228.52 on IAX2/73.178.228.52:4565-13150 (type = 7, subclass = 0, ts=375569068, seqno=252)
[Aug 25 15:13:04] WARNING[646] chan_iax2.c: Max retries exceeded to host 174.118.182.224 on IAX2/174.118.182.224:4569-1349 (type = 7, subclass = 0, ts=625628008, seqno=169)
[Aug 25 15:13:16] ERROR[677] app_rpt.c: No link messages from [27884] in 46 seconds – One way audio??? Forcing reconnect.
[Aug 25 15:13:18] ERROR[677] app_rpt.c: No link messages from [43694] in 46 seconds – One way audio??? Forcing reconnect.
[Aug 25 15:13:22] ERROR[677] app_rpt.c: No link messages from [47817] in 46 seconds – One way audio??? Forcing reconnect.
[Aug 25 15:13:22] ERROR[677] app_rpt.c: No link messages from [50772] in 46 seconds – One way audio??? Forcing reconnect.
[Aug 25 15:14:56] NOTICE[646] chan_iax2.c: Registered IAX2 to ‘178.32.160.82’, who sees us as 173.180.71.184:4573 with no messages waiting

[Aug 25 15:14:56] WARNING[20110] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:14:58] WARNING[20160] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:02] WARNING[20162] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:07] WARNING[20171] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:13] WARNING[20192] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:18] WARNING[20242] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:23] WARNING[20286] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:29] WARNING[20341] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:34] WARNING[20388] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:40] WARNING[20439] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:45] WARNING[20489] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:51] WARNING[20539] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:15:56] WARNING[20583] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:02] WARNING[20640] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:07] WARNING[20692] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:13] WARNING[20742] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:18] WARNING[20786] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:23] WARNING[20833] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:29] WARNING[20890] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:34] WARNING[20938] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:40] WARNING[20991] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:45] WARNING[21041] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:51] WARNING[21091] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:16:56] WARNING[21135] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:02] WARNING[21193] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:07] WARNING[21248] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:13] WARNING[21294] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:18] WARNING[21341] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:24] WARNING[21388] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:29] WARNING[21443] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:34] WARNING[21496] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:40] WARNING[21547] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:45] WARNING[21597] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!
[Aug 25 15:17:51] WARNING[21644] app_rpt.c: Node 47817 IP 68.0.252.207 does not match link IP 155.138.201.254!!

Adrian - This appears to be a case where the nodes ip address / port info is not in tight sync time wise with the dhcp assignment from your ISP to the node in question. If you have a provider that changes your IP address on a more frequent basis, then there will be periods where this sync will be broken for up to 15 minutes while the allstar mothership awaits / gets a new update from your node.

For those times that your outbound connection loses sync, check on your router to see if it has received a new IP address.

Fixing this - there are a few options available. Call me and we can discuss.

Keith / VA3YC

Hi Keith, thanks for your help as always. However, the WAN IP address, while dynamic, has not changed and has only changed once in the last couple of years. Looking at the logs it seems like the nodes I am connected to are changing their IP and are therefore out of sync, but it doesn’t make sense that this would happen to multiple (in fact “all”) nodes at the same time that are in different parts of the world. I’ll grab my radio and give you a shout after breakfast. Thx. Adrian

After further investigation it may be related to my HF station getting RF into the network causing a brief internet outage. Outbound calls drop and don’t recover, inbound ones seem to, perhaps because they are permanent links (not 100% sure). Back to ferrite chokes and spray on shielding!