Upgrading from 2.2.6 to 2.3 system does not boot - arprequest cannot find

  • Hello,

    I have upgraded my installation from 2.2.6 to 2.3 which went fine.

    Upon reboot the system does not fully start anymore, it hangs with error:

    arprequest cannot find matching address

    right after raising the LAN interface.

    My 2.2.6 setup was:

    2 NICs, one for WAN and one for LAN
    WAN NIC set up as PPPoE
    LAN set up with
    OpenVPN enabled
    IPv6 on WAN set to "None"
    IPv6 on LAN set to "Track interface"
    Some port forwarding rules

    The system just displays the"arprequest cannot find matching address" in console, it raises the WAN interface but I'm guessing not the LAN interface (no ping to the LAN IP and no internet connection).

    Please help.

    Thank you!

  • I'm having the exact same problem after upgrading.

    Sometimes I do get internet after a few reboots, but it fails again randomly after a few minutes and the arprequest message still keeps filling the console all the time, even when I do have internet.

    And when I go to: "Status / DHCP Leases" it shows devices(Desktops and a Wi-Fi access-point) offline which are in fact online(turned on and connected to LAN via a switch). And it shows the columns "start / end" as "n/a"

    It also seems to use significantly more RAM. 86% off 989MB at the moment and from what I recall, that used to be about half that. And the web interface seems less responsive

  • Rebel Alliance Developer Netgate

    Can you somehow capture or get a picture of the boot output before that point?

    Are you certain you're viewing the correct console and it isn't outputting something over serial instead of VGA?

  • Thank you for replying.

    Here it is:


    Is the system trying to start DHCPv6 service twice?

  • Friendly bump  :)

  • Rebel Alliance Developer Netgate

    I suspect that something is failing to setup your WAN connection properly, and you're actually hitting https://redmine.pfsense.org/issues/6177

    If you have IPv6 that is configured but not completely functional, the above could be happening. If you could reach the GUI I'd suggest setting System > Advanced, Networking, check Prefer IPv4 over IPv6.

  • I did a fresh install and restored individually backed up settings (filter, NAT and so on).

    Also checked the prefer IPv4 option though the IPv6 tunneling to my ISP via PPPoE works flawlessly.

    Thank you for the time spent responding! The fresh install performs as expected from a pfSense system (very close to perfect that is  :) )

    All the best!

  • I've also solved it, with me it was an improperly configured WAN connection.

Log in to reply