Opt1 warning sign
-
Hello Gru thanks for reply. I just want to know if it can't affect the load balancer config?
-
Well if your link drops then yes it will affect your loadbalancer ;)
If this is a screenshot just after you've created/modified the pool then this isn't an issue.
The first time the link comes up (or is detected as up) qualifies as a "change of the gateway" and thus is displayed as warning. -
But It didn't happen on wan 1,,only in opt1 interface
-
What did you set as criterium in the loadbalancer to consider the link down?
Well what does your system log say?
If the link of the NIC went down it will say so. If you had high latency it will say so as well. -
I'm pretty sure this warning is because the latency on that interface is so high.
I can't be sure about 1.2.3 but in 2.0 anything over 200ms will cause a warning. You can set the warning threshold higher if that is a normal ping time. Is it a satellite connection?Steve
-
It's not a sattelite connection it's just a dsl connection.,,so that maybe the cause of getting warning sign. I'm using pfsense 1.2.3
-
Why is the ping time so high? If it's adsl I'd expect less than 50ms. Perhaps you have the gateway set to an alternative address?
Steve
-
so do you think the normal delay in a adsl connection is 50ms?. I have 30 users connecting. My wan1 adsl have 4.5 mbps while my wan2 adsl has 3 mbps and I'm getting 100 + delay but 0% packet loss.
-
Well it will depend on the amount of traffic on the connection at the time. If the connection is completely saturated the delay will increase a lot.
<50ms is what I'd expect with no traffic.
Just as a test I am seeing ping times of around 200ms from here (London, UK) to California and around 350ms to Australia.
Your gateway should be set to the first piece of IP addressable (and pingable) equipment at your ISP. A lot closer than the 5000+ miles to California! Hence the warning being set to 200ms.Steve
-
thanks steve ;D
