Pfsense 2.1.5 going into the negatives?
-
it says 30ms
-
Is it showing any packet loss?
-
i dislike not knowing how to do something, can you please tell me how to check packet loss?
-
Check your quality on your RRD graphs for the wan interface and look for red and anything that reminds you the himalayas and high numbers…. not that 30 is low....
BTW - I MISS THE OLD RRD GRAPHS!
-
here is a screen shot, sorry, im half asleep, i work nights, but today is my day off
 -
Need to click on the quality tab…. (I'm on the newest version now which is different than yours. Look for "quality"
-
yes, i am getting packet loss
 -
OK - Thats causing your problems.
I suggest you go in and change your latency thresholds in apinger.
Problem is when the latency is very high pfsense can think the wan is offline.
(Probably wouldn't have problem with current pfsense version.
Possibly also actually a internet problem before it gets to pfsense, but apinger doesn't like high latency.
-
thank you for the help, i have changed it and will post back here if it still acts up, which i should know shortly as i am currently downloading a few movies from amazon and that is when i noticed it acting up like that, been a while since i downloaded a large set of files
-
hmmm, it seems to have been only a temp fix, but it is taking a lot longer for the weird spike to happen
-
Your also going to want to make sure you don't kill the states when it thinks wan is offline.. Even upping the value for apinger, your getting huge latency there of 180 some ms when your seeing that much traffic, and yeah out of the box pfsense will reset the states on loss of wan.
-
that seems to have fixed it, i want to thank you for taking the time to help me with this issue, and if there is anymore weird issues that i can not solve, i will post in the forums
thank you again
:D -
NP - glad you got it sorted. I would suggest you move to current 2.3 vesion. 2.1 is not really a supported version.
You might want to look into maybe doing something with what I would guess is bufferbloat since looks like when your downloading something your pings are going through the roof.. A somewhat simple help for that is just turning on codel
