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

    What can I do to troubleshoot this

    Scheduled Pinned Locked Moved 2.2 Snapshot Feedback and Problems - RETIRED
    2 Posts 2 Posters 1.7k 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.
    • J
      jeepster
      last edited by

      I just lost access to websites, I had to goto DNS resolver and just click 'save' without changing anything in order to visits websites again. I went into the system log and saw the following….. 2.2-RC (amd64) built on Thu Jan 15 16:17:52 CST 2015 FreeBSD 10.1-RELEASE-p4
      My NIC card is a HP NC360T.
      em1 is my lan and that is connected to a TP-Link tl-sg2216 (IP 192.168.1.1)
      em0 is connected to my ISP supplied router,> modem == DMZ on with fixed ip 192.168.2.4 to pfsense
      I'm lost why the log is stating "192.168.4.1."

      Jan 19 12:15:56 kernel: em1: Watchdog timeout -- resetting
      Jan 19 12:15:56 kernel: em1: Queue(0) tdh = 224, hw tdt = 224
      Jan 19 12:15:56 kernel: em1: TX(0) desc avail = 31,Next TX to Clean = 255
      Jan 19 12:15:56 kernel: em1: link state changed to DOWN
      Jan 19 12:15:57 check_reload_status: Linkup starting em1
      Jan 19 12:15:58 php-fpm[77313]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.1.1 )
      Jan 19 12:15:59 check_reload_status: Linkup starting em1
      Jan 19 12:15:59 kernel: em1: link state changed to UP
      Jan 19 12:16:00 php-fpm[77313]: /rc.linkup: Hotplug event detected for LAN(lan) but ignoring since interface is configured with static IP (192.168.1.1 )
      Jan 19 12:16:00 check_reload_status: rc.newwanip starting em1
      Jan 19 12:16:01 php-fpm[77313]: /rc.newwanip: rc.newwanip: Info: starting on em1.
      Jan 19 12:16:01 php-fpm[77313]: /rc.newwanip: rc.newwanip: on (IP address: 192.168.1.1) (interface: LAN[lan]) (real interface: em1).
      Jan 19 12:16:02 php-fpm[77313]: /rc.newwanip: IP has changed, killing states on former IP 192.168.4.1.
      Jan 19 12:16:06 php-fpm[77313]: /rc.newwanip: The command '/usr/local/sbin/unbound -c /var/unbound/unbound.conf' returned exit code '1', the output was '[1421687766] unbound[61747:0] error: bind: address already in use [1421687766] unbound[61747:0] fatal error: could not open ports'
      Jan 19 12:16:08 php-fpm[77313]: /rc.newwanip: Resyncing OpenVPN instances for interface LAN.
      Jan 19 12:16:08 php-fpm[77313]: /rc.newwanip: Creating rrd update script
      Jan 19 12:16:10 php-fpm[77313]: /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 192.168.4.1 -> 192.168.1.1 - Restarting packages.
      Jan 19 12:16:10 check_reload_status: Starting packages
      Jan 19 12:16:11 php-fpm[56742]: /rc.start_packages: Restarting/Starting all packages.

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Something else is bound to port 53, which is making unbound fail to restart under that circumstance.

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