Packet Loss issue
-
Hmm,
So is it a new ISP? (may not be relevant)Why are you using a VLAN on em0 when you only have a single interface on it?
Steve
-
Have my network on a 48 port patch panel and switch. It's easy to work that way as I am planning to add additional WAN in the months ahead. I removed the VLAN on em0 and attached the modem cable directly to pfSense but it didn't make a difference.
-
Is your monitor IP your gateway IP? May have to change that to something else, some ISP routers will not reliably respond to pings even when they're passing traffic just fine.
-
I already tried that. Used google DNS 8.8.8.8. Same apinger issue.
-
So, have you recently changed ISP? Did it coincide with this problem?
Steve
-
Yes, I recently moved. But didn't see this issue for the first 3 months. This has been going on since last 3 weeks.
-
I do not see the apinger issue with this build
2.1-DEVELOPMENT (amd64)
built on Sun Feb 26 13:39:54 CET 2012Unfortunately I cannot use this build as Squid fails to work on it.
-
I do not see the apinger issue with this build
2.1-DEVELOPMENT (amd64)
built on Sun Feb 26 13:39:54 CET 2012Almost certainly a coincidence, nothing at all has changed with apinger.
-
Is that an 8.3 build?
The drivers will be different.
What are NICs are you using?Steve
-
Yes, that's a 8.3 build
Intel dual gigabit. It has worked flawlessly till 2.0. Something changed in 2.0.1?
If it were a driver issue then why don't I see this within the network? It's only on the WAN. Maybe apinger is just monitoring WAN I suppose.
-
Exactly.
It maybe some incompatibility with the upstream equipment. Some change in the ISPs network.
Which Intel chipset is it?Steve
-
I think I found the root cause. I have snort installed (sorry failed to mention that).
Something changed in the snort.org rules that I usually select.
Last night, snort.org site was down and with a clean new install it failed to update the snort.org rule set but the emerging rules were applied. I kept an eye on the system logs and didn't see the apinger issue. I had even rebooted my 48 port L2 managed switch so I thought it might be the cause (though I had rebooted it earlier).
All through out the night and whole day today there was not a single apinger issue reported in the system log. Just now I did a manual snort rules update and snort.org rule sets were added. I selected the usual snort.org rules (I do the same in the emerging rules too). The moment snort restarted with the new rules applied the system log started to fill up with apinger issues again.
Now I have deselected all snort.org rules and will have to select one rule set at a time to pin point exactly which rule set is causing this apinger issue.
-
I would not have guessed that, though it makes sense. Good to know.
Hopefully this will help anyone else with a similar issue.Steve