[REQ] - Support multiple monitoring IPs

[maxwbot]

Feature Request

Currently connmon allows monitoring only a single IP/host to determine internet connectivity.

This can lead to false positives when the monitored IP becomes temporarily unreachable (e.g., remote server issue, routing issue, ICMP blocked), even though the internet connection is still working.

Proposed Enhancement

Add support for multiple monitoring IPs (e.g., 2 or 3), with configurable behavior such as:

1. Failover mode

   • If primary IP fails, test secondary IP(s) before declaring connection down.

2. Quorum mode

   • Consider connection DOWN only if all configured IPs fail.
   • Consider connection UP if at least one IP responds.

3. Optional:

   • Configurable threshold (e.g., "minimum X successful responses out of Y IPs").
   • Separate timeout per host.
   • Round-robin testing instead of sequential.

Example Use Case

For example:

MONITOR_IPS="1.1.1.1 8.8.8.8 9.9.9.9"

If 1.1.1.1 fails but 8.8.8.8 responds, connection should still be considered UP.

This would significantly reduce false internet-down triggers caused by single endpoint failures.

Why This Matters

Many users rely on connmon for:

• WAN failover
• Auto-reconnect logic
• Monitoring stability

Single-endpoint monitoring is inherently fragile. Multi-endpoint support would make connmon more robust and production-ready.

[ExtremeFiretop]

@Martinski4GitHub

For your review :)

[Martinski4GitHub]

@Martinski4GitHub

For your review :)>

I'll take a look when I get some free time this weekend.

BTW, do you happen to know why I never get any email notifications when people submit "issues" for any of the AMTM-OSR repos? It's very strange since I do get notifications of any and all PRs that are submitted, but none at all for the "issues" reported.
Just wondering if you happen to have any ideas.

Thanks.

[ExtremeFiretop]

@Martinski4GitHub
For your review :)>

I'll take a look when I get some free time this weekend.

BTW, do you happen to know why I never get any email notifications when people submit "issues" for any of the AMTM-OSR repos? It's very strange since I do get notifications of any and all PRs that are submitted, but none at all for the "issues" reported. Just wondering if you happen to have any ideas.

Thanks.

I'll have to take a deeper look today, maybe run a few tests with some dummy issue reports to see if I can get it to properly assign to us.

Some people know to tag us or assign to us, others do not. So there should be a way to automate the assignment process you would think.

I'll review today and advise buddy, I'm on the case!

[maxwbot]

@Martinski4GitHub
For your review :)>

I'll take a look when I get some free time this weekend.

BTW, do you happen to know why I never get any email notifications when people submit "issues" for any of the AMTM-OSR repos? It's very strange since I do get notifications of any and all PRs that are submitted, but none at all for the "issues" reported. Just wondering if you happen to have any ideas.

Thanks.

Hello! Based on what you described, the most likely cause is that Issue notifications are disabled or configured differently from Pull Request notifications in your GitHub account.

Since PR emails are arriving normally, this indicates that the notification system itself is working, but the Issues category may be unchecked in your preferences.

Please check your account notification settings, as well as the “Watch” settings for the AMTM-OSR repositories, to make sure Issue notifications are enabled. If you'd like, you can also use ChatGPT (IA).

[ExtremeFiretop]

@Martinski4GitHub
For your review :)>

I'll take a look when I get some free time this weekend.
BTW, do you happen to know why I never get any email notifications when people submit "issues" for any of the AMTM-OSR repos? It's very strange since I do get notifications of any and all PRs that are submitted, but none at all for the "issues" reported. Just wondering if you happen to have any ideas.
Thanks.

Hello! Based on what you described, the most likely cause is that Issue notifications are disabled or configured differently from Pull Request notifications in your GitHub account.

Since PR emails are arriving normally, this indicates that the notification system itself is working, but the Issues category may be unchecked in your preferences.

Please check your account notification settings, as well as the “Watch” settings for the AMTM-OSR repositories, to make sure Issue notifications are enabled. If you'd like, you can also use ChatGPT (IA).

Hello @maxwbot

I can confirm this is not the problem. We simply need to find a way for the issue reports to be correctly assigned to us by an automated method, likely using the issue templates or a workflow, instead of relying on people doing it manually.

