Pfsense on watchguard x500 stops then starts working again



  • I have pfsense on a watchguard x500 box and everything has been working great for about 6 months (if not more). Just recently it has been giving me problems though. I will be plugging away on the net and then it will come to a halt. Then it may start working again after 1 minute or so. I have the firewall connected to a switch connected to the computers in my house. When this happens I can ping through that switch just fine but if I try to ping the x500 I get no response. I started pinging it continuously and you can see when my internet dies due to very slow ping response times:

    64 bytes from 10.0.0.254: icmp_seq=258 ttl=64 time=0.176 ms
    64 bytes from 10.0.0.254: icmp_seq=259 ttl=64 time=0.201 ms
    64 bytes from 10.0.0.254: icmp_seq=260 ttl=64 time=0.196 ms
    64 bytes from 10.0.0.254: icmp_seq=261 ttl=64 time=0.198 ms
    64 bytes from 10.0.0.254: icmp_seq=262 ttl=64 time=0.197 ms
    64 bytes from 10.0.0.254: icmp_seq=263 ttl=64 time=0.196 ms
    64 bytes from 10.0.0.254: icmp_seq=271 ttl=64 time=3.87 ms
    64 bytes from 10.0.0.254: icmp_seq=272 ttl=64 time=3.51 ms
    64 bytes from 10.0.0.254: icmp_seq=290 ttl=64 time=3.60 ms
    64 bytes from 10.0.0.254: icmp_seq=294 ttl=64 time=3.52 ms
    64 bytes from 10.0.0.254: icmp_seq=296 ttl=64 time=4.02 ms
    64 bytes from 10.0.0.254: icmp_seq=307 ttl=64 time=3.71 ms
    64 bytes from 10.0.0.254: icmp_seq=318 ttl=64 time=4.01 ms
    64 bytes from 10.0.0.254: icmp_seq=320 ttl=64 time=3.54 ms
    64 bytes from 10.0.0.254: icmp_seq=324 ttl=64 time=874 ms
    64 bytes from 10.0.0.254: icmp_seq=325 ttl=64 time=0.195 ms
    64 bytes from 10.0.0.254: icmp_seq=326 ttl=64 time=0.221 ms
    64 bytes from 10.0.0.254: icmp_seq=327 ttl=64 time=0.202 ms
    64 bytes from 10.0.0.254: icmp_seq=328 ttl=64 time=0.226 ms
    64 bytes from 10.0.0.254: icmp_seq=329 ttl=64 time=0.285 ms
    64 bytes from 10.0.0.254: icmp_seq=330 ttl=64 time=0.201 ms
    64 bytes from 10.0.0.254: icmp_seq=331 ttl=64 time=0.198 ms
    64 bytes from 10.0.0.254: icmp_seq=332 ttl=64 time=0.212 ms
    64 bytes from 10.0.0.254: icmp_seq=333 ttl=64 time=0.264 ms
    64 bytes from 10.0.0.254: icmp_seq=334 ttl=64 time=0.311 ms
    64 bytes from 10.0.0.254: icmp_seq=335 ttl=64 time=0.218 ms
    64 bytes from 10.0.0.254: icmp_seq=336 ttl=64 time=1.01 ms
    64 bytes from 10.0.0.254: icmp_seq=337 ttl=64 time=0.330 ms
    64 bytes from 10.0.0.254: icmp_seq=338 ttl=64 time=0.324 ms
    64 bytes from 10.0.0.254: icmp_seq=339 ttl=64 time=0.348 ms
    64 bytes from 10.0.0.254: icmp_seq=340 ttl=64 time=119 ms
    64 bytes from 10.0.0.254: icmp_seq=341 ttl=64 time=0.326 ms
    64 bytes from 10.0.0.254: icmp_seq=342 ttl=64 time=0.294 ms
    64 bytes from 10.0.0.254: icmp_seq=343 ttl=64 time=0.196 ms
    64 bytes from 10.0.0.254: icmp_seq=344 ttl=64 time=0.317 ms
    
    

    I have shut it down for 5-10 minutes and powered it back up, I have also tried restarting it and it will work for a little bit but do the exact same thing every time. Is there some that I could possibly look for to troubleshoot what is actually malfunctioning? Like continuous pings withing the x500. One to the internet, and one to a home networked PC? Maybe that would tell me if it is a particular port or something entirely different. Please help me out here, thanks!


  • Netgate Administrator

    What are you pinging from where in that log? You say:
    @n0hc:

    if I try to ping the x500 I get no response.

    So if that is the X500 you're pinging it gets slow (very slow) but does respond. How much packet loss are you seeing?
    This is the sort of thing that can happen when your WAN goes down and pfSense tries to reconnect. What;s in the system logs for the same time period?

    Steve


Log in to reply