Navigation

    Netgate Discussion Forum
    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search

    WAN not reconnecting after high packet loss

    General pfSense Questions
    1
    1
    346
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      reisender last edited by

      I'm using 2.3.2-RELEASE-p1.  I've recently started having problems with my WAN connection not reconnecting after periods of high packet loss.  I suspect the packet loss is caused by something the ISP is doing because the problem occurs daily at 9:20 pm.  I've also seen it happen at 9:20 am, but not predictably.  My internet connection is provided by my building, so I don't have a direct line of communication to the ISP or their support center.

      I have to reboot pfSense to get the WAN to come back online.  I've tried changing the Monitor IP to different servers, but it hasn't made a difference.  I'm hoping somebody has an idea on a setting within pfSense that will allow it to self-recover from the WAN connection having high latency.

      A sample of the logs are below:

      Dec 22 21:20:51 dpinger WAN_DHCP 208.67.220.220: Alarm latency 0us stddev 0us loss 100%
      Dec 22 21:20:48 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 208.67.220.220 bind_addr x.x.x.x identifier "WAN_DHCP "
      Dec 22 21:20:41 dpinger WAN_DHCP 208.67.220.220: Alarm latency 0us stddev 0us loss 100%
      Dec 22 21:20:38 dpinger send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 208.67.220.220 bind_addr x.x.x.x identifier "WAN_DHCP "
      Dec 22 21:19:05 dpinger WAN_DHCP 208.67.220.220: Alarm latency 35340us stddev 257us loss 22%

      Dec 22 21:20:53 pfsense.localdomain nginx: 2016/12/22 21:20:53 [crit] 30108#100122: *97 SSL_write() failed (SSL:) (13: Permission denied) while sending to client, client: 192.168.20.102, server: , request: "GET /status_services.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.20.1"

      Dec 22 21:20:43 pfsense.localdomain nginx: 2016/12/22 21:20:43 [crit] 30108#100122: *65 SSL_write() failed (SSL:) (13: Permission denied) while sending to client, client: 192.168.20.102, server: , request: "POST /status_services.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm.socket", host: "192.168.20.1", referrer: "https://192.168.20.1/status_services.php"

      1 Reply Last reply Reply Quote 0
      • First post
        Last post

      Products

      • Platform Overview
      • TNSR
      • pfSense
      • Appliances

      Services

      • Training
      • Professional Services

      Support

      • Subscription Plans
      • Contact Support
      • Product Lifecycle
      • Documentation

      News

      • Media Coverage
      • Press
      • Events

      Resources

      • Blog
      • FAQ
      • Find a Partner
      • Resource Library
      • Security Information

      Company

      • About Us
      • Careers
      • Partners
      • Contact Us
      • Legal
      Our Mission

      We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

      Subscribe to our Newsletter

      Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

      © 2021 Rubicon Communications, LLC | Privacy Policy