This is one of those instances where AI may be a little lost in the woods with its suggestions it's giving you. Its probably for the best we have someone human troubleshooting this one 😂

@Martinski4GitHub I'll let you know what I find.

[Martinski4GitHub]

@Martinski4GitHub
For your review :)>

I'll take a look when I get some free time this weekend.
BTW, do you happen to know why I never get any email notifications when people submit "issues" for any of the AMTM-OSR repos? It's very strange since I do get notifications of any and all PRs that are submitted, but none at all for the "issues" reported. Just wondering if you happen to have any ideas.
Thanks.

Hello! Based on what you described, the most likely cause is that Issue notifications are disabled or configured differently from Pull Request notifications in your GitHub account.
Since PR emails are arriving normally, this indicates that the notification system itself is working, but the Issues category may be unchecked in your preferences.
Please check your account notification settings, as well as the “Watch” settings for the AMTM-OSR repositories, to make sure Issue notifications are enabled. If you'd like, you can also use ChatGPT (IA).

Hello @maxwbot

I can confirm this is not the problem. We simply need to find a way for the issue reports to be correctly assigned to us by an automated method, likely using the issue templates or a workflow, instead of relying on people doing it manually.

This is one of those instances where AI may be a little lost in the woods with its suggestions it's giving you. Its probably for the best we have someone human troubleshooting this one 😂

@Martinski4GitHub I'll let you know what I find.

Thanks a lot for troubleshooting and looking into this. It's not a time-critical situation, so there's no rush - take your time, bud.

[ExtremeFiretop]

Hello @maxwbot
I can confirm this is not the problem. We simply need to find a way for the issue reports to be correctly assigned to us by an automated method, likely using the issue templates or a workflow, instead of relying on people doing it manually.
This is one of those instances where AI may be a little lost in the woods with its suggestions it's giving you. Its probably for the best we have someone human troubleshooting this one 😂
@Martinski4GitHub I'll let you know what I find.

Thanks a lot for troubleshooting and looking into this. It's not a time-critical situation, so there's no rush - take your time, bud.

Hey @Martinski4GitHub

As I expected there are 2 ways to get the assignments to be automated.

1. You can setup a workflow to dynamically assign to the team members.
2. You can update the bug-report template file or the feature-request template file.

Because our team is currently small I opted to just update all the template files across all repos to automatically assign to us a few minutes ago:

You can test it on any repo of the org, by draft/starting a new issue you will see us all automatically assigned:

If the team grows to a larger size one day, or if we need to be more strict and FORCE users to not unselect us from the template, then we can investigate a workflow implementation.

[Martinski4GitHub]

Hello @maxwbot
I can confirm this is not the problem. We simply need to find a way for the issue reports to be correctly assigned to us by an automated method, likely using the issue templates or a workflow, instead of relying on people doing it manually.
This is one of those instances where AI may be a little lost in the woods with its suggestions it's giving you. Its probably for the best we have someone human troubleshooting this one 😂
@Martinski4GitHub I'll let you know what I find.

Thanks a lot for troubleshooting and looking into this. It's not a time-critical situation, so there's no rush - take your time, bud.

Hey @Martinski4GitHub

As I expected there are 2 ways to get the assignments to be automated.

1. You can setup a workflow to dynamically assign to the team members.

2. You can update the bug-report template file or the feature-request template file.

Because our team is currently small I opted to just update all the template files across all repos to automatically assign to us a few minutes ago:

You can test it on any repo of the org, by draft/starting a new issue you will see us all automatically assigned:

If the team grows to a larger size one day, or if we need to be more strict and FORCE users to not unselect us from the template, then we can investigate a workflow implementation.

Thanks a lot, buddy!! I appreciate your taking the time to resolve the situation.

P.S.
Apologies for the radio silence. During last Monday's Engineering meeting, I was assigned an action item with a deliverable due this coming Friday, so I've been busy working on that. I'm about 80% done, so I won't have much free time to take a look at anything related to GitHub or AMTM-OSR repos. I got to take my time in the evenings to relax and chill with "my better half" after a long day. 😉

Take care, bud, and thanks again.