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

    Kernel: Arp moved from - to

    General pfSense Questions
    10
    26
    19.4k
    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.
    • Z
      z3r0x
      last edited by

      Hi

      I have quite a lot of these messages in the logfile

      kernel: arp: 10.0.10.19 moved from 58:55:ca:39:e3:19 to 00:24:36:a3:28:2f on lagg0_vlan110
      kernel: arp: 10.0.10.19 moved from 00:24:36:a3:28:2f to 58:55:ca:39:e3:19 on lagg0_vlan110

      lagg0 is configured with LCAP.

      Is this something to worry about or just normal?

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

        how frequent is that ?

        if this happens multiple times per minute with the same ip-address then you might have a static ip configured inside your dhcp pool

        1 Reply Last reply Reply Quote 0
        • Z
          z3r0x
          last edited by

          It maybe happens every 15-20 minutes… depends a little bit.
          I don't think that I have configured any static ip adresses inside the dhcp pool but I will have a look.

          1 Reply Last reply Reply Quote 0
          • S
            serialdie
            last edited by

            I have the same issue with no static inside the dhcp pool.

            1 Reply Last reply Reply Quote 0
            • Z
              z3r0x
              last edited by

              I know that 58:55:ca:39:e3:19 is my appleTV. Not sure what device the other MAC is… Is there a way to find out?

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

                @z3r0x:

                kernel: arp: 10.0.10.19 moved from 58:55:ca:39:e3:19 to 00:24:36:a3:28:2f on lagg0_vlan110
                kernel: arp: 10.0.10.19 moved from 00:24:36:a3:28:2f to 58:55:ca:39:e3:19 on lagg0_vlan110

                You probably have two devices with the same IP address. This can happen in a variety of ways including:
                1. a device has been configured with a static IP  address that is inside the dynamic IP address range of the DHCP server.
                2. You have two (or more) DHCP servers on the same network and they have overlapping address pools
                3. you have two devices configured with the same IP address.
                4. you have a device with two interfaces (perhaps wired and wireless) and the same IP address configured on each interface (possibly DHCP configured) and the device is switching between interfaces.

                1 Reply Last reply Reply Quote 0
                • S
                  serialdie
                  last edited by

                  Not in my case…

                  arp: 10.30.2.99 moved from b0:b2:dc:ed:59:XX to 00:00:00:00:00:00 on re1
                  arp: 10.30.2.99 moved from 00:00:00:00:00:00 to b0:b2:dc:ed:59:XX on re1

                  1 Reply Last reply Reply Quote 0
                  • Z
                    z3r0x
                    last edited by

                    @wallabybob:

                    You probably have two devices with the same IP address. This can happen in a variety of ways including:
                    1. a device has been configured with a static IP  address that is inside the dynamic IP address range of the DHCP server.
                    2. You have two (or more) DHCP servers on the same network and they have overlapping address pools
                    3. you have two devices configured with the same IP address.
                    4. you have a device with two interfaces (perhaps wired and wireless) and the same IP address configured on each interface (possibly DHCP configured) and the device is switching between interfaces.

                    Hi. Apple TV is using DHCP. There is only 1 DHCP running and no one is using the same ip. But what I have seen when sniffing with Wireshark was something with IPv6. I have added a txt file. Maybe this tells you more? I don't remember doing anything with ipv6.

                    dump.txt

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

                      @serialdie: i'm guessing you have a hardware failure (broken networkcard/cabling/…) mac address 00:00:00:00:00:00 is invalid

                      @z3r0x: both mac addresses you mention are from apple hardware. the logs indicate both devices (or 1 device using multiple interfaces) compete for the same address.
                      ipv6 does not have ARP, so it can not be involved - ipv6 has NDP (similar purpose, not the same)
                      http://en.wikipedia.org/wiki/Neighbor_Discovery_Protocol

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

                        @z3r0x:

                        Hi

                        I have quite a lot of these messages in the logfile

                        kernel: arp: 10.0.10.19 moved from 58:55:ca:39:e3:19 to 00:24:36:a3:28:2f on lagg0_vlan110
                        kernel: arp: 10.0.10.19 moved from 00:24:36:a3:28:2f to 58:55:ca:39:e3:19 on lagg0_vlan110

                        lagg0 is configured with LCAP.

                        Is this something to worry about or just normal?

                        Do you have a Time Capsule or AirPort Extreme to go with the AppleTV?  If so, that is, unfortunately, normal.

                        I can break anything.

                        1 Reply Last reply Reply Quote 0
                        • C
                          cmb
                          last edited by

                          @Jason:

                          Do you have a Time Capsule or AirPort Extreme to go with the AppleTV?  If so, that is, unfortunately, normal.

                          Wow, really? Why's that? Odd that effectively the symptoms of an IP conflict would be normal, but I recall seeing that once on my home network also between two Apple vendor MACs. Don't have a time capsule or AirPort Extreme, have 2 Apple TVs, a couple iPhones, couple iPads, couple MacBook Pros, and an iMac. At the time I didn't even have time to check which MAC went to which device, and it hasn't recurred so I haven't bothered digging into it.

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

                            @cmb:

                            @Jason:

                            Do you have a Time Capsule or AirPort Extreme to go with the AppleTV?  If so, that is, unfortunately, normal.

                            Wow, really? Why's that? Odd that effectively the symptoms of an IP conflict would be normal, but I recall seeing that once on my home network also between two Apple vendor MACs. Don't have a time capsule or AirPort Extreme, have 2 Apple TVs, a couple iPhones, couple iPads, couple MacBook Pros, and an iMac. At the time I didn't even have time to check which MAC went to which device, and it hasn't recurred so I haven't bothered digging into it.

                            It's a "feature" and part of the Bonjour Sleep Proxy.

                            http://support.apple.com/kb/HT3774

                            Also:

                            https://discussions.apple.com/thread/2160614
                            http://blog.martinshouse.com/2009/11/apple-time-capsule-steals-ip-addresses.html?m=1
                            http://en.usenet.digipedia.org/thread/16243/200/

                            I can break anything.

                            1 Reply Last reply Reply Quote 0
                            • S
                              serialdie
                              last edited by

                              @Jason:

                              @cmb:

                              @Jason:

                              Do you have a Time Capsule or AirPort Extreme to go with the AppleTV?  If so, that is, unfortunately, normal.

                              Wow, really? Why's that? Odd that effectively the symptoms of an IP conflict would be normal, but I recall seeing that once on my home network also between two Apple vendor MACs. Don't have a time capsule or AirPort Extreme, have 2 Apple TVs, a couple iPhones, couple iPads, couple MacBook Pros, and an iMac. At the time I didn't even have time to check which MAC went to which device, and it hasn't recurred so I haven't bothered digging into it.

                              It's a "feature" and part of the Bonjour Sleep Proxy.

                              http://support.apple.com/kb/HT3774

                              Also:

                              https://discussions.apple.com/thread/2160614
                              http://blog.martinshouse.com/2009/11/apple-time-capsule-steals-ip-addresses.html?m=1
                              http://en.usenet.digipedia.org/thread/16243/200/

                              Ha! That makes sense.
                              I have bonjour enable on my nas and thats the IP of the nas.

                              Thanks.

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

                                @Jason:

                                @cmb:

                                @Jason:

                                Do you have a Time Capsule or AirPort Extreme to go with the AppleTV?  If so, that is, unfortunately, normal.

                                Wow, really? Why's that? Odd that effectively the symptoms of an IP conflict would be normal, but I recall seeing that once on my home network also between two Apple vendor MACs. Don't have a time capsule or AirPort Extreme, have 2 Apple TVs, a couple iPhones, couple iPads, couple MacBook Pros, and an iMac. At the time I didn't even have time to check which MAC went to which device, and it hasn't recurred so I haven't bothered digging into it.

                                It's a "feature" and part of the Bonjour Sleep Proxy.

                                http://support.apple.com/kb/HT3774

                                Also:

                                https://discussions.apple.com/thread/2160614
                                http://blog.martinshouse.com/2009/11/apple-time-capsule-steals-ip-addresses.html?m=1
                                http://en.usenet.digipedia.org/thread/16243/200/

                                If we disable the sleep proxy "feature" on all the MACs will the errors go away?

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

                                  If you just want those messages not to appear in the log add the system tunable "net.link.ether.inet.log_arp_movements" and set its value to 0.

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

                                    @joako:

                                    If we disable the sleep proxy "feature" on all the MACs will the errors go away?

                                    No. The issue is with the TC and AE, not the Macs, and you can't disable that feature on them.

                                    @bardelot:

                                    If you just want those messages not to appear in the log add the system tunable "net.link.ether.inet.log_arp_movements" and set its value to 0.

                                    I actually think the Suppress ARP messages setting will do it as well. If memory serves I didn't add a manual tunable.

                                    I can break anything.

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

                                      @Jason:

                                      I actually think the Suppress ARP messages setting will do it as well. If memory serves I didn't add a manual tunable.

                                      Yes it sets the same tunable and also net.link.ether.inet.log_arp_wrong_iface="0" .

                                      1 Reply Last reply Reply Quote 0
                                      • T
                                        tojoski
                                        last edited by

                                        This is happening on my Home Server as well.. I have 2 Gigabit Ethernet ports that are teamed to a single connection.

                                        Feb 5 12:33:22

                                        kernel: arp: 10.1.1.5 moved from 00:e0:81:ba:57:c4 to 00:e0:81:ba:57:c5 on em0

                                        Feb 5 12:33:22

                                        kernel: arp: 10.1.1.5 moved from 00:e0:81:ba:57:c5 to 00:e0:81:ba:57:c4 on em0

                                        Will this create an issue? It seems to be working ok

                                        1 Reply Last reply Reply Quote 0
                                        • C
                                          cmb
                                          last edited by

                                          @tojoski:

                                          This is happening on my Home Server as well.. I have 2 Gigabit Ethernet ports that are teamed to a single connection.

                                          Feb 5 12:33:22

                                          kernel: arp: 10.1.1.5 moved from 00:e0:81:ba:57:c4 to 00:e0:81:ba:57:c5 on em0

                                          Feb 5 12:33:22

                                          kernel: arp: 10.1.1.5 moved from 00:e0:81:ba:57:c5 to 00:e0:81:ba:57:c4 on em0

                                          Will this create an issue? It seems to be working ok

                                          That's a different scenario, that's what you see when using certain types of NIC bonding. It's fine.

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

                                            @Jason:

                                            @joako:

                                            If we disable the sleep proxy "feature" on all the MACs will the errors go away?

                                            No. The issue is with the TC and AE, not the Macs, and you can't disable that feature on them.

                                            @bardelot:

                                            If you just want those messages not to appear in the log add the system tunable "net.link.ether.inet.log_arp_movements" and set its value to 0.

                                            I actually think the Suppress ARP messages setting will do it as well. If memory serves I didn't add a manual tunable.

                                            I don't have any Time Capsule or Airport Express. Only Apple TV, 2x MacBook that are here sometimes and probably a few PCs with iTunes installed, if that matters.

                                            But I still get the errors in the pfSense log.

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