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

    MultiWAN + Bridge + Sticky OFF == kernel: arpresolve: can't allocate llinfo for

    Scheduled Pinned Locked Moved Routing and Multi WAN
    1 Posts 1 Posters 1.5k 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.
    • D
      df
      last edited by

      Hi, I'm currently using 2.0-rel on an Alix 2D3.
      My setup is a bit weird, but seems to somehow work ok.

      ISP1
      ADSL
      MGCP VoIP for 10 phones
      IP: 10.0.10.254
      Runs a dhcpd + tftp for the VoIP phones, it's traffic must passthru.
      We want to use this provider only for VoIP and as a backup provider

      ISP2
      SDSL
      Static Public IP
      We want to use this provider as main incoming and outgoing to the world

      pfSense
      LAN (10.0.10.251 - bridged to WAN)
      WAN (10.0.10.250 - bridged to LAN)
      OPT1 (x.x.x.x - Static Public IP)
      One Gateway Group is set with WAN GW + OPT1 GW == GWG1
      LAN Firewall rules: set to limit outgoing traffic, and redirect some portions of it (HTTP, MAIL) via GWG1 - work as expected
      WAN Firewall rules: set to allow * incoming (might be changed later), mainly to ensure the dhcp gets in, so the MBCP phones can work correctly
      OPT1 Firewall rules : set to block *, since this is a Public IP !
      No sticky connections set (!!!!)

      Symptom
      kernel: arpresolve: can't allocate llinfo for 10.0.10.254
      kernel: arpresolve: can't allocate llinfo for 10.0.10.254
      kernel: arpresolve: can't allocate llinfo for 10.0.10.254
      kernel: arpresolve: can't allocate llinfo for 10.0.10.254

      Now i found this bug report : http://redmine.pfsense.org/issues/337 that has the same symptoms except …
      !! I have sticky connections turned off !!
      Aside these messages everything -seems- to work fine (only 24hrs i deployed this in production ..)

      So what can be the issue ?

      Is my setup THAT weird ?

      Note here are a few extra notes regarding my setup:

      Caveat
      Since it's ISP1 that is pushing dhcpd infos, it's pushing itself as default GW to all network gear, so if ISP1 fails, no more net.

      Forthcoming upgrades
      ISP1 needs to have it's dhcpd push data to the phones, i'm planning to setup a dhcpd conf on pfsense that would forward all dhcpd queries from the phones to the ISP1, and address all others itself, so pfsense can server as dhcpd and main GW for the LAN network gear.

      Please comment..

      Every advise is good !

      df.

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