BGP failing. arpresolve: can't allocate llinfo for



  • Hi

    We are running a test together with our ISP to use a local BGP towards them. I was hoping this was going to be quick and easy, so we could put it out in production.. But, that not the case here - yet….

    Both PFsense are online, ISP announced the linknets and gateway. The routed subnet and carp are also working 100%.
    Its working for a little while. Minutes, half hour/hour. Then one of the firewalls cant get online anymore. It looks like its random which firewall that looses connectivity. It doesnt seem like the bgpsessions from that firewall and isp are talking. Last update: many minutes/hours

    I know that the isp set up a route map yesterday to be able to control the failover on the routed subnet. Looks like thats working when I test with both firewalls (when both are online...)

    1 week ago we tried to setup bgp with carp status ip, but then the failover is kind of slow and I cant get the secondary firewall online (not getting its routes from bgp, therefor the linknet isnt online).

    dmesg in both firewalls are getting spammed with these:

    fw1:
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0
    arpresolve: can't allocate llinfo for xx.175.30.xx on bge0

    Also getting error on other waninterface on fw1, just not right now.

    fw2:
    arpresolve: can't allocate llinfo for xx.28.7.105 on bge0
    arpresolve: can't allocate llinfo for xx.28.7.105 on bge0
    arpresolve: can't allocate llinfo for xx.28.7.109 on em0
    arpresolve: can't allocate llinfo for xx.28.7.109 on em0
    arpresolve: can't allocate llinfo for xx.28.7.109 on em0
    arpresolve: can't allocate llinfo for xx.28.7.105 on bge0
    arpresolve: can't allocate llinfo for xx.28.7.109 on em0

    All I need to do to get the failing firewall online is ifconfig bge0/em0 down and up. Then its reconnecting the bgpsessions and get the routes.

    BGP raw config:

    This file was created by the package manager. Do not edit!

    AS xxxxx
    fib-update yes
    holdtime 30
    listen on 0.0.0.0
    network xx.160.227.208/28
    network xx:270:203F::/48
    group "Kvantel" {
    remote-as xxxx
    neighbor xx.175.30.81 {
    descr "KvantelMaster"
    announce all 
    set localpref 101
    local-address xx.175.30.82
    }
    neighbor xx.175.30.85 {
    descr "KvantelSlave"
    announce all 
    set localpref 100
    local-address xx.175.30.86
    }
    neighbor xx:270:1:56::1 {
    descr "KvantelMasterIPv6"
    announce all 
    set localpref 101
    local-address xx:270:1:56::2
    }
    neighbor xx:270:1:56:4000::1 {
    descr "KvantelSlaveIPv6"
    announce all 
    set localpref 100
    local-address xx:270:1:56:4000::2
    }
    }
    deny from any
    deny to any
    allow from xx.175.30.81
    allow to xx.175.30.81
    allow from xx.175.30.85
    allow to xx.175.30.85
    allow from xx:270:1:56::1
    allow to xx:270:1:56::1
    allow from xx:270:1:56:4000::1
    allow to xx:270:1:56:4000::1

    ![Visio PFSense HA.png](/public/imported_attachments/1/Visio PFSense HA.png)
    ![Visio PFSense HA.png_thumb](/public/imported_attachments/1/Visio PFSense HA.png_thumb)



  • Anyone?



  • Tested with a new pfsense/hardware today.

    Only with one firewall and two neighbors (isp master/slave).

    Still getting arp error in syslog..

    arp against slave is also down (so is the bgp.)

    [2.3.4-RELEASE][root@pfSense.localdomain]/root: dmesg
    arpresolve: can't allocate llinfo for xx.175.30.85 on igb1
    arpresolve: can't allocate llinfo for xx.175.30.85 on igb1
    arpresolve: can't allocate llinfo for xx.175.30.85 on igb1
    arpresolve: can't allocate llinfo for xx.175.30.85 on igb1
    arpresolve: can't allocate llinfo for xx.175.30.85 on igb1



  • I get that error when cable modem goes offline.
    Never used bgp,  so can't help there


Log in to reply