I’m new to ALLStar and its operations. My new node 64546 shows registered, recently seen, and port 4569 forwarded in my router is for the assigned local IP address. Using a mini-PC configured by AllScan and all seems to be as it should be. To test, I acquired the RepeaterPhone app which works well to connect to other nodes, but mine won’t ‘answer’. I’m assuming something is not correct. Radio system not yet attached but wishing to test node connectivity.
I am having exactly the same problem. Looking for solution. Scott
I’m feeling I am just missing something being new to the system and this being a newly connected node. Heck, I’m not sure how to even connect to another node for a test, being I don’t have my radio system attached yet where I can touch-tone in access codes. Perhaps someone can try to connect to my 64546 to see if they have access?
64546 is registered & reporting statistics, but not accepting connections from the outside world. Are you port forwarding the required UDP port (4569) and ensured there’s no firewall blocking it?
The port is forwarded but not being a real networking guy, I’m not sure about the firewall. I’m using a new Netgear BE9300 router and the node is connected directly into one of its rear ports and my assigned IP of 192.168.1.107 has port 4569 forwarded. Would the router have a firewall on it? I believe my home PC does through Norton but this is well after the router.
The node itself might have a local firewall like ufw running. Try monitoring the node using sudo asterisk -rvvv and try connecting to it. See what gets logged.
I get a lot about asterisk and it license. Below a line after that is “Connected to Asterisk 20.11.0+asl3-3.2.0.deb12 currently running on t5 (pid=1094)
t5*CLI>
OK now see what (if anything) you see from attempted connections.
How do I get out of the T5*CLI prompt? From here it won’t accept sudo asterisk -rvvv
Did you specifically forward UDP 4569 rather than TCP or both?
I can’t connect to your node. Appears to be a standard timeout, I.E. can’t reach the server, so nothing would show up in your log from Asterisk CLI.
Yeah, I’m working with Netgear now about the IP reservation process. Git it reserved now so will see.
Type quit or exit to leave the CLI. So you’ve seen nothing since you ran sudo asterisk -rvvv?
I saw back on my node, after while I’ve been also working with Netgear, a series of ‘Remote Unix connection disconnected entries.
The exit got me back to where I could sudo asterisk -rvvv in; same notice as before. Need a minute. Netgear is having me reboot.
N2DYI - yes, UDP 4569 only, because I wasn’t getting anywhere with both selected.
If you saw nothing else in the CLI after you ran it, then packets are not reaching your node. If port forwarding is correct, then that leaves a firewall or asl3+asterisk configuration as suspects.
I appreciate everyone’s advice! Looks like I’m going to have to look into the firewall aspect. I’m using an Xfinity Comcast modem which has the RJ45 outputs to my router. I’m going to contact Comcast to see if they have a firewall running.
OK. Next (possibly dumb) question:
You are on Comcast using a Netgear router. Are you connecting your router to a Comcast gateway, or your own modem? If so, is it in bridge mode? If not, then your router is being blocked upstream by another layer of NAT, and port forwarding to devices behind the Netgear won’t work.
I am connecting my router to the Comcast gateway. There is no other modem. As for the bridge mode, not sure how I can check for this. I’m planning on contacting Comcast support. Perhaps they can advise me on what’s going on.
Exit with exit !
cli>exit
Returns to a OS command line.
This issue is with repeaterphone setup most likely. But Can’t say that for sure with info provided.
You may have more than one issue you are dealing with.
I can not connect to 64546