4G gateway monitoring options
-
@Gertjan said in 4G gateway monitoring options:
no monitoring == no automated fail over.
At least the other way around is true: failover requires gateway monitoring.
And I cannot think of any other use of it.
It's not required to access the interface address at all. -
-
@viragomann
Yep, that 500 milli seconds is half a second, the one I used in my "how many bytes used", see above -
@Gertjan Sorry I understand this I'm just a little confused as it requires a whole bunch of other values to be changed too and its frying my brain..
I was never good at maths at school.
-
@Gertjan
Well briefed!
A half GB a month? Not as less as I was thinking.
Never worried about this. But it's a considerable amount of data if you have a limited connection for sure. -
- "Time Period" > 2 x "Probe Interval" + "Loss Interval"
- "Alert interval" >= "Probe Interval"
This means in words, when you enhance the "Probe Interval", you have also to enhance "Time Period" and "Alert interval" according to this.
Without knowing your new value for "Probe Interval", we cannot calculate the other values for you.
-
@Gertjan Ok you raise a good point here, sorry I missed that part of that post.
I did think of this, but I have no idea why else my data would be being chewed up.
I've done some testing and im pretty sure my traffic is flowing via my primary, and only switching over when I take the primary down.
Confirmed with traceroutes. From the setup images I posted above, does everything look alright? I have honestly never configured failover before.
-
@deanfourie
Check out Diagnostics > States > States and select the 4G interface. So you can see all existing states on it.
If the primary gateway is up there should be nothing more than the icmp from dpinger. -
I use:
Comes in at ~150MB a month. Which is less than the 200MB limit on the free plan Three used to offer. Sadly no longer.
-
You could run a packet capture for a while on your 4G interface and check what goes out and when.
Exclude ICMP traffic.
