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

    Arp error on pfsense

    Scheduled Pinned Locked Moved General pfSense Questions
    5 Posts 2 Posters 3.8k 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.
    • B
      Bourrinos
      last edited by

      Hello
      I don't know in what section I have to post this question, so I posted here, if you need to move it, no probleme.

      I setup a pfsense.
      I'v computer, with motherboard don't handle vt, with 3700+ and 2go ram
      under debian squeeze.

      I'v installed Virtualbox, and install pfsense. I'v 3 network card, two for virtualbox, in direct bridge and the third is for the host (my debian squeeze) and it's not connected for the moment.
      When pfsense boot, it's take control of my two network card, one for the wan, another for the lan.

      I'v livebox (french) to go over internet.

      I sync with git mainline, to resolv tap issue.

      I use openvpn to connect to vpntunnel.se

      I use DE sever and it's fine, yesterday, all goes fine, but this monrning, I'v issue with ARP.

      My network, is simple, it's test network

      WAN -> 192.169.1.199 for psfsense em0
      LAN -> 192.168.1.210 -> em1 (correponding of virtualbox acces)
      gw -> 192.168.1.1

      Wan is use with gw, i connect to pfsense with my computer 192.168.1.219 (static ip)
      No dhcp server on pfsense, just forward dns

      I use two rules to forward ports, and that's it.

      This morning openvnp is down, no way to access internet and in the log

      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arp: 7c:03:4c:63:d1:4f attempts to modify permanent entry for 192.168.1.1 on em1                                                                                                                         
      arp: 7c:03:4c:63:d1:4f attempts to modify permanent entry for 192.168.1.1 on em1                                                                                                                         
      arp: 7c:03:4c:63:d1:4f attempts to modify permanent entry for 192.168.1.1 on em1                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1                                                                                                                                                         
      arpresolve: can't allocate llinfo for 192.168.1.1

      HAve you an idea ?

      Thanks (i'v another two question about my pfsense, but, I know how to post, and want to have on topic for each question)

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        You probably have an invalid configuration: Your pfSense WAN and LAN interfaces need to be on distinct IP subnetworks. You didn't specify network masks so I can't tell for certain.

        1 Reply Last reply Reply Quote 0
        • B
          Bourrinos
          last edited by

          I use 192.168.199 for the wan and .210 for the lan, with 255.255.255.0

          You tell I need to have different subnetwork for lan and wan, why ?

          Something like :

          WAN 192.168.1.199/24
          LAN 192.168.0.210/24

          ?

          Wan have to be in the same subnetwork than the GW, if my gateway is on 192.168.1.1, i need wan on 192.168.0.0 subnetworks ?

          it is correct ?

          ps: thank you ;) I use pfsense no for longer, and my network skill need to be improved ;)

          1 Reply Last reply Reply Quote 0
          • B
            Bourrinos
            last edited by

            It's ok this morning, thank you, I change wan and lan for differents subnetworks

            no arp problem

            If someone can tell my why it's important, for the knowledge ^^

            thanks

            1 Reply Last reply Reply Quote 0
            • W
              wallabybob
              last edited by

              When deciding which interface to use to send an IP packet, IP software will send the packet on the interface belong to the subnet of the destination (either the ultimate destination or a router which will forward the packet closer to its destination). If you have multiple interfaces belong to the same subnet then it is not well defined which interface will get used (if any).

              There is a Wikipedia article on IP routing which you may find informative.

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