Re: [App_rpt-users] Nodes on same server linked, but not repeating audio?
Jeremy, Each server in a LAN subnet must have a separate port; but all nodes on a given server use the one server UDP port. If you are having issues between nodes on the same LAN, try using the LAN IPs in the [NODES] stanza instead of the loop back 127.0.01. K5TRA
On 11/1/17 4:58 PM, Tom wrote:
Each server in a LAN subnet must have a separate port; but all nodes on a given server use the one server UDP port.
This is wrong. The servers will have different IP addresses and UDP ports are only significant per IP address. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
Lets get back to the original post. One server three nodes. Nodes are not able to connect to each other on the same server. My guess: 1) loopback IP's are getting blocked or miss routed. 2) Server loses integrity over time 2)app_rpt is not reading the node stanza in rpt.conf. What does Asterisk cmd say when the error presents itself? i.e. when you try to connect one node to another? Verbose should be high. You can turn on logging. /etc/asterisk/logger.conf messages => notice,warning,error,debug,verbose "Be warned that logging could fill your hard drive fast" Is there any other services on this server? David KE6UPI -- Thanks, David "Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson On Wed, Nov 1, 2017 at 2:00 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/1/17 4:58 PM, Tom wrote:
Each server in a LAN subnet must have a separate port; but all nodes on a given server use the one server UDP port.
This is wrong. The servers will have different IP addresses and UDP ports are only significant per IP address.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
Exactly how are you linking them? Via touchtone 3=ilink,3 or C=ilink,13 or startup_macro maybe something else? What happens if you un-link them and then re-link them? Are you using "locallist" or "locallinknodes" anywhere in your config? And on a different subject..... (unrelated since your nodes are all on the same server) About port numbers, and maybe someone else already pointed this out, they need to be different on each server that is on the same LAN together if they are all NATed to one globally unique IP address by the router. If each server has it's own globally unique IP address then they can have the same port number on each server. Chuck On Wed, Nov 1, 2017 at 6:06 PM, David Shaw <shawpbx@gmail.com> wrote:
Lets get back to the original post.
One server three nodes. Nodes are not able to connect to each other on the same server.
My guess: 1) loopback IP's are getting blocked or miss routed. 2) Server loses integrity over time 2)app_rpt is not reading the node stanza in rpt.conf.
What does Asterisk cmd say when the error presents itself? i.e. when you try to connect one node to another? Verbose should be high.
You can turn on logging. /etc/asterisk/logger.conf
messages => notice,warning,error,debug,verbose
"Be warned that logging could fill your hard drive fast"
Is there any other services on this server?
David KE6UPI
-- Thanks, David
"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one." Thomas Jefferson
On Wed, Nov 1, 2017 at 2:00 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/1/17 4:58 PM, Tom wrote:
Each server in a LAN subnet must have a separate port; but all nodes on a given server use the one server UDP port.
This is wrong. The servers will have different IP addresses and UDP ports are only significant per IP address.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/c gi-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.
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
On 11/2/17 5:54 PM, Chuck Henderson wrote:
Exactly how are you linking them? Via touchtone 3=ilink,3 or C=ilink,13 or startup_macro maybe something else?
startup_macro=*95341618 on 40821 node config. 953=ilink,13 ; Permanent link transceive
What happens if you un-link them and then re-link them?
The problem clears.
Are you using "locallist" or "locallinknodes" anywhere in your config?
no, just nolocallinkct=1
And on a different subject..... (unrelated since your nodes are all on the same server) About port numbers, and maybe someone else already pointed this out, they need to be different on each server that is on the same LAN together if they are all NATed to one globally unique IP address by the router.
NAT's a totally different thing. It's just evil :) I think I said this before https://youtu.be/mkKOX5q1XJ4?t=2227
If each server has it's own globally unique IP address then they can have the same port number on each server.
Well not to be that guy, but really only on the NAT public interface. Internal IP 1:4569 >Outside IP:4569 Internal IP 2:4569 >Outside IP:4570 Internal IP 3:4569 >Outside IP:4571 This should work. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
On Nov 2, 2017, at 11:14 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
If each server has it's own globally unique IP address then they can have the same port number on each server.
Well not to be that guy, but really only on the NAT public interface.
Internal IP 1:4569 >Outside IP:4569 Internal IP 2:4569 >Outside IP:4570 Internal IP 3:4569 >Outside IP:4571
This should work. -- Bryan Fields
727-409-1194 - Voice http://bryanfields.net
Bryan, I experienced a problem with Port-translation similar to what you described, when trying to access a friends site using Supermon. When his internal port number did not match the external port number translated by his router, I could not connect to his node. Based on that, I would recommend you do this instead:
Internal IP 1:4569 >Outside IP:4569 Internal IP 2:4570 >Outside IP:4570 Internal IP 3:4571 >Outside IP:4571
I am new to Allstar/Asterisk and don't know the protocol details, but it appears to me that the absolute port number is important - at least for some things. I have done port-translation with HTTP which works just fine, but Allstar appears to have problems with this. -Andy, PB7B/KB7B Allstar: 42432
This should work` Maybe it should but I don't think it will. The problem with the servers all thinking that their public port is 4569 is that then the registration system will advertise them with the wrong port unless other steps are taken to modify the registration info. At least that is what I ran into when I first tried to do it years ago like you suggested. I found the simple fix was to have each server on a different port, same as Andy is saying. Maybe now the registration servers are newer and improved and they pick up NATed ports during registration. I don't know. I am a dinosaur, I know it. I am CCIE2285 I helped write some of the code that runs in Cisco routers. I greatly improved the IPV4 NAT code in Cisco routers (in the beginning) and really made it work well and scale better. Most of the advanced NAT features that I designed are still in all Cisco routers and L3 switches but are not used because almost no one knows how to configure them. So I have to disagree about NAT being evil. It is wonderful if you know how to configure it.
I watched the video. Sorry, there currently is no IPV6 in the voter board or the RTCM but they are still very useful. Maybe you can write the IPV6 for them. I am aware of a couple of bugs in the app_rpt.c that were never fixed by Jim despite me identifying them and what was causing them. Yours could be related and I will look for my notes about what I had found and see if those parts of the code are still the same. One of the bugs I had tracked down was a bug that under specific situations would send all transmit audio out over the links including local only audio like IDs and tones. Apparently, I was the only one who experienced it even though Jim could reproduce it with my info. As I remember he gave me the " locallist" and "locallinknodes" commands to work around the bug. That was too long ago and I don't still have the configurations that needed that and I don't see any documentation for them so I will have to dig through notes from long ago to re-find that info. As I recall, I think it was a sequence of keydowns back and forth between the linked local nodes aligning with an ID that would induce the strange problems reliably every time. Unlinking the permalinks and re-linking would fix it until the next time. Now I have separate computers for each node so it isn't an issue for me now like it was back then. While typing this little pieces of memory are coming back to me. Maybe after my regeneration cycle tonight I will remember it all. Maybe I have jogged someone else's memory who can fix this before I can remember it. Chuck On Fri, Nov 3, 2017 at 3:16 AM, andy_kb7b <andy_kb7b@yahoo.com> wrote:
On Nov 2, 2017, at 11:14 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
If each server has it's own globally unique IP address then they can have the same port number on each server.
Well not to be that guy, but really only on the NAT public interface.
Internal IP 1:4569 >Outside IP:4569 Internal IP 2:4569 >Outside IP:4570 Internal IP 3:4569 >Outside IP:4571
This should work. -- Bryan Fields
727-409-1194 - Voice http://bryanfields.net
Bryan,
I experienced a problem with Port-translation similar to what you described, when trying to access a friends site using Supermon. When his internal port number did not match the external port number translated by his router, I could not connect to his node.
Based on that, I would recommend you do this instead:
Internal IP 1:4569 >Outside IP:4569 Internal IP 2:4570 >Outside IP:4570 Internal IP 3:4571 >Outside IP:4571
I am new to Allstar/Asterisk and don't know the protocol details, but it appears to me that the absolute port number is important - at least for some things. I have done port-translation with HTTP which works just fine, but Allstar appears to have problems with this.
-Andy, PB7B/KB7B Allstar: 42432
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
This should work` Maybe it should but I don't think it will. The problem with the servers all thinking that their public port is 4569 is that then the registration system will advertise them with the wrong port unless other steps are taken to modify the registration info. At least that is what I ran into when I first tried to do it years ago like you suggested. I found the simple fix was to have each server on a different port, same as Andy is saying. Maybe now the registration servers are newer and improved and they pick up NATed ports during registration. I don't know. I am a dinosaur, I know. CCIE2285 I helped write some of the code that runs in Cisco routers. I greatly improved the IPV4 NAT code in Cisco routers (in the beginning) and really made it work well and scale better. Most of the advanced NAT features that I designed are still in all Cisco routers and L3 switches but are not used because almost no one knows how to configure them. So I have to disagree about NAT being evil. It is wonderful if you know how to configure it.
I watched the video. Sorry, there currently is no IPV6 in the voter board or the RTCM but they are still very useful. Maybe you can write the IPV6 for them. I am aware of a couple of bugs in the app_rpt.c that were never fixed by Jim despite me identifying them and what was causing them. Yours could be related and I will look for my notes about what I had found and see if those parts of the code are still the same. One of the bugs I had tracked down was a bug that under specific situations would send all transmit audio out over the links including local only audio like IDs and tones. Apparently, I was the only one who experienced it even though Jim could reproduce it with my info. As I remember he gave me the " locallist" and "locallinknodes" commands to work around the bug. That was too long ago and I don't still have the configurations that needed that and I don't see any documentation for them so I will have to dig through notes from long ago to re-find that info. As I recall, I think it was a sequence of keydowns back and forth between the linked local nodes aligning with an ID that would induce the strange problems reliably every time. Unlinking the permalinks and re-linking would fix it until the next time. Now I have separate computers for each node so it isn't an issue for me now like it was back then. While typing this little pieces of memory are coming back to me. Maybe after my regeneration cycle tonight I will remember it all. Maybe I have jogged someone else's memory who can fix this before I can remember it. Chuck On Thu, Nov 2, 2017 at 5:14 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 11/2/17 5:54 PM, Chuck Henderson wrote:
Exactly how are you linking them? Via touchtone 3=ilink,3 or C=ilink,13 or startup_macro maybe something else?
startup_macro=*95341618 on 40821 node config. 953=ilink,13 ; Permanent link transceive
What happens if you un-link them and then re-link them?
The problem clears.
Are you using "locallist" or "locallinknodes" anywhere in your config?
no, just nolocallinkct=1
And on a different subject..... (unrelated since your nodes are all on the same server) About port numbers, and maybe someone else already pointed this out, they need to be different on each server that is on the same LAN together if they are all NATed to one globally unique IP address by the router.
NAT's a totally different thing. It's just evil :)
I think I said this before https://youtu.be/mkKOX5q1XJ4?t=2227
If each server has it's own globally unique IP address then they can have the same port number on each server.
Well not to be that guy, but really only on the NAT public interface.
Internal IP 1:4569 >Outside IP:4569 Internal IP 2:4569 >Outside IP:4570 Internal IP 3:4569 >Outside IP:4571
This should work. -- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
On 11/3/17 4:45 AM, Chuck Henderson wrote:
Maybe it should but I don't think it will. The problem with the servers all thinking that their public port is 4569 is that then the registration system will advertise them with the wrong port unless other steps are taken to modify the registration info. At least that is what I ran into when I first tried to do it years ago like you suggested. I found the simple fix was to have each server on a different port, same as Andy is saying. Maybe now the registration servers are newer and improved and they pick up NATed ports during registration. I don't know.
It's set in the server config in the portal. But yea, I'd tend to agree from an operational perspective, just keep the UDP ports the same on the inside and outside.
I am a dinosaur, I know. CCIE2285 I helped write some of the code that runs in Cisco routers. I greatly improved the IPV4 NAT code in Cisco routers (in the beginning) and really made it work well and scale better. Most of the advanced NAT features that I designed are still in all Cisco routers and L3 switches but are not used because almost no one knows how to configure them. So I have to disagree about NAT being evil. It is wonderful if you know how to configure it.
ALU NRSexpert here, all my other certs expired long ago. Though I did interview a guy in his CCIE bomber jacket a few months back ;) Cisco's certainly diluted their certs value, it's a profit center now. I do know the difference between a route-map and an ACL for NAT overload in IOS classic, FWIW. I even had a bit of NAT with a VRF looped back to allow mapping TCP port on one server to a port on a VRF loopback. It's disgusting to even recall it. NAT breaks the internets goal of end-to-end connectivity. It's evil, and I'll proclaim it loudly. Now it can be useful for certain things, but I'd rather have globally unique addresses in the first place.
I watched the video. Sorry, there currently is no IPV6 in the voter board or the RTCM but they are still very useful. Maybe you can write the IPV6 for them.
I'd love to, but I think we'd need to consider separating the IP/mgmt from the real time parts of the RTCM. We'd also need to get on a newer version of asterisk too. I think we'd all be in agreement about moving to a more recent version. I got down this rat hole from time to time with a friend of mine on how to improve the RTCM.
I am aware of a couple of bugs in the app_rpt.c that were never fixed by Jim despite me identifying them and what was causing them. Yours could be related and I will look for my notes about what I had found and see if those parts of the code are still the same. One of the bugs I had tracked down was a bug that under specific situations would send all transmit audio out over the links including local only audio like IDs and tones. Apparently, I was the only one who experienced it even though Jim could reproduce it with my info. As I remember he gave me the " locallist" and "locallinknodes" commands to work around the bug. That was too long ago and I don't still have the configurations that needed that and I don't see any documentation for them so I will have to dig through notes from long ago to re-find that info. As I recall, I think it was a sequence of keydowns back and forth between the linked local nodes aligning with an ID that would induce the strange problems reliably every time. Unlinking the permalinks and re-linking would fix it until the next time. Now I have separate computers for each node so it isn't an issue for me now like it was back then. While typing this little pieces of memory are coming back to me. Maybe after my regeneration cycle tonight I will remember it all. Maybe I have jogged someone else's memory who can fix this before I can remember it.
If you can document it or publish it, I'm sure we can get it fixed. I'm almost certain I'm seeing some buffer overflow or similar bug here. 73 -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
On Nov 3, 2017, at 9:45 AM, Chuck Henderson <rpt2@chuck.midlandsnetworking.com> wrote:
This should work` Maybe it should but I don't think it will. The problem with the servers all thinking that their public port is 4569 is that then the registration system will advertise them with the wrong port unless other steps are taken to modify the registration info. At least that is what I ran into when I first tried to do it years ago like you suggested. I found the simple fix was to have each server on a different port, same as Andy is saying. Maybe now the registration servers are newer and improved and they pick up NATed ports during registration. I don't know. I am a dinosaur, I know. CCIE2285 I helped write some of the code that runs in Cisco routers. I greatly improved the IPV4 NAT code in Cisco routers (in the beginning) and really made it work well and scale better. Most of the advanced NAT features that I designed are still in all Cisco routers and L3 switches but are not used because almost no one knows how to configure them. So I have to disagree about NAT being evil. It is wonderful if you know how to configure it.
I watched the video. Sorry, there currently is no IPV6 in the voter board or the RTCM but they are still very useful. Maybe you can write the IPV6 for them.
I am aware of a couple of bugs in the app_rpt.c that were never fixed by Jim despite me identifying them and what was causing them. Yours could be related and I will look for my notes about what I had found and see if those parts of the code are still the same. One of the bugs I had tracked down was a bug that under specific situations would send all transmit audio out over the links including local only audio like IDs and tones. Apparently, I was the only one who experienced it even though Jim could reproduce it with my info. As I remember he gave me the "locallist" and "locallinknodes" commands to work around the bug. That was too long ago and I don't still have the configurations that needed that and I don't see any documentation for them so I will have to dig through notes from long ago to re-find that info. As I recall, I think it was a sequence of keydowns back and forth between the linked local nodes aligning with an ID that would induce the strange problems reliably every time. Unlinking the permalinks and re-linking would fix it until the next time. Now I have separate computers for each node so it isn't an issue for me now like it was back then. While typing this little pieces of memory are coming back to me. Maybe after my regeneration cycle tonight I will remember it all. Maybe I have jogged someone else's memory who can fix this before I can remember it.
Chuck
Chuck, With all your Asterisk experience, might I ask a question? I remember reading something (probably on the ohnosec site) stating that the "convention" was to number additional Allstar ports down from 4569. In other words 4568, 4567 ... etc. Of course I cannot seem to find this reference today. Assuming you remember such a reference, can you tell me whether there are any performance reasons behind it, or is it completely arbitrary? In other words, does the Asterisk code pay special attention to (or waste any time on) ports 4570 or above? Thank you for whatever you might remember. -Andy, PB7B/KB7B 42432
I have used a wide variety of ports with no problems. It only listens where you tell it to listen. IMHO there are some advantages to some security by obscurity. Just like putting the ssh access on 222, Putting Asterisk on randomly chosen ports seemed to decrease the number of attempted attacks that I saw. I have even changed some of my servers to not use 222 but to use other different ports for ssh. On Fri, Nov 3, 2017 at 7:09 AM, andy_kb7b <andy_kb7b@yahoo.com> wrote:
Chuck,
With all your Asterisk experience, might I ask a question?
I remember reading something (probably on the ohnosec site) stating that the "convention" was to number additional Allstar ports down from 4569. In other words 4568, 4567 ... etc. Of course I cannot seem to find this reference today.
Assuming you remember such a reference, can you tell me whether there are any performance reasons behind it, or is it completely arbitrary? In other words, does the Asterisk code pay special attention to (or waste any time on) ports 4570 or above?
Thank you for whatever you might remember.
-Andy, PB7B/KB7B 42432
I've had no issues with going up or down for the UDP port. I've also had no issues with SSH in the 40,000+ range. tnx Mike / W5JR Alpharetta GA sent via my HP95LX
On Nov 7, 2017, at 3:39 AM, Chuck Henderson <rpt2@chuck.midlandsnetworking.com> wrote:
I have used a wide variety of ports with no problems. It only listens where you tell it to listen. IMHO there are some advantages to some security by obscurity. Just like putting the ssh access on 222, Putting Asterisk on randomly chosen ports seemed to decrease the number of attempted attacks that I saw. I have even changed some of my servers to not use 222 but to use other different ports for ssh.
On Fri, Nov 3, 2017 at 7:09 AM, andy_kb7b <andy_kb7b@yahoo.com> wrote:
Chuck,
With all your Asterisk experience, might I ask a question?
I remember reading something (probably on the ohnosec site) stating that the "convention" was to number additional Allstar ports down from 4569. In other words 4568, 4567 ... etc. Of course I cannot seem to find this reference today.
Assuming you remember such a reference, can you tell me whether there are any performance reasons behind it, or is it completely arbitrary? In other words, does the Asterisk code pay special attention to (or waste any time on) ports 4570 or above?
Thank you for whatever you might remember.
-Andy, PB7B/KB7B 42432
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.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.
participants (6)
-
andy_kb7b -
Bryan Fields -
Chuck Henderson -
David Shaw -
Mike - W5JR -
Tom