I have an Allstarlink Server (Raspberry Pi with the official Image) running inside a network which
can’t have/does not support port forwarding. So what I did is settings up a proxy server for UDP port 4569 on a server in the Internet (IP is 65.109.113.117 as shown in the screenshot below).
When I directly connect to this IP on port 4569 with my SharkRF M1KE it works perfectly.
However, in the list of nodes/servers, when I select my server (DO1MJ), a different IP address shows up (probably the external IP of my home network) and not the Proxy IP I configured in the server settings. It seems like this setting is not being used?
yes, it's ASL3, Node Number is 65412, yes, I need to register with the static Proxy IP because my Node is behind Carried Grade NAT with no way in for any traffic. The IP address that is being sent in the list of all Allstarlink-Nodes is "176.83.120.23" and not "65.109.113.117".
Well, I have never used a proxy with asl, but you kinda answered yourself.
When registering, the server is using it's actual WAN IP.
You need to change something likely in your network so it's registering with your proxy.
The registration system updates frequently to catch changes, so whatever ip it registers with is what it uses and puts in the node list to be securely evaluated for connection.
I have to say I don't know what the setting in the self service portal actually does.
It does seem natural to think it would change what is being reported in the node list data.
I believe there is a way to setup a second network and select it on same if.
No experience with such things, so, perhaps someone has a better answer.
But it seems from your text that what you actually need is a port proxy.
Can't you use a different port and port and forward it to the needed port at your router ?
If you fail to get a resolution, perhaps try the helpdesk on the proxy in the self service.
Specifying a proxy IP for a server, and then associating one or more nodes to that server, will cause the proxy IP used in the connection database rather than the 'discovered' IP address. Calling it a "proxy" is incorrect nomenclature. It's basically "My IP is always this regardless of what the registration servers see". It's only useful/functional in a very limited set of advanced circumstances.
Yes, that is also what I thought. But my point is: it's not working. I entered a "Proxy IP" in the server settings and attached a node to it and still this Proxy IP is not being delivered from the connection database. So it seems like there is something wrong with this setting...
Hello Mike, thanks for all the information. I contacted the helpdesk already and they asked me to contact the community because it's not something that they can help with.
Sure. With my SharkRF M1KE, when I connect to my Node DO1MJ (65412), the IP address in the node list is the one shown in the image. My expectation would be that the static configured "ProxyIP" (65.109.113.117) is returned but it seems it's not. You can try it yourself. Search for "DO1MJ" in the node list and when the IP address of the node is not "65.109.113.117" it's not the correct one.
I'm not sure what app you're looking at there but the AllStarLink database is returning 65.109.113.117 for node 65412. That is what is configured in the ASL portal for your server labelled "PRIVATE" and what's in the DNS and file databases:
