I am at a loss on being able connect to Allstar node from a second allstar node. I have 559290 and 559292. The 559290 node was setup on an Netgear router with port forwarding on 4569 to a static IP. I replaced that with a Unifi Max router and setup the same port forwarding and it does not work. (only changed one thing by swapping routers). Using the asterisk command below it looks like the connection request is getting through, but I’m not making sense of the link IP statement.
I have tried hard coding the IP in the rpt.conf.
Any thoughts?
;559290 = radio@127.0.0.1:4569/559292,NONE ; This must be changed to your node number
559290 = radio@192.168.1.9:4569/559292,NONE ; This must be changed to your node number
Connected to Asterisk 1.4.23-pre.hamvoip-V1.7.1-04 app_rpt-0.327-01/22/2022 currently running on kx9rt-55929 (pid = 381)
Verbosity is at least 3
-- Accepting UNAUTHENTICATED call from 192.168.1.1:
> requested format = gsm,
> requested prefs = (gsm|ulaw|adpcm|g722|g726aal2|ilbc),
> actual format = g726aal2,
> host prefs = (g726aal2|ilbc|ulaw|gsm),
> priority = mine
-- Executing [559290@radio-secure:1] Rpt("IAX2/192.168.1.1:4569-2735", "559290") in new stack
[Jan 10 23:07:54] WARNING[27202]: app_rpt.c:15010 rpt_exec: Node 559292 IP 147.219.109.33 does not match link IP 192.168.1.1!!
== Spawn extension (radio-secure, 559290, 1) exited non-zero on 'IAX2/192.168.1.1:4569-2735'
-- Hungup 'IAX2/192.168.1.1:4569-2735'
kx9rt-55929*CLI>
Looks like you have a NAT masquerade rule set up in Unifi that is rewriting the source IP of the packet to appear as the internal IP of the Unifi itself.
Notice Asterisk is seeing the source IP as 192.168.1.1, which is the IP of your router, not the IP of the node the connection is actually coming from.
Also, do not change the IP in the top of rpt.conf. What you added there is incorrect. Leave it as:
559290 = radio@127.0.0.1:4569/559292,NONE
EDIT: I just realized as I was copying/pasting from your post… Look at that line more closely. The node # at the beginning of the line is 559290 and at the end of the line is 559292.
I missed that on my original post. It was correct in my rpt.conf file current shown as:
559290 = radio@127.0.0.1:4569/559290,NONE
Thank you Mason for the ideas on the masquerading. There is some sort of behavior that is different with the Unifi Max. I did a factory reset on the Unifi thinking that, but whatever it is, the behavior is different from the factory default from Netgear. Besides adding Wifi, I added the port forwardiing to each router on 4569. Netgear works, Unifi does not. The 192.168.1.1 does not look right as that is the gateway. Not sure what kind of interaction Allstar is having with the router that makes it different between the two routers. I’ve been working on this for a week and kind of at a loss at this point.
I wonder what is special about your setup as well. I run a Unifi Dream Machine Pro and host 3x separate ASL3 servers with no issues. I have never adjusted any NAT rules. There should not be any default NAT rules causing issues.
To clarify, these two nodes are both on your local LAN? or is one node on your LAN and the other is a WAN node?
If both nodes are on your LAN then please review Multiple Nodes on the Same Network, especially the [nodes] stanza in the /etc/asterisk/rpt.conf files on both nodes.
Allan, that solved the problem! Thank you. The documentation on that page is excellent.
I’ve been barking up the wrong tree and was misleading myself. In the past I have had 3 nodes running on the same 192.168.1.x network with no perceived issues. I only wanted one of the nodes for incoming traffic…the other two I didn’t care about. For whatever reason, I was able to connect to the one node with port forwarding to the outside world using the Netgear router. The Unifi has something different.
The solution to my problem was to follow the instructions for Multiple nodes link above. (edited both rpt.conf files, added another server on the Allstar portal site, assigned the second node to the second server, changed the second node to 4570).
Glad you figured it out… My System also will not accept incoming connections. And though I read with interest… IT’s not a problem as I don’t want to accept incoming connections… Either the Router (A Tp-Link Archer model) or the ISP is blocking incoming… (The ISP’s “modem” is also a router)
Just in case you wonder how much of a problem it is NOT for me. :
A local “Expert” attempted to connect to my node so he could “Help” me…
When he told me he was unable to connect… I Smiled…
(Of course I’d already solved the problem by then).