WANem to route between machines?












2















I have installed WANem 3.0 Beta 2 on a physical machine with 2 interfaces, and I have 2 Linux boxes connected to it. Like so:



Linux1:100.100.100.2 <--> 100.100.100.1:WANem:200.200.200.1 <--> 200.200.200.2 Linux2



I have set each Linux box to use the WANem interface they are connected to as their gateway. Each Linux box can ping the addresses of both WANem interfaces (ie, Linux1 can ping both 100.100.100.1 and 200.200.200.1). However neither of them can ping each other. From reading tutorials, it seems that it should work by default, but it is not working. Does anyone know how to set up WANem to do this kind of routing? I'm not familiar with the WANem shell.



Thanks!



EDIT: It seems that in this configuration you need to manually add IP forwarding - in the WANem shell I typed:



echo 1 > /proc/sys/net/ipv4/ip_forward


and I was able to ping both endpoints from each other. This is just a temporary change, so if you reboot it will revert to not forwarding. I haven't tried it yet but apparently this is controlled by the file /etc/network/options, so you can edit this and change ip_forward=no to ip_forward=yes and the change should be permanent.










share|improve this question





























    2















    I have installed WANem 3.0 Beta 2 on a physical machine with 2 interfaces, and I have 2 Linux boxes connected to it. Like so:



    Linux1:100.100.100.2 <--> 100.100.100.1:WANem:200.200.200.1 <--> 200.200.200.2 Linux2



    I have set each Linux box to use the WANem interface they are connected to as their gateway. Each Linux box can ping the addresses of both WANem interfaces (ie, Linux1 can ping both 100.100.100.1 and 200.200.200.1). However neither of them can ping each other. From reading tutorials, it seems that it should work by default, but it is not working. Does anyone know how to set up WANem to do this kind of routing? I'm not familiar with the WANem shell.



    Thanks!



    EDIT: It seems that in this configuration you need to manually add IP forwarding - in the WANem shell I typed:



    echo 1 > /proc/sys/net/ipv4/ip_forward


    and I was able to ping both endpoints from each other. This is just a temporary change, so if you reboot it will revert to not forwarding. I haven't tried it yet but apparently this is controlled by the file /etc/network/options, so you can edit this and change ip_forward=no to ip_forward=yes and the change should be permanent.










    share|improve this question



























      2












      2








      2








      I have installed WANem 3.0 Beta 2 on a physical machine with 2 interfaces, and I have 2 Linux boxes connected to it. Like so:



      Linux1:100.100.100.2 <--> 100.100.100.1:WANem:200.200.200.1 <--> 200.200.200.2 Linux2



      I have set each Linux box to use the WANem interface they are connected to as their gateway. Each Linux box can ping the addresses of both WANem interfaces (ie, Linux1 can ping both 100.100.100.1 and 200.200.200.1). However neither of them can ping each other. From reading tutorials, it seems that it should work by default, but it is not working. Does anyone know how to set up WANem to do this kind of routing? I'm not familiar with the WANem shell.



      Thanks!



      EDIT: It seems that in this configuration you need to manually add IP forwarding - in the WANem shell I typed:



      echo 1 > /proc/sys/net/ipv4/ip_forward


      and I was able to ping both endpoints from each other. This is just a temporary change, so if you reboot it will revert to not forwarding. I haven't tried it yet but apparently this is controlled by the file /etc/network/options, so you can edit this and change ip_forward=no to ip_forward=yes and the change should be permanent.










      share|improve this question
















      I have installed WANem 3.0 Beta 2 on a physical machine with 2 interfaces, and I have 2 Linux boxes connected to it. Like so:



      Linux1:100.100.100.2 <--> 100.100.100.1:WANem:200.200.200.1 <--> 200.200.200.2 Linux2



      I have set each Linux box to use the WANem interface they are connected to as their gateway. Each Linux box can ping the addresses of both WANem interfaces (ie, Linux1 can ping both 100.100.100.1 and 200.200.200.1). However neither of them can ping each other. From reading tutorials, it seems that it should work by default, but it is not working. Does anyone know how to set up WANem to do this kind of routing? I'm not familiar with the WANem shell.



      Thanks!



      EDIT: It seems that in this configuration you need to manually add IP forwarding - in the WANem shell I typed:



      echo 1 > /proc/sys/net/ipv4/ip_forward


      and I was able to ping both endpoints from each other. This is just a temporary change, so if you reboot it will revert to not forwarding. I haven't tried it yet but apparently this is controlled by the file /etc/network/options, so you can edit this and change ip_forward=no to ip_forward=yes and the change should be permanent.







      linux networking routing wanem






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 15 '15 at 20:23







      user2792137

















      asked Jun 12 '15 at 18:23









      user2792137user2792137

      113




      113






















          1 Answer
          1






          active

          oldest

          votes


















          0














          A bit late to the show here, but as there have been no new releases of WANem since this was posted, it's relevant.



          There was actually a Debian Squeeze bug that was present in the version of knoppix that WANem 3.0 was based on that complicates this a bit.



          The solution is to add the setting net.ipv4.ip_forward = 1 to /etc/sysctl.conf (because in Debian Squeeze, the /etc/network/options was deprecated).



          This is only part of the solution though, due to the bug. Debian Squeeze executed /etc/init.d/procps (which applies the settings in sysctl configuration) before the modules for networking were loaded, thus they were ignored by the modules. To work around this, you need to restart the /etc/init.d/procps service in /etc/rc.local. Full credit for this workaround goes to this post by Vladislav Kononenko



          The linked issue was based on a system that had an empty rc.local file, so use this example instead, as WANem has necessary logic in rc.local for it's startup.



          rc.local



          #!/bin/bash
          #
          # rc.local
          #
          # Load kernel variables from /etc/sysctl.d and /etc/sysctl.conf
          /etc/init.d/procps restart

          # Start local services after hardware detection
          SERVICES="apache2 ajaxterm"

          for i in $SERVICES; do
          [ -x /etc/init.d/"$i" ] && /etc/init.d/"$i" start >/dev/null 2>&1
          done

          exit 0


          That will fix and enable ip_forwarding for you and will persist across reboots (if you've installed WANem to the harddrive of the VM with 0wn






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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%2fsuperuser.com%2fquestions%2f927228%2fwanem-to-route-between-machines%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            A bit late to the show here, but as there have been no new releases of WANem since this was posted, it's relevant.



            There was actually a Debian Squeeze bug that was present in the version of knoppix that WANem 3.0 was based on that complicates this a bit.



            The solution is to add the setting net.ipv4.ip_forward = 1 to /etc/sysctl.conf (because in Debian Squeeze, the /etc/network/options was deprecated).



            This is only part of the solution though, due to the bug. Debian Squeeze executed /etc/init.d/procps (which applies the settings in sysctl configuration) before the modules for networking were loaded, thus they were ignored by the modules. To work around this, you need to restart the /etc/init.d/procps service in /etc/rc.local. Full credit for this workaround goes to this post by Vladislav Kononenko



            The linked issue was based on a system that had an empty rc.local file, so use this example instead, as WANem has necessary logic in rc.local for it's startup.



            rc.local



            #!/bin/bash
            #
            # rc.local
            #
            # Load kernel variables from /etc/sysctl.d and /etc/sysctl.conf
            /etc/init.d/procps restart

            # Start local services after hardware detection
            SERVICES="apache2 ajaxterm"

            for i in $SERVICES; do
            [ -x /etc/init.d/"$i" ] && /etc/init.d/"$i" start >/dev/null 2>&1
            done

            exit 0


            That will fix and enable ip_forwarding for you and will persist across reboots (if you've installed WANem to the harddrive of the VM with 0wn






            share|improve this answer




























              0














              A bit late to the show here, but as there have been no new releases of WANem since this was posted, it's relevant.



              There was actually a Debian Squeeze bug that was present in the version of knoppix that WANem 3.0 was based on that complicates this a bit.



              The solution is to add the setting net.ipv4.ip_forward = 1 to /etc/sysctl.conf (because in Debian Squeeze, the /etc/network/options was deprecated).



              This is only part of the solution though, due to the bug. Debian Squeeze executed /etc/init.d/procps (which applies the settings in sysctl configuration) before the modules for networking were loaded, thus they were ignored by the modules. To work around this, you need to restart the /etc/init.d/procps service in /etc/rc.local. Full credit for this workaround goes to this post by Vladislav Kononenko



              The linked issue was based on a system that had an empty rc.local file, so use this example instead, as WANem has necessary logic in rc.local for it's startup.



              rc.local



              #!/bin/bash
              #
              # rc.local
              #
              # Load kernel variables from /etc/sysctl.d and /etc/sysctl.conf
              /etc/init.d/procps restart

              # Start local services after hardware detection
              SERVICES="apache2 ajaxterm"

              for i in $SERVICES; do
              [ -x /etc/init.d/"$i" ] && /etc/init.d/"$i" start >/dev/null 2>&1
              done

              exit 0


              That will fix and enable ip_forwarding for you and will persist across reboots (if you've installed WANem to the harddrive of the VM with 0wn






              share|improve this answer


























                0












                0








                0







                A bit late to the show here, but as there have been no new releases of WANem since this was posted, it's relevant.



                There was actually a Debian Squeeze bug that was present in the version of knoppix that WANem 3.0 was based on that complicates this a bit.



                The solution is to add the setting net.ipv4.ip_forward = 1 to /etc/sysctl.conf (because in Debian Squeeze, the /etc/network/options was deprecated).



                This is only part of the solution though, due to the bug. Debian Squeeze executed /etc/init.d/procps (which applies the settings in sysctl configuration) before the modules for networking were loaded, thus they were ignored by the modules. To work around this, you need to restart the /etc/init.d/procps service in /etc/rc.local. Full credit for this workaround goes to this post by Vladislav Kononenko



                The linked issue was based on a system that had an empty rc.local file, so use this example instead, as WANem has necessary logic in rc.local for it's startup.



                rc.local



                #!/bin/bash
                #
                # rc.local
                #
                # Load kernel variables from /etc/sysctl.d and /etc/sysctl.conf
                /etc/init.d/procps restart

                # Start local services after hardware detection
                SERVICES="apache2 ajaxterm"

                for i in $SERVICES; do
                [ -x /etc/init.d/"$i" ] && /etc/init.d/"$i" start >/dev/null 2>&1
                done

                exit 0


                That will fix and enable ip_forwarding for you and will persist across reboots (if you've installed WANem to the harddrive of the VM with 0wn






                share|improve this answer













                A bit late to the show here, but as there have been no new releases of WANem since this was posted, it's relevant.



                There was actually a Debian Squeeze bug that was present in the version of knoppix that WANem 3.0 was based on that complicates this a bit.



                The solution is to add the setting net.ipv4.ip_forward = 1 to /etc/sysctl.conf (because in Debian Squeeze, the /etc/network/options was deprecated).



                This is only part of the solution though, due to the bug. Debian Squeeze executed /etc/init.d/procps (which applies the settings in sysctl configuration) before the modules for networking were loaded, thus they were ignored by the modules. To work around this, you need to restart the /etc/init.d/procps service in /etc/rc.local. Full credit for this workaround goes to this post by Vladislav Kononenko



                The linked issue was based on a system that had an empty rc.local file, so use this example instead, as WANem has necessary logic in rc.local for it's startup.



                rc.local



                #!/bin/bash
                #
                # rc.local
                #
                # Load kernel variables from /etc/sysctl.d and /etc/sysctl.conf
                /etc/init.d/procps restart

                # Start local services after hardware detection
                SERVICES="apache2 ajaxterm"

                for i in $SERVICES; do
                [ -x /etc/init.d/"$i" ] && /etc/init.d/"$i" start >/dev/null 2>&1
                done

                exit 0


                That will fix and enable ip_forwarding for you and will persist across reboots (if you've installed WANem to the harddrive of the VM with 0wn







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 17 at 22:06









                RouthinatorRouthinator

                514




                514






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f927228%2fwanem-to-route-between-machines%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

                    flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                    Mangá

                    Eduardo VII do Reino Unido