Some routers don’t do what is called hairpin NAT. That is connecting from an address on your NATed to the public IP address of a service on the same NATed network won’t work.

Or the problem could be that your servers are set to the same port and/or the router port forwarding is not correct.

In any case nodes on the same NATed network should have the IP address of the other nodes listed in the [nodes] stanza of rpt.conf. The port is needed if not default (4569).

[nodes]

; Note, if you are using automatic update for allstar link nodes,

; no allstar link nodes should be defined here. Only place a definition

; for your local nodes, and private (off of allstar link) nodes here.

2510 = radio@127.0.0.1:4570/2510,NONE                    ; Local node

2502 = radio@192.168.1.12:4571/2502,NONE		 ; other node

--
Tim
:wq

On Feb 9, 2015, at 9:11 AM, Mike Lussier <mike.lussier@gmail.com> wrote:

Good afternoon all,
I have two nodes on my internal network. both on the same subnet. for the past 16 hours if I look at either node that show state as "Connecting" and not connected .

Any thoughts ? I tried it once from one node running a script and before I went to bed last night I tried it from the other side.

Mike AE4ML

--
"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.