DNS and IAX2 registration notices

I am running an older ACID version of Allstar.

Have set verbose level to as small I know how. Is there anyway to stop
the continual CLI display of “Refreshing DNS lookups”
plus the ongoing “-- Registered IAX2” continual notices which swap
many times more than the 3 times in the example below.

The clutter from this is annoying when trying to monitor activity on my
nodes.

Larry N7FM

== Refreshing DNS lookups.
– Registered IAX2 to ‘192.83.199.4’, who sees us as
69.28.37.6:40599 with no messages waiting

 -- Registered IAX2 to '216.244.83.154', who sees us as 

69.28.37.6:10996 with no messages waiting

 -- Registered IAX2 to '192.83.199.4', who sees us as 

69.28.37.6:40599 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘44.72.21.13’, who sees us as 69.28.37.6:6765
with no messages waiting

 -- Registered IAX2 to '178.32.160.82', who sees us as 

69.28.37.6:54779 with no messages waiting

 -- Registered IAX2 to '178.32.160.85', who sees us as 

69.28.37.6:36206 with no messages waiting

 -- Registered IAX2 to '178.32.160.82', who sees us as 

69.28.37.6:58483 with no messages waiting

 -- Registered IAX2 to '44.72.21.13', who sees us as 69.28.37.6:6765 

with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘192.83.199.4’, who sees us as
69.28.37.6:13993 with no messages waiting

 -- Registered IAX2 to '192.83.199.4', who sees us as 

69.28.37.6:13993 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘178.32.160.85’, who sees us as
69.28.37.6:19777 with no messages waiting

 -- Registered IAX2 to '178.32.160.85', who sees us as 

69.28.37.6:19777 with no messages waiting

 -- Registered IAX2 to '216.244.83.154', who sees us as 

69.28.37.6:15479 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘216.244.83.154’, who sees us as
69.28.37.6:15479 with no messages waiting

 -- Registered IAX2 to '216.244.83.154', who sees us as 

69.28.37.6:15479 with no messages waiting

 -- Registered IAX2 to '178.32.160.85', who sees us as 

69.28.37.6:14286 with no messages waiting

Unfortunately no, it can’t be stopped on any version of AllStar. The best you could do is log to a file. But that would also log other messages you want to see on the console.

This is a side effect of Round Robin DNS. There are currently 5 servers in RRDNS. Every time your node queries DNS it will get the next server. The reason is for load balancing, see https://grafana.allstarlink.org, the upper right pie chart shows the registration load.

I’ve build an alternate registration method using http. It’s under very limited Alpha testing. If anyone would like to test it, please send me a PM. The install requires comfort at the Linux command line.

Thank You Tim,
Goes also for editing the Wiki Page

Larry - N7FM

···

On 5/4/20 8:44 AM, Tim Sawyer via AllStarLink Discussion Groups wrote:

[wd6awp] wd6awp https://community.allstarlink.org/u/wd6awp ASL Admin
May 4

Unfortunately no, it can’t be stopped on any version of AllStar. The
best you could do is log to a file. But that would also log other
messages you want to see on the console.

This is a side effect of Round Robin DNS. There are currently 5 servers
in RRDNS. Every time your node queries DNS it will get the next server.
The reason is for load balancing, see https://grafana.allstarlink.org,
the upper right pie chart shows the registration load.

I’ve build an alternate registration method using http. It’s under very
limited Alpha testing. If anyone would like to test it, please send me a
PM. The install requires comfort at the Linux command line.


Visit Topic
https://community.allstarlink.org/t/dns-and-iax2-registration-notices/16907/2
or reply to this email to respond.


    Previous Replies

[larry] larry https://community.allstarlink.org/u/larry
May 3

I am running an older ACID version of Allstar.

Have set verbose level to as small I know how. Is there anyway to stop
the continual CLI display of “Refreshing DNS lookups”
plus the ongoing “-- Registered IAX2” continual notices which swap
many times more than the 3 times in the example below.

The clutter from this is annoying when trying to monitor activity on my
nodes.

Larry N7FM

== Refreshing DNS lookups.
– Registered IAX2 to ‘192.83.199.4’, who sees us as
69.28.37.6:40599 with no messages waiting

