Using iptables to Bridge Network Interfaces

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












1















I three devices connected like so;



pictured configuration.



  • Device A runs Windows.

  • Devices B and C run Linux

I want device A to be able to connect with device C and vice versa. Device B does not need to anything but bridge the connection between the two interfaces.
All of the IP's are static. I have implimented the following iptables solution, however, this solution only allows for connections originating with Device C due to the nature of the masquerade. I can currently ping from device C to device A. But from device A I cannot ping any of the IP addresses on the eth0 interface



I would like to be able to ping both ways from A -> C and from C -> A.



The following code runs on Device B.



 sysctl -w net.ipv4.ip_forward=1
iptables -A FORWARD -i sn0 -o usb0 -j ACCEPT
iptables -A FORWARD -i usb0 -o sn0 -j ACCEPT
iptables -t nat -A POSTROUTING -o usb0 -j MASQUERADE









share|improve this question













migrated from stackoverflow.com Aug 11 '16 at 12:00


This question came from our site for professional and enthusiast programmers.


















  • Please note that Stackoverflow is for programming related questions only. Please review the help center for what topics can be asked here. This question may be appropriate on other SE sites such as Unix & Linux or superuser. Check their help first to see if the question belongs there and if so you can click the "flag" link to request migration there.

    – kaylum
    Jul 29 '16 at 3:26















1















I three devices connected like so;



pictured configuration.



  • Device A runs Windows.

  • Devices B and C run Linux

I want device A to be able to connect with device C and vice versa. Device B does not need to anything but bridge the connection between the two interfaces.
All of the IP's are static. I have implimented the following iptables solution, however, this solution only allows for connections originating with Device C due to the nature of the masquerade. I can currently ping from device C to device A. But from device A I cannot ping any of the IP addresses on the eth0 interface



I would like to be able to ping both ways from A -> C and from C -> A.



The following code runs on Device B.



 sysctl -w net.ipv4.ip_forward=1
iptables -A FORWARD -i sn0 -o usb0 -j ACCEPT
iptables -A FORWARD -i usb0 -o sn0 -j ACCEPT
iptables -t nat -A POSTROUTING -o usb0 -j MASQUERADE









share|improve this question













migrated from stackoverflow.com Aug 11 '16 at 12:00


This question came from our site for professional and enthusiast programmers.


















  • Please note that Stackoverflow is for programming related questions only. Please review the help center for what topics can be asked here. This question may be appropriate on other SE sites such as Unix & Linux or superuser. Check their help first to see if the question belongs there and if so you can click the "flag" link to request migration there.

    – kaylum
    Jul 29 '16 at 3:26













1












1








1








I three devices connected like so;



pictured configuration.



  • Device A runs Windows.

  • Devices B and C run Linux

I want device A to be able to connect with device C and vice versa. Device B does not need to anything but bridge the connection between the two interfaces.
All of the IP's are static. I have implimented the following iptables solution, however, this solution only allows for connections originating with Device C due to the nature of the masquerade. I can currently ping from device C to device A. But from device A I cannot ping any of the IP addresses on the eth0 interface



I would like to be able to ping both ways from A -> C and from C -> A.



The following code runs on Device B.



 sysctl -w net.ipv4.ip_forward=1
iptables -A FORWARD -i sn0 -o usb0 -j ACCEPT
iptables -A FORWARD -i usb0 -o sn0 -j ACCEPT
iptables -t nat -A POSTROUTING -o usb0 -j MASQUERADE









share|improve this question














I three devices connected like so;



pictured configuration.



  • Device A runs Windows.

  • Devices B and C run Linux

I want device A to be able to connect with device C and vice versa. Device B does not need to anything but bridge the connection between the two interfaces.
All of the IP's are static. I have implimented the following iptables solution, however, this solution only allows for connections originating with Device C due to the nature of the masquerade. I can currently ping from device C to device A. But from device A I cannot ping any of the IP addresses on the eth0 interface



I would like to be able to ping both ways from A -> C and from C -> A.



The following code runs on Device B.



 sysctl -w net.ipv4.ip_forward=1
iptables -A FORWARD -i sn0 -o usb0 -j ACCEPT
iptables -A FORWARD -i usb0 -o sn0 -j ACCEPT
iptables -t nat -A POSTROUTING -o usb0 -j MASQUERADE






linux networking iptables






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jul 29 '16 at 2:10









Chris PugliaChris Puglia

62




62




migrated from stackoverflow.com Aug 11 '16 at 12:00


This question came from our site for professional and enthusiast programmers.









migrated from stackoverflow.com Aug 11 '16 at 12:00


This question came from our site for professional and enthusiast programmers.














  • Please note that Stackoverflow is for programming related questions only. Please review the help center for what topics can be asked here. This question may be appropriate on other SE sites such as Unix & Linux or superuser. Check their help first to see if the question belongs there and if so you can click the "flag" link to request migration there.

    – kaylum
    Jul 29 '16 at 3:26

















  • Please note that Stackoverflow is for programming related questions only. Please review the help center for what topics can be asked here. This question may be appropriate on other SE sites such as Unix & Linux or superuser. Check their help first to see if the question belongs there and if so you can click the "flag" link to request migration there.

    – kaylum
    Jul 29 '16 at 3:26
















Please note that Stackoverflow is for programming related questions only. Please review the help center for what topics can be asked here. This question may be appropriate on other SE sites such as Unix & Linux or superuser. Check their help first to see if the question belongs there and if so you can click the "flag" link to request migration there.

– kaylum
Jul 29 '16 at 3:26





Please note that Stackoverflow is for programming related questions only. Please review the help center for what topics can be asked here. This question may be appropriate on other SE sites such as Unix & Linux or superuser. Check their help first to see if the question belongs there and if so you can click the "flag" link to request migration there.

– kaylum
Jul 29 '16 at 3:26










1 Answer
1






active

oldest

votes


















0














iptables isn't used for this sort of functionality, you will get more success creating a network bridging interface on the middle B device.



The Arch wiki has a good guide to setting one up (the guide will apply to most other Linux distros, not just Arch), at this link






share|improve this answer






















    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "106"
    ;
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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%2funix.stackexchange.com%2fquestions%2f302764%2fusing-iptables-to-bridge-network-interfaces%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














    iptables isn't used for this sort of functionality, you will get more success creating a network bridging interface on the middle B device.



    The Arch wiki has a good guide to setting one up (the guide will apply to most other Linux distros, not just Arch), at this link






    share|improve this answer



























      0














      iptables isn't used for this sort of functionality, you will get more success creating a network bridging interface on the middle B device.



      The Arch wiki has a good guide to setting one up (the guide will apply to most other Linux distros, not just Arch), at this link






      share|improve this answer

























        0












        0








        0







        iptables isn't used for this sort of functionality, you will get more success creating a network bridging interface on the middle B device.



        The Arch wiki has a good guide to setting one up (the guide will apply to most other Linux distros, not just Arch), at this link






        share|improve this answer













        iptables isn't used for this sort of functionality, you will get more success creating a network bridging interface on the middle B device.



        The Arch wiki has a good guide to setting one up (the guide will apply to most other Linux distros, not just Arch), at this link







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 11 '16 at 18:42









        einonmeinonm

        1,234521




        1,234521



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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%2funix.stackexchange.com%2fquestions%2f302764%2fusing-iptables-to-bridge-network-interfaces%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 check contact read email or not when send email to Individual?

            Bahrain

            Postfix configuration issue with fips on centos 7; mailgun relay