Strange behavior with gateway
-
@dond and with that big Starlink outage today I can see why.. LOL.
I am trying to figure out what I can do to replicate your setup here..
(starlink outage is what Elon gets for insinuating that a robot could take over as a rollerskate wearing carhop waitress) x. com thing..
-
@chpalmer LOL...
In short, what happens is that if the starlink link is enabled, I don't know why pfsesnne assumes it as the main one even though it is not defined in the gateway group.
-
@dond Im curious if it has to do with monitoring the addresses your first two links are in your first graphic. I know that in the past some have had issues using Googles IP there but cannot remember specifics.
Will your actual gateways answer to a ping? or are they to close in the scope of things to let it work?
-
In a way, yes.
What I expect is that when I define the gateway group, it will assume the tier I defined.
In IP Monitorin, I defined it this way and saw an error in my logs with dpinger.
Jul 24 18:29:19 dpinger 54194 DNET_PPPOE 8.8.8.8: sendto error: 13
Jul 24 18:29:20 dpinger 54194 DNET_PPPOE 8.8.8.8: sendto error: 13
Jul 24 18:29:20 dpinger 54194 DNET_PPPOE 8.8.8.8: sendto error: 13 -
@dond Do you have the "Gateways" widget on your dashboard? Does it show any loss to any of the gateways?
Here since my secondary is just that I simply use the actual modem address to monitor which will never go down unless it loses power just because I expect that my tier1 gateway will take back over when it comes back up and it always does.
Should be true on the highest numerical tier (in your case) 3.. you should not have to ping very far out at all if it is working correctly.
Just trying to rule things out.. and thinking out loud.
-
-
-
@chpalmer said in Strange behavior with gateway:
Set your weight for all of them to one. See if that does not work...
By default it was 1, I changed it in an attempt to fix this, but I'm back now.
I'm waiting for the staff to finalize the billing. I'll leave everything as it was and do a new check. I'll highlight everything and come back here.
-
Good luck. Be monitoring from the sidelines.
-
Hmm, if you set the default to the failover group it should show the tiers in the gateway list like:
Your screenshot above doesn't show that.
When starlink becomes the default do the other two gateways still show on-line as expected? Or is something actually breaking the other two gateways somehow?
-
@stephenw10 https://forum.netgate.com/post/1221361
???
Triggering snowflakes one by one..
Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box. -
@stephenw10 said in Strange behavior with gateway:
When starlink becomes the default do the other two gateways still show on-line as expected? Or is something actually breaking the other two gateways somehow?
Reply
It remains online, then I take down the starlink and then the main one comes back on.
-
What's shown in the logs when it switches the default to Starlink?
-
@chpalmer said in Strange behavior with gateway:
???
When the default gateway is set to a failover group the 'Default' column in the gateways list should show the tiers. But in this screenshot it doesn't: https://forum.netgate.com/post/1221365
That's unexpected.