– Registered IAX2 to ‘216.244.83.154’, who sees us as |

69.28.37.6:10996 with no messages waiting

– Registered IAX2 to ‘192.83.199.4’, who sees us as |

69.28.37.6:40599 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘44.72.21.13’, who sees us as 69.28.37.6:6765
with no messages waiting

– Registered IAX2 to ‘178.32.160.82’, who sees us as |

69.28.37.6:54779 with no messages waiting

– Registered IAX2 to ‘178.32.160.85’, who sees us as |

69.28.37.6:36206 with no messages waiting

– Registered IAX2 to ‘178.32.160.82’, who sees us as |

69.28.37.6:58483 with no messages waiting

– Registered IAX2 to ‘44.72.21.13’, who sees us as 69.28.37.6:6765 |

with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘192.83.199.4’, who sees us as
69.28.37.6:13993 with no messages waiting

– Registered IAX2 to ‘192.83.199.4’, who sees us as |

69.28.37.6:13993 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘178.32.160.85’, who sees us as
69.28.37.6:19777 with no messages waiting

– Registered IAX2 to ‘178.32.160.85’, who sees us as |

69.28.37.6:19777 with no messages waiting

– Registered IAX2 to ‘216.244.83.154’, who sees us as |

69.28.37.6:15479 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘216.244.83.154’, who sees us as
69.28.37.6:15479 with no messages waiting

– Registered IAX2 to ‘216.244.83.154’, who sees us as |

69.28.37.6:15479 with no messages waiting

– Registered IAX2 to ‘178.32.160.85’, who sees us as |

69.28.37.6:14286 with no messages waiting


Visit Topic
https://community.allstarlink.org/t/dns-and-iax2-registration-notices/16907/2
or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here
https://community.allstarlink.org/email/unsubscribe/609f8e248c6a3e12dc083014a04ce2cf30c354d44b947e0869dcc9435723fa0c.

Question for the Asterisk GURU…

Is there any point where the Asterisk CLI traffic being routed to the
Node Console could be captured and filtered?

I would like to be able to monitor Nodes without Screens and Screens of
garbage. Every every 5 minutes or sooner if Registration fails it swaps
servers and post notice after notice. I have turned of Logging as well
as running Asterisk -r rather than verbose mode.

You could be a BIG TIME HERO with the Allstar Group if you could find
where some script could be installed to filter out all the DNS Refresh
and the Round Robin Registration crap being fed to the Node Console
every 5 minutes or less.

Later
Dad

···

On 5/4/20 8:44 AM, Tim Sawyer via AllStarLink Discussion Groups wrote:

[wd6awp] wd6awp https://community.allstarlink.org/u/wd6awp ASL Admin
May 4

Unfortunately no, it can’t be stopped on any version of AllStar. The
best you could do is log to a file. But that would also log other
messages you want to see on the console.

This is a side effect of Round Robin DNS. There are currently 5 servers
in RRDNS. Every time your node queries DNS it will get the next server.
The reason is for load balancing, see https://grafana.allstarlink.org,
the upper right pie chart shows the registration load.

I’ve build an alternate registration method using http. It’s under very
limited Alpha testing. If anyone would like to test it, please send me a
PM. The install requires comfort at the Linux command line.


Visit Topic
https://community.allstarlink.org/t/dns-and-iax2-registration-notices/16907/2
or reply to this email to respond.


    Previous Replies

[larry] larry https://community.allstarlink.org/u/larry
May 3

I am running an older ACID version of Allstar.

Have set verbose level to as small I know how. Is there anyway to stop
the continual CLI display of “Refreshing DNS lookups”
plus the ongoing “-- Registered IAX2” continual notices which swap
many times more than the 3 times in the example below.

The clutter from this is annoying when trying to monitor activity on my
nodes.

Larry N7FM

== Refreshing DNS lookups.
– Registered IAX2 to ‘192.83.199.4’, who sees us as
69.28.37.6:40599 with no messages waiting

– Registered IAX2 to ‘216.244.83.154’, who sees us as |

69.28.37.6:10996 with no messages waiting

