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

    Help

    Scheduled Pinned Locked Moved General pfSense Questions
    8 Posts 5 Posters 3.9k 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.
    • F
      forum
      last edited by

      Hi. my pfsense get a failed message and i don,t now why… this is the failed message..... ??? ???

      kernel: arplookup 1.1.1.1 failed: host is not on local network

      1 Reply Last reply Reply Quote 0
      • H
        hoba
        last edited by

        Download your config.xml at diagnostics>backup/restore and open it with a texteditor. Then search for "1.1.1.1". Maybe you have entered something wrong somewhere. Maybe some faulty static route or something.

        1 Reply Last reply Reply Quote 0
        • F
          forum
          last edited by

          ok. i test what you say but i dont see any wrong there… whats more can i do ??

          1 Reply Last reply Reply Quote 0
          • J
            jeroen234
            last edited by

            post youre config here maybe we see wat you did rong

            1 Reply Last reply Reply Quote 0
            • J
              Justinw
              last edited by

              @forum:

              Hi. my pfsense get a failed message and i don,t now why… this is the failed message..... ??? ???

              kernel: arplookup 1.1.1.1 failed: host is not on local network

              I use to get 0.0.0.0 failed: host is not on local network, For me it was a conflict with the cable modem, I had my pf set to 192.168.100.0/24 net which was the same that motorola cable modems resides on, they are usually 192.168.100.1, and if you pf is 192.168.100.1, that is trouble.  Had me stumped for a bit, maybe its not your issue, but I thought I would take a stab anyways.

              1 Reply Last reply Reply Quote 0
              • F
                forum
                last edited by

                no it is set to 192.168.32.1/24 this wasnt a problem with release 1.0    since the 1.0.1 release come out i have haft this problem..

                1 Reply Last reply Reply Quote 0
                • F
                  forum
                  last edited by

                  ok i will bring this back. how do i solve this problem ?

                  1 Reply Last reply Reply Quote 0
                  • Cry HavokC
                    Cry Havok
                    last edited by

                    Find the offending device and give it a valid IP address  ;D

                    Seriously - you can't "fix" this at the pfSense end - you've got to deal with the source of the packet that pfSense is receiving.  The only way to do that is track down the offending box and correct the IP configuration.

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