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
a node behind your nat but on a different server?
a node on the same server?
a external node outside of your nat?
You probably need to define more info for other nodes behind your nat but
on other servers.
Specifying the ip & port used in rpt.conf of the other servers "if" that
is the case.
The line above shows the ip and port used of the other server inside of
nat. the top line is a node local to the box/server.
You would need to do this in each box behind your nat with proper ip/port
to connect between them.
...mike/kb8jnm
···
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.
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
···
“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
Mike,
It was not clear from your statements if you were ever able to connect them or if the script was the problem. If its two (or more) nodes on the same LAN on different computers (servers) they would need routing information in the nodes section of rpt.conf so they connect locally and do not try and use the public IP. You would need to do this on both servers. They should also be on different ports setup at allstarlink.org
[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.
40000 = radio@127.0.0.1/40000,NONE
40001 = radio@192.168.1.100:4568,NONE <<<< IP and port of other local server
On the other server it would be just reversed with the other nodes port. 4569 is default but shown here for clarity.
40001 = radio@127.0.0.1/40000,NONE
40000 = radio@192.168.1.100:4569,NONE <<<< IP and port of other local server 73 Doug
WA3DSP http://www.crompton.com/hamradio
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
I figured with them on the same subnet they would talk directly to each other and there was no need to go out to the internet to make their connection.
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
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
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.
–
“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
Corrected… the IPs and /nodes were not correct in the previous example…
40000 = radio@127.0.0.1/40000,NONE
40001 = radio@192.168.1.100:4568/40001,NONE <<<< IP and port of other local server
On the other server it would be just reversed with the other nodes port. 4569 is default but shown here for clarity.
40001 = radio@127.0.0.1/40001,NONE
40000 = radio@192.168.1.101:4569/40000,NONE <<<< IP and port of other local server 73 Doug
WA3DSP http://www.crompton.com/hamradio
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
Nodes will attempt to connect to the public IP unless you tell them not to with the [nodes] stanza.
If you know how a hosts file works it the same sort of thing: App_rpt first looks for the node’s IP address in the [nodes] stanza. If not found it looks in the rpt_extnodes file. Being that you didn’t have the node listed in your [nodes] stanza it uses rpt_extnodes and hence the public IP.
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
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
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.
–
“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
Nodes will attempt to connect to the public IP unless you tell them not to with the [nodes] stanza.
If you know how a hosts file works it the same sort of thing: App_rpt first looks for the node’s IP address in the [nodes] stanza. If not found it looks in the rpt_extnodes file. Being that you didn’t have the node listed in your [nodes] stanza it uses rpt_extnodes and hence the public IP.
I figured with them on the same subnet they would talk directly to each other and there was no need to go out to the internet to make their connection.
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
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
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.
– “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
“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
Problem resolved instantly as soon as I added the privates under the stanza [node]
Thank you all
Mike AE4ML
···
On Mon, Feb 9, 2015 at 1:13 PM, Doug Crompton doug@crompton.com wrote:
Mike,
It was not clear from your statements if you were ever able to connect them or if the script was the problem. If its two (or more) nodes on the same LAN on different computers (servers) they would need routing information in the nodes section of rpt.conf so they connect locally and do not try and use the public IP. You would need to do this on both servers. They should also be on different ports setup at allstarlink.org
[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.
40000 = radio@127.0.0.1/40000,NONE
40001 = radio@192.168.1.100:4568,NONE <<<< IP and port of other local server
On the other server it would be just reversed with the other nodes port. 4569 is default but shown here for clarity.
40001 = radio@127.0.0.1/40000,NONE
40000 = radio@192.168.1.100:4569,NONE <<<< IP and port of other local server 73 Doug
WA3DSP http://www.crompton.com/hamradio
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
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.
–
“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
I can get “connecting” if the target system is in a mode that does not accept new connections. This has happened when I was running a bulletin where the script got interrupted and never put things back in the normal mode.
73
Ken
···
From: Mike Lussier [mailto:mike.lussier@gmail.com] Sent: Monday, February 09, 2015 12:11 PM To: ALL STAR Subject: [App_rpt-users] 2 nodes setup to auto connect don’t seem to work
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