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

    WAN fails to pass data after reboot (until interface is disabled and enabled).

    Scheduled Pinned Locked Moved General pfSense Questions
    1 Posts 1 Posters 345 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.
    • T
      Tom7141
      last edited by

      Not sure where to put this but i had a strange issue where when ever pfsense was rebooted the WAN connection wouldn't pass any data no pings etc, even though the interface shows as up. the only thing that showed up in the logs was this line:

      arpresolve: can't allocate llinfo for 192.168.1.254 on re0_vlan8
      arpresolve: can't allocate llinfo for 192.168.1.254 on re0_vlan8
      arpresolve: can't allocate llinfo for 192.168.1.254 on re0_vlan8
      arpresolve: can't allocate llinfo for 192.168.1.254 on re0_vlan8

      it repeats meany times every second or so. strangely by going to the menu interfaces > WAN then unticking the enable interface box save and apply changes then go back re-tick the box save and apply the interface will start working again until the next time the system is rebooted and the steps would have to be repeated.

      this has been going on for a while now, since then however i've backed up and reinstalled pfsense, it was working normally until i reloaded the backup and it went back to its old ticks. i then reinstalled it again but only restored the interfaces, vlans, firewall, NAT, OpenVPN settings from the backup and now pfsense works perfectly even after a reboot. i can only assume that somewhere in the backup there is a setting that somehow curses this issue to pop up at reboot though i find it strange that simply disabling and enabling the interface temporarily fixes the problem till the next reboot…..

      As i say i've over come the problem on my own but wanted to share this experience in case some one else has this problem, if i have the time and anyone's interested i could sanitise the backup and post it if maybe one of the developers wants it.

      Tom

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