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

    Issues with WAN Gateway

    Scheduled Pinned Locked Moved General pfSense Questions
    22 Posts 4 Posters 8.6k 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.
    • jimpJ
      jimp Rebel Alliance Developer Netgate
      last edited by

      When dhclient stopped, what was in the system log around it?

      If you don't have WAN connectivity some parts of the GUI will be slow because it can't reach DNS servers.

      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

      Need help fast? Netgate Global Support!

      Do not Chat/PM for help!

      1 Reply Last reply Reply Quote 0
      • S
        sinicide
        last edited by

        This is what I grab around that time from the system logs around that time.

        Jan 31 00:40:55 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 00:41:05 pfsense check_reload_status: Reloading filter
Jan 31 00:41:27 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 00:41:37 pfsense check_reload_status: Reloading filter
Jan 31 00:43:00 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 00:43:10 pfsense check_reload_status: Reloading filter
Jan 31 00:43:36 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 00:43:46 pfsense check_reload_status: Reloading filter
Jan 31 00:44:51 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 00:45:00 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 00:45:01 pfsense check_reload_status: Reloading filter
Jan 31 00:51:31 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 00:51:41 pfsense check_reload_status: Reloading filter
Jan 31 00:52:07 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 00:52:17 pfsense check_reload_status: Reloading filter
Jan 31 00:52:29 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 00:52:39 pfsense check_reload_status: Reloading filter
Jan 31 00:53:33 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 00:53:43 pfsense check_reload_status: Reloading filter
Jan 31 00:54:32 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 00:54:42 pfsense check_reload_status: Reloading filter
Jan 31 00:55:49 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 00:55:59 pfsense check_reload_status: Reloading filter
Jan 31 01:01:01 pfsense php: : DynDns: updatedns() starting
Jan 31 01:01:01 pfsense php: : DynDns debug information: 74.67.172.72 extracted from local system.
Jan 31 01:01:01 pfsense php: : DynDns: Current WAN IP: 74.67.172.72 Cached IP: 74.67.172.72
Jan 31 01:01:01 pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 31 01:01:01 pfsense php: : DynDns: updatedns() starting
Jan 31 01:01:01 pfsense php: : DynDns debug information: 74.67.172.72 extracted from local system.
Jan 31 01:01:01 pfsense php: : DynDns: Current WAN IP: 74.67.172.72 Cached IP: 74.67.172.72
Jan 31 01:01:01 pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 31 01:01:02 pfsense php: : DynDns: updatedns() starting
Jan 31 01:01:02 pfsense php: : DynDns debug information: 74.67.172.72 extracted from local system.
Jan 31 01:01:02 pfsense php: : DynDns: Current WAN IP: 74.67.172.72 Cached IP: 74.67.172.72
Jan 31 01:01:02 pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 31 01:01:02 pfsense php: : DynDns: updatedns() starting
Jan 31 01:01:02 pfsense php: : DynDns debug information: 74.67.172.72 extracted from local system.
Jan 31 01:01:02 pfsense php: : DynDns: Current WAN IP: 74.67.172.72 Cached IP: 74.67.172.72
Jan 31 01:01:02 pfsense php: : phpDynDNS: No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
Jan 31 01:05:31 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:05:41 pfsense check_reload_status: Reloading filter
Jan 31 01:06:03 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:06:13 pfsense check_reload_status: Reloading filter
Jan 31 01:06:24 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:06:34 pfsense check_reload_status: Reloading filter
Jan 31 01:07:28 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:07:38 pfsense check_reload_status: Reloading filter
Jan 31 01:07:51 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:08:01 pfsense check_reload_status: Reloading filter
Jan 31 01:08:14 pfsense apinger: ALARM: WAN(8.8.8.8)  *** down ***
Jan 31 01:08:24 pfsense check_reload_status: Reloading filter
Jan 31 01:23:08 pfsense sshd[19381]: error: PAM: authentication error for root from 192.168.70.201
Jan 31 01:23:08 pfsense sshd[19381]: error: PAM: authentication error for root from 192.168.70.201
Jan 31 01:23:11 pfsense sshd[19381]: Accepted keyboard-interactive/pam for root from 192.168.70.201 port 55504 ssh2
Jan 31 01:27:19 pfsense dhclient: PREINIT
Jan 31 01:27:19 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:19 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:19 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:19 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:19 pfsense dhclient[39038]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
Jan 31 01:27:20 pfsense dhclient[39038]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:20 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.1
Jan 31 01:27:21 pfsense dhclient[39038]: DHCPACK from 10.243.128.1
Jan 31 01:27:21 pfsense dhclient: REBOOT
Jan 31 01:27:21 pfsense dhclient: Starting add_new_address()
Jan 31 01:27:21 pfsense dhclient: ifconfig rl0 inet 74.67.172.72 netmask 255.255.254.0 broadcast 255.255.255.255
Jan 31 01:27:21 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:21 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:21 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:21 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotification: sendto(s_udp=14): No route to host
Jan 31 01:27:21 pfsense dhclient: New IP Address (rl0): 74.67.172.72
Jan 31 01:27:21 pfsense dhclient: New Subnet Mask (rl0): 255.255.254.0
Jan 31 01:27:21 pfsense dhclient: New Broadcast Address (rl0): 255.255.255.255
Jan 31 01:27:21 pfsense dhclient: New Routers (rl0): 74.67.172.1
Jan 31 01:27:21 pfsense dhclient: Adding new routes to interface: rl0
Jan 31 01:27:21 pfsense dhclient: /sbin/route add default 74.67.172.1
Jan 31 01:27:21 pfsense dhclient: Creating resolv.conf
Jan 31 01:27:21 pfsense check_reload_status: rc.newwanip starting rl0
Jan 31 01:27:21 pfsense dhclient[39038]: bound to 74.67.172.72 -- renewal in 13527 seconds.
Jan 31 01:27:22 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** down ***
Jan 31 01:27:23 pfsense php: : rc.newwanip: Informational is starting rl0.
Jan 31 01:27:23 pfsense php: : rc.newwanip: on (IP address: 74.67.172.72) (interface: wan) (real interface: rl0).
Jan 31 01:27:23 pfsense php: : ROUTING: setting default route to 74.67.172.1
Jan 31 01:27:23 pfsense php: : Removing static route for monitor 8.8.8.8 and adding a new route through 74.67.172.1
Jan 31 01:27:23 pfsense apinger: Exiting on signal 15.
Jan 31 01:27:23 pfsense check_reload_status: Reloading filter
Jan 31 01:27:24 pfsense dnsmasq[48840]: reading /etc/resolv.conf
Jan 31 01:27:24 pfsense dnsmasq[48840]: using nameserver 8.8.4.4#53
Jan 31 01:27:24 pfsense dnsmasq[48840]: using nameserver 8.8.8.8#53
Jan 31 01:27:24 pfsense dnsmasq[48840]: ignoring nameserver 127.0.0.1 - local interface
Jan 31 01:27:24 pfsense dnsmasq[48840]: ignoring nameserver 127.0.0.1 - local interface
Jan 31 01:27:24 pfsense apinger: Starting Alarm Pinger, apinger(49039)
Jan 31 01:27:57 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:28:07 pfsense check_reload_status: Reloading filter
Jan 31 01:28:24 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:28:34 pfsense check_reload_status: Reloading filter
Jan 31 01:28:47 pfsense apinger: ALARM: WAN(8.8.8.8)  *** down ***
Jan 31 01:28:57 pfsense check_reload_status: Reloading filter
Jan 31 01:30:51 pfsense check_reload_status: Syncing firewall
Jan 31 01:32:27 pfsense php: /index.php: XMLRPC communication error: php_network_getaddresses: getaddrinfo failed: hostname nor servname provide
d, or not known
        1 Reply Last reply Reply Quote 0
        • jimpJ
          jimp Rebel Alliance Developer Netgate
          last edited by

          Are you sure that's everything? I don't see any messages logged from dhclient about it stopping/exiting, just starting.

          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

          Need help fast? Netgate Global Support!

          Do not Chat/PM for help!

          1 Reply Last reply Reply Quote 0
          • S
            sinicide
            last edited by

            Here is more. By the end of it, I either manually rebooted or my reboot script kicked in.

            Jan 31 01:32:44 pfsense dhclient[39268]: connection closed