– Registered IAX2 to ‘192.83.199.4’, who sees us as |

69.28.37.6:40599 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘44.72.21.13’, who sees us as 69.28.37.6:6765
with no messages waiting

– Registered IAX2 to ‘178.32.160.82’, who sees us as |

69.28.37.6:54779 with no messages waiting

– Registered IAX2 to ‘178.32.160.85’, who sees us as |

69.28.37.6:36206 with no messages waiting

– Registered IAX2 to ‘178.32.160.82’, who sees us as |

69.28.37.6:58483 with no messages waiting

– Registered IAX2 to ‘44.72.21.13’, who sees us as 69.28.37.6:6765 |

with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘192.83.199.4’, who sees us as
69.28.37.6:13993 with no messages waiting

– Registered IAX2 to ‘192.83.199.4’, who sees us as |

69.28.37.6:13993 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘178.32.160.85’, who sees us as
69.28.37.6:19777 with no messages waiting

– Registered IAX2 to ‘178.32.160.85’, who sees us as |

69.28.37.6:19777 with no messages waiting

– Registered IAX2 to ‘216.244.83.154’, who sees us as |

69.28.37.6:15479 with no messages waiting

== Refreshing DNS lookups.
– Registered IAX2 to ‘216.244.83.154’, who sees us as
69.28.37.6:15479 with no messages waiting

– Registered IAX2 to ‘216.244.83.154’, who sees us as |

69.28.37.6:15479 with no messages waiting

– Registered IAX2 to ‘178.32.160.85’, who sees us as |

69.28.37.6:14286 with no messages waiting


Visit Topic
https://community.allstarlink.org/t/dns-and-iax2-registration-notices/16907/2
or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here
https://community.allstarlink.org/email/unsubscribe/609f8e248c6a3e12dc083014a04ce2cf30c354d44b947e0869dcc9435723fa0c.

Just turn the messages off in the source code and recompile. To mute the “Refreshing DNS lookups” messages, set your asterisk verbosity level < 3, or adjust the source code to test for a higher value—perhaps like: “if (option_verbose > 5)” …This same type “fix” will mute other noisey messages.

73, David KB4FXC

Thats the beauty of open source software…

Just saying :wink:

Le lun. 4 mai 2020 à 14:06, David McGough via AllStarLink Discussion Groups noreply@community.allstarlink.org a écrit :

···


David_McGough

    May 4

Just turn the messages off in the source code and recompile. To mute the “Refreshing DNS lookups” messages, set your asterisk verbosity level < 3, or adjust the source code to test for a higher value—perhaps like: “if (option_verbose > 5)” …This same type “fix” will mute other noisey messages.

github.com

AllStarLink/Asterisk/blob/master/asterisk/main/dnsmgr.c#L235

  1. struct refresh_info *info = (struct refresh_info *)data;
  2. struct ast_dnsmgr_entry *entry;
  3. /* if a refresh or reload is already in progress, exit now */
  4. if (ast_mutex_trylock(&refresh_lock)) {
  5. if (info->verbose)
  6. ast_log(LOG_WARNING, “DNS Manager refresh already in progress.\n”);
  7. return -1;
  8. }
  9. if (option_verbose > 2)
  10. ast_verbose(VERBOSE_PREFIX_2 “Refreshing DNS lookups.\n”);
  11. AST_LIST_LOCK(info->entries);
  12. AST_LIST_TRAVERSE(info->entries, entry, list) {
  13. if (info->regex_present && regexec(&info->filter, entry->name, 0, NULL, 0))
  14. continue;
  15. dnsmgr_refresh(entry, info->verbose);
  16. }
  17. AST_LIST_UNLOCK(info->entries);

73, David KB4FXC


Visit Topic or reply to this email to respond.


In Reply To


larry

    May 4

Question for the Asterisk GURU… Is there any point where the Asterisk CLI traffic being routed to the Node Console could be captured and filtered? I would like to be able to monitor Nodes without Screens and Screens of garbage. Every every 5 minutes or sooner if Registration fails it swaps serv…


Visit Topic or reply to this email to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.

1 Like

Touché! Exactly what open source is for!