Messages

1

23.1 Legacy Series / Re: dpinger Needs Frequent Manual Restarts - Multi-WAN

« on: March 07, 2023, 10:07:19 pm »

Interesting, they have been the same (different monitor source for each gateway, but matched in both settings pages) already.

2

23.1 Legacy Series / Re: dpinger Needs Frequent Manual Restarts - Multi-WAN

« on: March 07, 2023, 05:42:49 am »

This may help you: https://forum.opnsense.org/index.php?topic=18745.msg97953#msg97953

Thanks, I'll take a look.

3

23.1 Legacy Series / Re: dpinger Needs Frequent Manual Restarts - Multi-WAN

« on: March 06, 2023, 09:00:52 pm »

Hmm that looks like a similar situation but I don't need to reboot the whole router, just the dpinger service. If I had the skillset to write a script to restart it on a certain time frequency that would be a workable bandaid for myself. Or even knowing how to add it to the list of cron jobs.

4

23.1 Legacy Series / Re: dpinger Needs Frequent Manual Restarts - Multi-WAN

« on: March 06, 2023, 03:27:17 am »

Any possible ideas why dpinger appears to get stuck "offline"? I just had a 45 min outage on my Tier 1 and had to manually restart it (totally off and red) and it immediately recognized as online. Very frustrating.

5

23.1 Legacy Series / dpinger Needs Frequent Manual Restarts - Multi-WAN

« on: March 02, 2023, 06:59:56 pm »

Hello, running latest OPNsense 23.1.1_2-amd64 on a dedicated mini-PC router with two WAN gateways configured for failover Tier 1 and 2 according to the documentation.

I've been having this issue for several weeks that dpinger needs to be frequently restarted from the dashboard manually or it won't detect that the Tier 1 network is back up. Sometimes dpinger appears green and sometimes it's fully stopped and red. My Tier 1 is starlink which is rather spotty (frequent 1-10s interruptions here in Alaska).

Is there anywhere I can tune dpinger to be more aggressive in rechecking for good gateway?

An easy band aid fix would be a cron job that resets dpinger every 5 min or so but that's not ideal and not an option under the cron menu.

Any help or pointers would be greatly appreciated. Please let me know if I need more info to be able to be helped.

6

22.7 Legacy Series / Gateway Being Set to "Disabled" and stuck after outage - Multi-WAN

« on: January 25, 2023, 02:23:09 am »

Having a weird issue. Running 22.7.11 on a mini-PC router. I have things set up by the Multi-WAN failover instructions to the letter. Have two Gateways, set to Tier 1 and Tier 2. Tier 1 is Starlink and my preferred connection. Here's the issue I'm having:

If Starlink is down for a long period (sometimes 30 min+) its gateway will get set to "disabled" under System/Gateways/single and I have to manually uncheck that box and restart dpinger for that gateway, then everything is perfectly fine. When it's disabled it's completely gone from the dashboard view as well.

Any idea what's up here or what I may have configured wrong? Any more information I need to post for this to actually be helpful?

Thanks so much, I'm new to all this.

7

22.7 Legacy Series / DNS and/or DHCP Settings for Starlink as part of Multi-WAN

« on: January 20, 2023, 08:56:10 pm »

Hello, I've been searching all over and trying to read guides but much of this is over my head.

I just got OPNSense up and running with multi-WAN failover for my home network yesterday. I have two ISPs/gateways coming into a mini-PC: Starlink and my failover old ISP with a hard data cap.

In reading many guides I'm seeing people needing to configure some specific DNS and DHCP settings to keep things happy based on some unique Starlink behavior but I'm not sure if any of it is actually needed or not, especially as part of a Multi-WAN.

I followed the OPNSense multi-WAN setup documentation to the letter and that seems to be functional for me at this point.

For reference, this is one of the guides that mentions some specific settings: https://matthias.guru/en/2021/12/13/starlink-mit-opnsense-pfsense-als-router/

Thanks! I'm brand new to all of this but glad to learn it.