New setup of ASL3 on a PI 4b attempting to get inbound connections. I currently have one node running on my network now, so this is number 2. Number 1 is working fine on 4569
What I have done so far:
Configured router for static IP address setting to Node
Forwarded UDP port 4570 in router.
Set UDP port 4570 in Node Settings -> Update Asterisk IAX port (and confirmed)
Set up a second new server at Allstarlink.org
Set new server IAX port to 4570
Set new node to new server confirmed
Node access list is set to "open"
Post node status is "yes" if that makes a difference
Still when I attempt to connect from outside my network, search finds the new node, new node connects then immediately hangs up the connection.
Node 655100 (older working well)
Node 655101 (new being configured)
Yes, I have forwarded udp port 4570 for 655101 identically the way I did 4569 for 655100.
They are running on two different servers at allstarlink.org
The original server is running 655100 and set to udp port 4569
The new server is running 655101 and set to udp port 4570
655100 is servicing and connected to our club Yaesu DR2x repeater currently being housed at my home. This is a Node-Ventures ClearRpt node running flawlessly so far.
The 655101 is being developed as hotspot for me when the club repeater moves to its permanent site.
The connection that fails is from my iphone 12 running RepeaterPhone. I can connect to 655100 with no issues.
When I attempt to connece to 655101 to test it, the connection opens then immediately closes.
I have RepeaterPhone on my iPhone12 also and sometimes it connects sometimes it does not. Some nodes it will never connect to. I chalk it up to issues with RepeaterPhone
GeorgeC W2DB
This is an entirely different matter than you first posted.
This is not a matter of 2 nodes connecting.
The problem is your repeaterphone setup somewhere.
In the app or the asl/iax? setup.
Sorry, I don't use it to be able to help you better.
Review the instructions again line by line as you likely missed something or a fat finger error.
I have two separate Raspberry nodes behind the same router. An issue I found this week has to do with calling from RepeaterPhone when VPN is on. That blocks the connection
This would say 'only 192.168.0.23' could connect.
iax wildcard is in order.
Anything can connect, or try to.
Security is covered by the nodelist data or other specific stanza setup.
But a check to stanza name & user/pass for the application is in order.
Including the 'type' connection.
I think the bindaddr defines the interface, not a whitelist. My understanding is that 0.0.0.0 means 'accept connections on all interfaces' while an address restricts listening to a single interface.
All IP's.
Interfaces are not in decision here.
So, yes a bindaddr=192.168.0.23 would mean that it is the only IP allowed to connect or bind to iax.
However, you can bind to more than one static address, or a range of addresses.
But there is no help specifying a single static address if 0.0.0.0 is not doing it.
Even at the troubleshooting level.
Specifying exact addresses/range would be a security measure to block anything other than them.
If you did this in iax, you would not get connects from asl, except from those addresses listed.
Do both the conectee and connecting nodes have a private node number connected to them that is of the same number ? And even any public node of the same number.
If you have two interfaces with the same IP address, you have other problems. I think the manual refers to addresses, but in most ASL3 cases this is equivalent to interfaces. There was supposed to be a "*" operator for this so I could do something like bindaddr=192.168.1.* to allow all addresses bound to interfaces only on my local net, but I had no luck with that.
EDIT: The situation would be different when monitoring a remote system, of course. I think you're stuck with 0.0.0.0 in that case.
