PFSense crash <7>arpresolve: can't allocate llinfo for 192.168.1.254 on em0


  • Hi. I am running PFsense 2.4.5p1 on a ESXi host connected to an AT&T gigabit fiber connection (directly to the ONT, using the wpa supp-licant and certs extracted from my AT&T GW, not though the AT&T GW).

    The interface for the WAN is em0, and PFSense has been running verey reliably, but a couple nights ago panic'd and rebooted the guest VM with a flood of these errors:

    <7>arpresolve: can't allocate llinfo for 192.168.1.254 on em0

    The info.0 log shows:

    Dump header from device: /dev/label/swap0
    Architecture: amd64
    Architecture Version: 1
    Dump Length: 157184
    Blocksize: 512
    Dumptime: Wed Aug 19 06:23:03 2020
    Hostname: XXXXXXX
    Magic: FreeBSD Text Dump
    Version String: FreeBSD 11.3-STABLE #243 abf8cba50ce(RELENG_2_4_5): Tue Jun 2 17:53:37 EDT 2020
    root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-245/obj/amd64/YNx4Qq3j/build/ce-crossbuild-245/source
    Panic String: page fault
    Dump Parity: 2690983692
    Bounds: 0
    Dump Status: good

    And here is crash dump stack trace:

    Crash report begins. Anonymous machine information:

    amd64
    11.3-STABLE
    FreeBSD 11.3-STABLE #243 abf8cba50ce(RELENG_2_4_5): Tue Jun 2 17:53:37 EDT 2020 root@buildbot1-nyi.netgate.com:/build/ce-crossbuild-245/obj/amd64/YNx4Qq3j/build/ce-crossbuild-245/sources/FreeBSD-src/sys/pfSense

    I've attached the dump log.

    Any idea as to what's going on? It's odd that IP address in the arp error would be on the WAN interface. It's not all related to the network address assigned from AT&T, but is used as a guest network on a VLAN hung off my lan interface vmx0, NOT em0 (the WAN).

    Is this some attack from the Internet on my PFSense FW?

    [0_1598031011080_panic info.txt](Uploading 100%)[0_1598031094322_panic info.txt](Uploading 100%)