Jan 31 01:32:44 pfsense dhclient[39268]: connection closed
Jan 31 01:32:44 pfsense dhclient[39268]: exiting.
Jan 31 01:32:44 pfsense dhclient[39268]: exiting.
Jan 31 01:32:45 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:45 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:46 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:46 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:46 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:46 pfsense dhclient: PREINIT
Jan 31 01:32:46 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 01:32:46 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 01:32:46 pfsense dhclient[54206]: DHCPREQUEST on rl0 to 255.255.255.255 p
ort 67
Jan 31 01:32:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 01:32:47 pfsense dhclient[54206]: DHCPACK from 10.243.128.1
Jan 31 01:32:47 pfsense dhclient: REBOOT
Jan 31 01:32:47 pfsense dhclient: Starting add_new_address()
Jan 31 01:32:47 pfsense dhclient: ifconfig rl0 inet 74.67.172.72 netmask 255.255
.254.0 broadcast 255.255.255.255
Jan 31 01:32:47 pfsense miniupnpd[1378]: ioctl(s, SIOCGIFADDR, ...): Can't assig
n requested address
Jan 31 01:32:47 pfsense miniupnpd[1378]: ioctl(s, SIOCGIFADDR, ...): Can't assig
n requested address
Jan 31 01:32:47 pfsense miniupnpd[1378]: Failed to get IP for interface rl0
Jan 31 01:32:47 pfsense miniupnpd[1378]: Failed to get IP for interface rl0
Jan 31 01:32:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: cannot get public IP address, stopping
Jan 31 01:32:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: cannot get public IP address, stopping
Jan 31 01:32:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 01:32:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 01:32:47 pfsense dhclient: New IP Address (rl0): 74.67.172.72
Jan 31 01:32:47 pfsense dhclient: New Subnet Mask (rl0): 255.255.254.0
Jan 31 01:32:47 pfsense dhclient: New Broadcast Address (rl0): 255.255.255.255
Jan 31 01:32:47 pfsense dhclient: New Routers (rl0): 74.67.172.1
Jan 31 01:32:47 pfsense dhclient: Adding new routes to interface: rl0
Jan 31 01:32:47 pfsense dhclient: /sbin/route add default 74.67.172.1
Jan 31 01:32:47 pfsense dhclient: Creating resolv.conf
Jan 31 01:32:47 pfsense check_reload_status: rc.newwanip starting rl0
Jan 31 01:32:48 pfsense dhclient[54206]: bound to 74.67.172.72 -- renewal in 133
64 seconds.
Jan 31 01:32:49 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** down ***
Jan 31 01:32:50 pfsense php: : rc.newwanip: Informational is starting rl0.
Jan 31 01:32:50 pfsense php: : rc.newwanip: on (IP address: 74.67.172.72) (inter
face: wan) (real interface: rl0).
Jan 31 01:32:50 pfsense php: : ROUTING: setting default route to 74.67.172.1
Jan 31 01:32:50 pfsense php: : Removing static route for monitor 8.8.8.8 and add
ing a new route through 74.67.172.1
Jan 31 01:32:50 pfsense apinger: Exiting on signal 15.
Jan 31 01:32:50 pfsense check_reload_status: Reloading filter
Jan 31 01:32:50 pfsense dnsmasq[48840]: reading /etc/resolv.conf
Jan 31 01:32:50 pfsense dnsmasq[48840]: using nameserver 8.8.4.4#53
Jan 31 01:32:50 pfsense dnsmasq[48840]: using nameserver 8.8.8.8#53
Jan 31 01:32:50 pfsense dnsmasq[48840]: ignoring nameserver 127.0.0.1 - local in
terface
Jan 31 01:32:50 pfsense dnsmasq[48840]: ignoring nameserver 127.0.0.1 - local in
terface
Jan 31 01:32:51 pfsense apinger: Starting Alarm Pinger, apinger(2003)
Jan 31 01:33:36 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:33:46 pfsense check_reload_status: Reloading filter
Jan 31 01:33:51 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:34:01 pfsense check_reload_status: Reloading filter
Jan 31 01:43:46 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:43:56 pfsense check_reload_status: Reloading filter
Jan 31 01:43:59 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:44:09 pfsense check_reload_status: Reloading filter
Jan 31 01:47:16 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:47:26 pfsense check_reload_status: Reloading filter
Jan 31 01:47:36 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:47:46 pfsense check_reload_status: Reloading filter
Jan 31 01:51:08 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:51:18 pfsense check_reload_status: Reloading filter
Jan 31 01:52:12 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:52:22 pfsense check_reload_status: Reloading filter
Jan 31 01:52:34 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:52:44 pfsense check_reload_status: Reloading filter
Jan 31 01:53:01 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:53:11 pfsense check_reload_status: Reloading filter
Jan 31 01:53:33 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:53:42 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:53:43 pfsense check_reload_status: Reloading filter
Jan 31 01:54:17 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:54:27 pfsense check_reload_status: Reloading filter
Jan 31 01:54:29 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:54:39 pfsense check_reload_status: Reloading filter
Jan 31 01:54:53 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 01:55:03 pfsense check_reload_status: Reloading filter
Jan 31 01:55:06 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 01:55:16 pfsense check_reload_status: Reloading filter
Jan 31 02:01:55 pfsense apinger: ALARM: WAN(8.8.8.8)  *** delay ***
Jan 31 02:02:05 pfsense check_reload_status: Reloading filter
Jan 31 02:02:16 pfsense apinger: ALARM: WAN(8.8.8.8)  *** down ***
Jan 31 02:02:26 pfsense check_reload_status: Reloading filter
Jan 31 02:02:49 pfsense php: /index.php: Successful webConfigurator login for us
er 'admin' from 192.168.70.203
Jan 31 02:02:49 pfsense php: /index.php: Successful webConfigurator login for us
er 'admin' from 192.168.70.203
Jan 31 02:03:03 pfsense sshd[29025]: Accepted keyboard-interactive/pam for root
from 192.168.70.203 port 52152 ssh2
Jan 31 02:04:19 pfsense dhclient[60861]: My address (74.67.172.72) was deleted,
dhclient exiting
Jan 31 02:04:19 pfsense dhclient[60861]: My address (74.67.172.72) was deleted,
dhclient exiting
Jan 31 02:04:19 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): Network is down
Jan 31 02:04:19 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): Network is down
Jan 31 02:04:19 pfsense dhclient: FAIL
Jan 31 02:04:19 pfsense dhclient[54382]: connection closed
Jan 31 02:04:19 pfsense dhclient[54382]: connection closed
Jan 31 02:04:19 pfsense dhclient[54382]: exiting.
Jan 31 02:04:19 pfsense dhclient[54382]: exiting.
Jan 31 02:04:19 pfsense dhclient[54382]: exiting.
Jan 31 02:04:30 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** down ***
Jan 31 02:04:40 pfsense check_reload_status: Reloading filter
Jan 31 02:05:06 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** delay ***
Jan 31 02:05:16 pfsense check_reload_status: Reloading filter
Jan 31 02:05:28 pfsense apinger: ALARM: WAN(8.8.8.8)  *** down ***
Jan 31 02:05:38 pfsense check_reload_status: Reloading filter
Jan 31 02:06:46 pfsense dhclient: PREINIT
Jan 31 02:06:46 pfsense miniupnpd[1378]: ioctl(s, SIOCGIFADDR, ...): Can't assig
n requested address
Jan 31 02:06:46 pfsense miniupnpd[1378]: ioctl(s, SIOCGIFADDR, ...): Can't assig
n requested address
Jan 31 02:06:46 pfsense miniupnpd[1378]: Failed to get IP for interface rl0
Jan 31 02:06:46 pfsense miniupnpd[1378]: Failed to get IP for interface rl0
Jan 31 02:06:46 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: cannot get public IP address, stopping
Jan 31 02:06:46 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: cannot get public IP address, stopping
Jan 31 02:06:46 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 02:06:46 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 02:06:46 pfsense dhclient[17897]: DHCPREQUEST on rl0 to 255.255.255.255 p
ort 67
Jan 31 02:06:46 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 02:06:46 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 02:06:47 pfsense dhclient[17897]: DHCPREQUEST on rl0 to 255.255.255.255 p
ort 67
Jan 31 02:06:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 02:06:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 02:06:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 02:06:47 pfsense kernel: arpresolve: can't allocate llinfo for 74.67.172.
1
Jan 31 02:06:47 pfsense dhclient[17897]: DHCPACK from 10.243.128.1
Jan 31 02:06:47 pfsense dhclient: REBOOT
Jan 31 02:06:47 pfsense dhclient: Starting add_new_address()
Jan 31 02:06:47 pfsense dhclient: ifconfig rl0 inet 74.67.172.72 netmask 255.255
.254.0 broadcast 255.255.255.255
Jan 31 02:06:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 02:06:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 02:06:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 02:06:47 pfsense miniupnpd[1378]: SendNATPMPPublicAddressChangeNotificati
on: sendto(s_udp=14): No route to host
Jan 31 02:06:47 pfsense dhclient: New IP Address (rl0): 74.67.172.72
Jan 31 02:06:47 pfsense dhclient: New Subnet Mask (rl0): 255.255.254.0
Jan 31 02:06:47 pfsense dhclient: New Broadcast Address (rl0): 255.255.255.255
Jan 31 02:06:47 pfsense dhclient: New Routers (rl0): 74.67.172.1
Jan 31 02:06:47 pfsense dhclient: Adding new routes to interface: rl0
Jan 31 02:06:47 pfsense dhclient: /sbin/route add default 74.67.172.1
Jan 31 02:06:47 pfsense dhclient: Creating resolv.conf
Jan 31 02:06:47 pfsense check_reload_status: rc.newwanip starting rl0
Jan 31 02:06:47 pfsense dhclient[17897]: bound to 74.67.172.72 -- renewal in 123
44 seconds.
Jan 31 02:06:48 pfsense apinger: alarm canceled: WAN(8.8.8.8)  *** down ***
Jan 31 02:06:48 pfsense shutdown: reboot by root:
            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              I think I have narrowed this down between this thread and another similar one:
              https://redmine.pfsense.org/issues/2792

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • S
                sinicide
                last edited by

                Thanks Jimp. I guess I'll keep an eye on this bug to see if/when it gets fixed.

                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  There is a potential fix in 2.0.3 and 2.1 snapshots for this now, so it's worth a try to upgrade and see if it works.

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • S
                    sinicide
                    last edited by

                    Well I'm already on the 2.0.3 Pre-release since I thought that might help my situation, I may try the 2.1 beta at some point over the weekend to see how it fairs.

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      The "prerelease" images of 2.0.3 are snapshots. If yours isn't dated yesterday or today, you don't have the fix.

                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      1 Reply Last reply Reply Quote 0
                      • S
                        sinicide
                        last edited by

                        I applied the latest one from Feb 6th last night and still had issues. (http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/i386/pfSense_RELENG_2_0/updates/) unless that is not the correct update link?

                        I came home and checked the system log and found two instances in which the issue still occurred.

                        1 Reply Last reply Reply Quote 0
                        • jimpJ
                          jimp Rebel Alliance Developer Netgate
                          last edited by

                          It may have been in the snapshot just after you updated, it's still worth updating and checking again.

                          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                          Need help fast? Netgate Global Support!

                          Do not Chat/PM for help!

                          1 Reply Last reply Reply Quote 0
                          • T
                            Trel
                            last edited by

                            @jimp:

                            It may have been in the snapshot just after you updated, it's still worth updating and checking again.

                            I didn't want to create a new topic for this, but I'm having the exact same problem in 2.0.3-RELEASE
                            (same scenario, same symptoms)
                            Did the bug fix not make it into the release version?

                            1 Reply Last reply Reply Quote 0
                            • jimpJ
                              jimp Rebel Alliance Developer Netgate
                              last edited by

                              The fix mentioned earlier in the thread did. It's possible you're hitting a different error/condition that the previous fix didn't correct. Probably best to start a fresh thread.

                              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                              Need help fast? Netgate Global Support!

                              Do not Chat/PM for help!

                              1 Reply Last reply Reply Quote 0
                              • T
                                Trel
                                last edited by

                                Ok, I'll have to wait until tonight so I can grab the full log.
                                (It was in the middle of occuring when I tried to login to verify the namecheap dns settings for the other topic >.< )

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