Internet Connection Drops. PFSense 2.1
-
Are you saturating your upload when this happens?
-
No, it happens randomly throughout the day/night cycle. Sometimes it happens when my wife is playing WoW, other times when using netflix, still other times I have recorded outages when no one is home (I have smoke ping setup on 2 computers and confirmed with the RRD graphs in pfsense)
-
So in the last day and a bit I have had 2 more instances of complete internet outages as seen by PFSense.
I have gone to System -> Routing -> Edit Gateway and Checked "Disable Gateway Monitoring"
We'll see what happens
-
After a few days with gateway monitoring disabled, I have noticed no appreciable change (still running 2.0.3). I have re-enabled gateway monitoring and set the Frequency Probe to 3 and down to 20 as well as the low water mark for Package Loss to 25%.
I am really hoping someone can point me in the right direction for this. I would hate to dump pfsense for another solution. The interruptions to service is very disheartening, especially considering I have migrated hardware and cables. The box outside of pfsense still has not registered a downed state during the same time periods.
-
Thought I would post an observation. Every time PFSense marks the WAN interface as offline I see the following in the modem's log
Sun Mar 09 11:02:50 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=8c:04:ff:1a:ee:fa;CMTS-MAC=0... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=8c:04:... Sun Mar 09 11:02:49 2014 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC... Sun Mar 09 11:02:40 2014 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=8c:04:ff:1a... Sat Mar 08 23:43:27 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=8c:04:ff:1a:ee:fa;CMTS-MAC=0... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.2;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.1;CM-MAC=8c:04:... Sat Mar 08 23:43:27 2014 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC... Sat Mar 08 23:43:18 2014 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=8c:04:ff:1a... Sat Mar 08 17:45:02 2014 Notice (6) TLV-11 - unrecognized OID;CM-MAC=8c:04:ff:1a:ee:fa;CMTS-MAC=0... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=8c:04:... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=8c:04:... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.7;CM-MAC=8c:04:... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.6;CM-MAC=8c:04:... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.5;CM-MAC=8c:04:... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.4;CM-MAC=8c:04:... Sat Mar 08 17:45:02 2014 Error (4) Missing BP Configuration Setting TLV Type: 17.3;CM-MAC=8c:04:...Is there anything that I can do to reduce the impact of this? Alternatively, is there a way to cycle the interface after it's been down for say 2 minutes?
-
I made the following adjustment yesterday:
Routing -> Edit Gateway
Probe Interval: 3 Down: 60I dont know if it is just a fluke or not, but I did not register any outages last night. I will continue to monitor and update this post as I discover things
-
I have noted the same errors showing up in my modem's log but I did not suffer the corresponding disruption in service.
I will continue to monitor for the next few days and report back, but I am hopeful that this actually worked around the problem
-
I think it might help work around the problem, but the issue with the ISP remains if you are also noticing issues in the modem.
-
I think it might help work around the problem, but the issue with the ISP remains if you are also noticing issues in the modem.
This is true enough. My goal was to mitigate the problem. The ISP has already acknowledged a problem with a cable in the ground, which cannot be fixed until ground thaws enough for them to dig
I have had another day without service interruption (aside from dropped packets). This may be a viable work around for others I hope. A couple more days and I will mark this as solved
-
I made the following adjustment yesterday:
Routing -> Edit Gateway
Probe Interval: 3 Down: 60I dont know if it is just a fluke or not, but I did not register any outages last night. I will continue to monitor and update this post as I discover things
This worked for me. Made an account just to thank you for it. Had been troubleshooting it for 2 days.