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

    Connection dropping between pfSense and cable modem

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 1.2k Views
    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.
    • B Offline
      bhenson1
      last edited by

      We are having an issue where every few minutes the connection between our pfSense firewall and our cable modem is dropping for about 1-2 minutes.

      The connection drop does not affect the LAN at all, and I'm able to ping the modem from outside, it appears to be the connection between these two devices that is going down.

      What are some steps I can take to troubleshoot? Is there anymore information I can provide that would help?

      Thanks,

      -Brian

      1 Reply Last reply Reply Quote 0
      • stephenw10S Offline
        stephenw10 Netgate Administrator
        last edited by

        @bhenson1:

        I'm able to ping the modem from outside

        Does that mean that your modem has your public IP? And your pfSense WAN is on a private subnet?

        Look in the system logs to see what triggered the disconnect.

        Steve

        1 Reply Last reply Reply Quote 0
        • B Offline
          bhenson1
          last edited by

          OK, further investigation has told me a few things:

          Both the WAN and the modem each have a separate static IP.

          The WAN has been going down but the modem can still be pinged from the outside. Also a computer hooked up directly to the modem can connect to the internet when the WAN goes down.

          Here's the system log for the most recent drop:

          Nov 24 09:07:05 check_reload_status: Linkup starting re1
          Nov 24 09:07:06 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:06 check_reload_status: rc.newwanip starting re1
          Nov 24 09:07:08 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:09 kernel: re1: link state changed to DOWN
          Nov 24 09:07:09 check_reload_status: Linkup starting re1
          Nov 24 09:07:11 kernel: re1: link state changed to UP
          Nov 24 09:07:12 php: : rc.newwanip: Informational is starting re1.
          Nov 24 09:07:12 php: : rc.newwanip: on (IP address: 75.150.44.1) (interface: wan) (real interface: re1).
          Nov 24 09:07:12 php: : ROUTING: setting default route to 75.150.44.2
          Nov 24 09:07:12 apinger: Exiting on signal 15.
          Nov 24 09:07:13 check_reload_status: Reloading filter
          Nov 24 09:07:13 apinger: Starting Alarm Pinger, apinger(35607)
          Nov 24 09:07:14 kernel: re1: link state changed to DOWN
          Nov 24 09:07:14 check_reload_status: Linkup starting re1
          Nov 24 09:07:14 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:15 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:15 check_reload_status: rc.newwanip starting re1
          Nov 24 09:07:19 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:21 php: : rc.newwanip: Informational is starting re1.
          Nov 24 09:07:21 php: : rc.newwanip: on (IP address: 75.150.44.1) (interface: wan) (real interface: re1).
          Nov 24 09:07:21 php: : ROUTING: setting default route to 75.150.44.2
          Nov 24 09:07:21 apinger: Exiting on signal 15.
          Nov 24 09:07:22 check_reload_status: Reloading filter
          Nov 24 09:07:22 apinger: Starting Alarm Pinger, apinger(46675)
          Nov 24 09:07:25 kernel: re1: link state changed to UP
          Nov 24 09:07:25 check_reload_status: Linkup starting re1
          Nov 24 09:07:30 kernel: re1: link state changed to DOWN
          Nov 24 09:07:30 check_reload_status: Linkup starting re1
          Nov 24 09:07:30 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:30 check_reload_status: rc.newwanip starting re1
          Nov 24 09:07:32 kernel: re1: link state changed to UP
          Nov 24 09:07:32 check_reload_status: Linkup starting re1
          Nov 24 09:07:35 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:36 php: : rc.newwanip: Informational is starting re1.
          Nov 24 09:07:36 php: : rc.newwanip: on (IP address: 75.150.44.1) (interface: wan) (real interface: re1).
          Nov 24 09:07:36 php: : ROUTING: setting default route to 75.150.44.2
          Nov 24 09:07:36 apinger: Exiting on signal 15.
          Nov 24 09:07:37 check_reload_status: Reloading filter
          Nov 24 09:07:37 apinger: Starting Alarm Pinger, apinger(20810)
          Nov 24 09:07:37 php: : Hotplug event detected for wan but ignoring since interface is configured with static IP (75.150.44.1)
          Nov 24 09:07:37 check_reload_status: rc.newwanip starting re1
          Nov 24 09:07:43 php: : rc.newwanip: Informational is starting re1.
          Nov 24 09:07:43 php: : rc.newwanip: on (IP address: 75.150.44.1) (interface: wan) (real interface: re1).
          Nov 24 09:07:43 php: : ROUTING: setting default route to 75.150.44.2
          Nov 24 09:07:43 apinger: Exiting on signal 15.
          Nov 24 09:07:44 check_reload_status: Reloading filter
          Nov 24 09:07:45 apinger: Starting Alarm Pinger, apinger(29719)

          1 Reply Last reply Reply Quote 0
          • B Offline
            bhenson1
            last edited by

            I found the issue. It turned out to be a bad switch. There was an unmanaged ethernet switch between the modem and the WAN, I replaced the switch and haven't had a drop since.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.