ARP flux how to solve





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







3















I have a server with 2 NICs having an IP address in the same subnet, this is what my /etc/network/interfaces looks like:



auto eth0
iface eth0 inet static
address 192.168.2.155
gateway 192.168.2.51
netmask 255.255.255.0
dns-nameservers 192.168.2.180
dns-domain exaple.com

auto eth1
iface eth1 inet static
address 192.168.2.156
netmask 255.255.255.0


So the idea is that eth0 with ip 192.168.2.155 is the 'management' interface with internet connectivity.
The eth1 NIC with IP 192.168.2.156 will be used to communicate with internal devices.



Now When i configure this with a default system, and try to ping eth1 on 192.168.2.156 with other devices on the LAN, these packets are not being received by eth1 as one would expect, but by eth0, I verified this by running tcpdump -i eth1 icmp, and can see no packets coming in. The client doing the ping is getting a reply, but from the wrong NIC/MAC address.



Now I've found out that this phenomenon is called 'ARP flux' and even nice articles describing how to solve it, problem is, none of these solutions seem to work for me.
This article seems to give the best explanation and fix, by running the following commands:



sudo sysctl -w net.ipv4.conf.all.arp_announce=1
sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
sudo sysctl -w net.ipv4.conf.all.rp_filter=0


This seems to do something, in that I start receiving packets on eth1, but it completely disables any communication on eth0 and IP address 192.168.2.155.



Any other ideas as to what I could try?










