Node IP does not match link IP

AllStarLink
1

Setup Information

********** AllStarLink [ASL] Version Info **********

OS : Debian GNU/Linux 13 (trixie)
OS Kernel : 6.12.62+rpt-rpi-v8

Asterisk : 22.7.0+asl3-3.7.1-1.deb13
ASL [app_rpt] : 3.7.1

*******************************************************

We built a RPi3 node to use at the repeater site and spent over a Month testing it .. Took it to different cities, used Mobile hot spots, connected via wi-fi and cat5 .. Everythng we could think of .. It was working great ..

It is now installed at a secure facillity that has graciously provided us with a public facing static IP address and NO firewalls or packet controls .. I have spoke several times with their network engineer and he assures me NOTHING is being blocked or dropped from the network side ..

Since this node has been installed at this new location it will NOT acccept any incoming ASL connections … We CAN connect to other node from it just not inbound connections … and .. The echolink will only accept one connection then it locks up freezes …

If we try to make a second connection with ecolink it calls the first user back over and over and over … a constant loop till reboot … It also shows echolink connections as the same node number as the account echolink number instead of the users own number … Never seen that before either.

The only change was the source of the internet service ...

I have read, searched and read some more and nothing helps with either connection issue ..

We can connect to other nodes from it just not inbound connections …

LOG MESSAGES :

Call to Log :

[2026-02-19 13:32:09.772] WARNING[3976][C-0000001b]: app_rpt.c:6254 parse_caller: Node 67468 IP 44.27.xxx.xxx does not match link IP 216.125.xxx.xxx!!

Call From Log:

Connected to Asterisk 22.7.0+asl3-3.7.1-1.deb13 currently running on node67468 (pid = 1231)
== Manager 'admin' logged on from 127.0.0.1
== Manager 'admin' logged off from 127.0.0.1
-- Call accepted by 216.125.xxx.xxx:4569 (format ulaw)
-- Format for call is (ulaw)
-- Hungup 'IAX2/216.125.xxx.xxx:4569-2037'
-- Hungup 'DAHDI/pseudo-2060859875'

The 67468 is MY node number and the 44.27.xxx.xxx is MY address and the 216.125.xxx.xxx is the device installed at the new facillity …

I have had other users try to connect and we get the same error message except with THEIR node number and IP address …

We have check the rpt_extnodes file and they are current and up to date .. We tried IAX2 registration instead of HTML and nothing changed …

Any help would be appreciated ..

2

For some reason when I looked up 67468 it is showing iax port 4669 and in your info you are showing 4569 port and I would think that is right so you either have the server port at allstarlink org set wrong or the pi port is set wrong I would start there.

Then look at the port forward or the pi firewall to make sure you can get form the 44net to the node once you get the port 4569 set to match all-star and node.

3

Correct my node is using port 4669 and the device that is rejecting ALL the calls is using 4569 ..

The node that is rejecting is rejecting ALL nodes connecting trying to connect to it not just my node .. and it is always the same message node IP mismatch …

The calling station gets the mesage that it answered then an immediate message IAX2 hungup ...

I thought for certain it was going to be a registration problem but I did try both IAX and HTML registration and neither cured the issue ..

4

So what node are you trying to connect to as so far I do not see that in the info above.

Earl

W9EJH

5

(post deleted by author)

6

The node that won’t take connections inbound is 419310 … My Node is 67468 … BUT .. I can’t get any nodes to inbound connect to 419310 … The logs just keep giving me the IP mismatch error .. no matter who trys to connect ..

7

On 419310, can you try our recently announced asl-node-auth-check tool :

asl-node-auth-check: New Tool for Authentication and Node Reachability Testing

8

ok so now I have this info from you and I did try to connect to 419310 as well and that is at iax port 4569 you will just need to make sure the server port at allstarlink.org is set to port 4569 for that node as I see there are 3 more nodes for K9ONA as well and each other node should each have their own servers so

419310 server should be port 4569

419311 server should be port 4568

419312 server should be port 4567

419313 server should be port 4566

and then make sure that on that wire or wifi that is feeding that node you can do a ip address lookup from the world maybe with a laptop and do whatsmyip.org and see if you get back 216.125.50.29 and if you do then make sure if you have a router that ip address is on the WAN side of the router if it is not then you have a CGNAT box in the middle of the equation and you will never get to that port 4569 if the WAN is ok then make sure the port forward is in place to the local ip address as you have not gave me the whole setup at this point yet, once you get that checked we will be able to get the iax connection to work as planned.

9

I did just check again and I think you still do not have the port either forwarded or the unit is behind a CGNAT box as I do see it registered but the port 4569 is blocked for sure.

10

OK I can see that your public ip address is ok as I can connect to cockpit screen, and I can connect to allmon3 screen so I would think the next step is to check to make sure allstarlink.org you have the sever setup right and only one port per server next. make sure there is only one server on port 4569 and that the node is connected to that server for 419310. also in the node configuration make sure it is set up to port 4569 as I think it is but recheck it any way.

I also see you are dealing with a school firewall as well on that ip address blocking that port 4569

District 86 - Access Blocked

Web Page Blocked

This web page is in violation of the HTHSD 86 Internet usage policy.

|
Category
|
Unrated
|
|----|----|
|
URL
|

http://216.125.50.29/

|
undefined|----|----|
|
Policy ID
|
#152
|
undefined|----|----|
|
Policy UUID
|
33eb0956-01f6-51f1-bf8e-94c098aa8729
|
undefined|----|----|

If you require further assistance please contact the D86 Helpdesk or

click here

.This will be resolved once the school firewall IT personal can resolve the blocking of ports 4569 UDP traffic for allstar, 5198,5199 UDP Traffic ,5200 TCP Traffic for echolink has been taken care of.