share|improve this question





























    3















    I have a server with 2 NICs having an IP address in the same subnet, this is what my /etc/network/interfaces looks like:



    auto eth0
    iface eth0 inet static
    address 192.168.2.155
    gateway 192.168.2.51
    netmask 255.255.255.0
    dns-nameservers 192.168.2.180
    dns-domain exaple.com

    auto eth1
    iface eth1 inet static
    address 192.168.2.156
    netmask 255.255.255.0


    So the idea is that eth0 with ip 192.168.2.155 is the 'management' interface with internet connectivity.
    The eth1 NIC with IP 192.168.2.156 will be used to communicate with internal devices.



    Now When i configure this with a default system, and try to ping eth1 on 192.168.2.156 with other devices on the LAN, these packets are not being received by eth1 as one would expect, but by eth0, I verified this by running tcpdump -i eth1 icmp, and can see no packets coming in. The client doing the ping is getting a reply, but from the wrong NIC/MAC address.



    Now I've found out that this phenomenon is called 'ARP flux' and even nice articles describing how to solve it, problem is, none of these solutions seem to work for me.
    This article seems to give the best explanation and fix, by running the following commands:



    sudo sysctl -w net.ipv4.conf.all.arp_announce=1
    sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
    sudo sysctl -w net.ipv4.conf.all.rp_filter=0


    This seems to do something, in that I start receiving packets on eth1, but it completely disables any communication on eth0 and IP address 192.168.2.155.



    Any other ideas as to what I could try?










    share|improve this question

























      3












      3








      3


      2






      I have a server with 2 NICs having an IP address in the same subnet, this is what my /etc/network/interfaces looks like:



      auto eth0
      iface eth0 inet static
      address 192.168.2.155
      gateway 192.168.2.51
      netmask 255.255.255.0
      dns-nameservers 192.168.2.180
      dns-domain exaple.com

      auto eth1
      iface eth1 inet static
      address 192.168.2.156
      netmask 255.255.255.0


      So the idea is that eth0 with ip 192.168.2.155 is the 'management' interface with internet connectivity.
      The eth1 NIC with IP 192.168.2.156 will be used to communicate with internal devices.



      Now When i configure this with a default system, and try to ping eth1 on 192.168.2.156 with other devices on the LAN, these packets are not being received by eth1 as one would expect, but by eth0, I verified this by running tcpdump -i eth1 icmp, and can see no packets coming in. The client doing the ping is getting a reply, but from the wrong NIC/MAC address.



      Now I've found out that this phenomenon is called 'ARP flux' and even nice articles describing how to solve it, problem is, none of these solutions seem to work for me.
      This article seems to give the best explanation and fix, by running the following commands:



      sudo sysctl -w net.ipv4.conf.all.arp_announce=1
      sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
      sudo sysctl -w net.ipv4.conf.all.rp_filter=0


      This seems to do something, in that I start receiving packets on eth1, but it completely disables any communication on eth0 and IP address 192.168.2.155.



      Any other ideas as to what I could try?










      share|improve this question














      I have a server with 2 NICs having an IP address in the same subnet, this is what my /etc/network/interfaces looks like:



      auto eth0
      iface eth0 inet static
      address 192.168.2.155
      gateway 192.168.2.51
      netmask 255.255.255.0
      dns-nameservers 192.168.2.180
      dns-domain exaple.com

      auto eth1
      iface eth1 inet static
      address 192.168.2.156
      netmask 255.255.255.0


      So the idea is that eth0 with ip 192.168.2.155 is the 'management' interface with internet connectivity.
      The eth1 NIC with IP 192.168.2.156 will be used to communicate with internal devices.



      Now When i configure this with a default system, and try to ping eth1 on 192.168.2.156 with other devices on the LAN, these packets are not being received by eth1 as one would expect, but by eth0, I verified this by running tcpdump -i eth1 icmp, and can see no packets coming in. The client doing the ping is getting a reply, but from the wrong NIC/MAC address.



      Now I've found out that this phenomenon is called 'ARP flux' and even nice articles describing how to solve it, problem is, none of these solutions seem to work for me.
      This article seems to give the best explanation and fix, by running the following commands:



      sudo sysctl -w net.ipv4.conf.all.arp_announce=1
      sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
      sudo sysctl -w net.ipv4.conf.all.rp_filter=0


      This seems to do something, in that I start receiving packets on eth1, but it completely disables any communication on eth0 and IP address 192.168.2.155.



      Any other ideas as to what I could try?







      networking server ethernet






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 27 '15 at 0:39









      AlexAlex

      12116




      12116






















          2 Answers
          2






          active

          oldest

          votes


















          0














          Based on this article Change to:



          sysctl -w net.ipv4.conf.all.arp_ignore=1
          sysctl -w net.ipv4.conf.all.arp_announce=2
          sysctl -w net.ipv4.conf.all.arp_filter=1





          share|improve this answer
























          • I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

            – Alex
            Jan 27 '15 at 11:53











          • If eth0 you user only for access from internet, set interface to be in different network.

            – 2707974
            Jan 27 '15 at 12:02











          • Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

            – Alex
            Jan 28 '15 at 12:50



















          0














          Based on this post and this post did you try with?:



          net.ipv4.conf.default.rp_filter = 2


          Did you fix it?



          EDIT:
          I mean... everything:



          sudo sysctl -w net.ipv4.conf.all.arp_announce=1
          sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
          sudo sysctl -w net.ipv4.conf.all.rp_filter=2





          share|improve this answer


























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "89"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f578210%2farp-flux-how-to-solve%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Based on this article Change to:



            sysctl -w net.ipv4.conf.all.arp_ignore=1
            sysctl -w net.ipv4.conf.all.arp_announce=2
            sysctl -w net.ipv4.conf.all.arp_filter=1





            share|improve this answer
























            • I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

              – Alex
              Jan 27 '15 at 11:53











            • If eth0 you user only for access from internet, set interface to be in different network.

              – 2707974
              Jan 27 '15 at 12:02











            • Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

              – Alex
              Jan 28 '15 at 12:50
















            0














            Based on this article Change to:



            sysctl -w net.ipv4.conf.all.arp_ignore=1
            sysctl -w net.ipv4.conf.all.arp_announce=2
            sysctl -w net.ipv4.conf.all.arp_filter=1





            share|improve this answer
























            • I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

              – Alex
              Jan 27 '15 at 11:53











            • If eth0 you user only for access from internet, set interface to be in different network.

              – 2707974
              Jan 27 '15 at 12:02











            • Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

              – Alex
              Jan 28 '15 at 12:50














            0












            0








            0







            Based on this article Change to:



            sysctl -w net.ipv4.conf.all.arp_ignore=1
            sysctl -w net.ipv4.conf.all.arp_announce=2
            sysctl -w net.ipv4.conf.all.arp_filter=1





            share|improve this answer













            Based on this article Change to:



            sysctl -w net.ipv4.conf.all.arp_ignore=1
            sysctl -w net.ipv4.conf.all.arp_announce=2
            sysctl -w net.ipv4.conf.all.arp_filter=1






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 27 '15 at 11:20









            27079742707974

            8,16852340




            8,16852340













            • I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

              – Alex
              Jan 27 '15 at 11:53











            • If eth0 you user only for access from internet, set interface to be in different network.

              – 2707974
              Jan 27 '15 at 12:02











            • Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

              – Alex
              Jan 28 '15 at 12:50



















            • I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

              – Alex
              Jan 27 '15 at 11:53











            • If eth0 you user only for access from internet, set interface to be in different network.

              – 2707974
              Jan 27 '15 at 12:02











            • Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

              – Alex
              Jan 28 '15 at 12:50

















            I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

            – Alex
            Jan 27 '15 at 11:53





            I just tried these but no luck, same result as before i.e.: All traffic shifts from eth0 to eth1 when running these commands

            – Alex
            Jan 27 '15 at 11:53













            If eth0 you user only for access from internet, set interface to be in different network.

            – 2707974
            Jan 27 '15 at 12:02





            If eth0 you user only for access from internet, set interface to be in different network.

            – 2707974
            Jan 27 '15 at 12:02













            Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

            – Alex
            Jan 28 '15 at 12:50





            Sorry not the answer I was hoping for... For reasons I don't think have to be discussed here, I have to use 2 IP addresses on the same subnet.

            – Alex
            Jan 28 '15 at 12:50













            0














            Based on this post and this post did you try with?:



            net.ipv4.conf.default.rp_filter = 2


            Did you fix it?



            EDIT:
            I mean... everything:



            sudo sysctl -w net.ipv4.conf.all.arp_announce=1
            sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
            sudo sysctl -w net.ipv4.conf.all.rp_filter=2





            share|improve this answer






























              0














              Based on this post and this post did you try with?:



              net.ipv4.conf.default.rp_filter = 2


              Did you fix it?



              EDIT:
              I mean... everything:



              sudo sysctl -w net.ipv4.conf.all.arp_announce=1
              sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
              sudo sysctl -w net.ipv4.conf.all.rp_filter=2





              share|improve this answer




























                0












                0








                0







                Based on this post and this post did you try with?:



                net.ipv4.conf.default.rp_filter = 2


                Did you fix it?



                EDIT:
                I mean... everything:



                sudo sysctl -w net.ipv4.conf.all.arp_announce=1
                sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
                sudo sysctl -w net.ipv4.conf.all.rp_filter=2





                share|improve this answer















                Based on this post and this post did you try with?:



                net.ipv4.conf.default.rp_filter = 2


                Did you fix it?



                EDIT:
                I mean... everything:



                sudo sysctl -w net.ipv4.conf.all.arp_announce=1
                sudo sysctl -w net.ipv4.conf.all.arp_ignore=2
                sudo sysctl -w net.ipv4.conf.all.rp_filter=2






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jan 21 '16 at 9:00

























                answered Jan 20 '16 at 17:35









                rasputinorasputino

                1011




                1011






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Ask Ubuntu!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f578210%2farp-flux-how-to-solve%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to change which sound is reproduced for terminal bell?

                    Can I use Tabulator js library in my java Spring + Thymeleaf project?

                    Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents