How to make OpenWRT work properly in GNS3












1















No matter what I try in GNS3 to get OpenWRT to run properly, I cannot get it to properly work with other GNS components. I can connect two devices through a switch and ping back and forth, but not to the OpenWRT device, not matter what.



When I ping OWRT an ARP request can be seen, but no reply is sent. When I ping from OWRT to a device, a requests and replies can be seen, but OWRT does not register the correct Mac-Address. It is filled with all 0s instead of the actual address that was replied.



I've tried an OWRT Docker container running on the GNS3 VMWare server, VMWare VM running a GNS3-controlled instance and a VirtualBox GNS3-controlled instance. All show exactly the same behaviour and I cannot seem to find any tutorials on how to make it work... none that actually work anyway.



Running on MacOS Mojave.
VMWare Fusion 10.










share|improve this question


















  • 2





    OpenWRT is meant for wireless routers and therefore has bridge interfaces setup--though not 100% if this is true of x86 build if you are using that. Weird things can happen here. Try disabling all bridges (use shell) and ensure you are using the physical eth0 interfaces.

    – LawrenceC
    Feb 15 at 15:50











  • I would love to see if someone answers this. I have experienced this and other bizarre bugs in GNS3 with OpenWrt. What version image are you using?

    – Tim_Stewart
    Feb 15 at 18:51






  • 1





    @LawrenceC Your comment did the trick. If you will post it as an answer, I will credit you with answering the question. What can be done is 1 - to add additional ports and use those and leave eth0 alone. Or 2 - comment out anything for eth0 / lan where it says type 'bridge' and proto 'static' (don't know if the proto needed to be commented out, but it worked for me) and reboot

    – Chris V
    Feb 16 at 9:07













  • Actually, I wasn't able to connect anything to the internet via eth0 or eth1. If you just stick with adding new ports and working with those, so far all is ok. Although I haven't tested that much yet

    – Chris V
    Feb 16 at 10:44
















1















No matter what I try in GNS3 to get OpenWRT to run properly, I cannot get it to properly work with other GNS components. I can connect two devices through a switch and ping back and forth, but not to the OpenWRT device, not matter what.



When I ping OWRT an ARP request can be seen, but no reply is sent. When I ping from OWRT to a device, a requests and replies can be seen, but OWRT does not register the correct Mac-Address. It is filled with all 0s instead of the actual address that was replied.



I've tried an OWRT Docker container running on the GNS3 VMWare server, VMWare VM running a GNS3-controlled instance and a VirtualBox GNS3-controlled instance. All show exactly the same behaviour and I cannot seem to find any tutorials on how to make it work... none that actually work anyway.



Running on MacOS Mojave.
VMWare Fusion 10.










share|improve this question


















  • 2





    OpenWRT is meant for wireless routers and therefore has bridge interfaces setup--though not 100% if this is true of x86 build if you are using that. Weird things can happen here. Try disabling all bridges (use shell) and ensure you are using the physical eth0 interfaces.

    – LawrenceC
    Feb 15 at 15:50











  • I would love to see if someone answers this. I have experienced this and other bizarre bugs in GNS3 with OpenWrt. What version image are you using?

    – Tim_Stewart
    Feb 15 at 18:51






  • 1





    @LawrenceC Your comment did the trick. If you will post it as an answer, I will credit you with answering the question. What can be done is 1 - to add additional ports and use those and leave eth0 alone. Or 2 - comment out anything for eth0 / lan where it says type 'bridge' and proto 'static' (don't know if the proto needed to be commented out, but it worked for me) and reboot

    – Chris V
    Feb 16 at 9:07













  • Actually, I wasn't able to connect anything to the internet via eth0 or eth1. If you just stick with adding new ports and working with those, so far all is ok. Although I haven't tested that much yet

    – Chris V
    Feb 16 at 10:44














1












1








1


1






No matter what I try in GNS3 to get OpenWRT to run properly, I cannot get it to properly work with other GNS components. I can connect two devices through a switch and ping back and forth, but not to the OpenWRT device, not matter what.



When I ping OWRT an ARP request can be seen, but no reply is sent. When I ping from OWRT to a device, a requests and replies can be seen, but OWRT does not register the correct Mac-Address. It is filled with all 0s instead of the actual address that was replied.



I've tried an OWRT Docker container running on the GNS3 VMWare server, VMWare VM running a GNS3-controlled instance and a VirtualBox GNS3-controlled instance. All show exactly the same behaviour and I cannot seem to find any tutorials on how to make it work... none that actually work anyway.



Running on MacOS Mojave.
VMWare Fusion 10.










share|improve this question














No matter what I try in GNS3 to get OpenWRT to run properly, I cannot get it to properly work with other GNS components. I can connect two devices through a switch and ping back and forth, but not to the OpenWRT device, not matter what.



When I ping OWRT an ARP request can be seen, but no reply is sent. When I ping from OWRT to a device, a requests and replies can be seen, but OWRT does not register the correct Mac-Address. It is filled with all 0s instead of the actual address that was replied.



I've tried an OWRT Docker container running on the GNS3 VMWare server, VMWare VM running a GNS3-controlled instance and a VirtualBox GNS3-controlled instance. All show exactly the same behaviour and I cannot seem to find any tutorials on how to make it work... none that actually work anyway.



Running on MacOS Mojave.
VMWare Fusion 10.







linux networking openwrt arp






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 15 at 15:36









Chris VChris V

1061




1061








  • 2





    OpenWRT is meant for wireless routers and therefore has bridge interfaces setup--though not 100% if this is true of x86 build if you are using that. Weird things can happen here. Try disabling all bridges (use shell) and ensure you are using the physical eth0 interfaces.

    – LawrenceC
    Feb 15 at 15:50











  • I would love to see if someone answers this. I have experienced this and other bizarre bugs in GNS3 with OpenWrt. What version image are you using?

    – Tim_Stewart
    Feb 15 at 18:51






  • 1





    @LawrenceC Your comment did the trick. If you will post it as an answer, I will credit you with answering the question. What can be done is 1 - to add additional ports and use those and leave eth0 alone. Or 2 - comment out anything for eth0 / lan where it says type 'bridge' and proto 'static' (don't know if the proto needed to be commented out, but it worked for me) and reboot

    – Chris V
    Feb 16 at 9:07













  • Actually, I wasn't able to connect anything to the internet via eth0 or eth1. If you just stick with adding new ports and working with those, so far all is ok. Although I haven't tested that much yet

    – Chris V
    Feb 16 at 10:44














  • 2





    OpenWRT is meant for wireless routers and therefore has bridge interfaces setup--though not 100% if this is true of x86 build if you are using that. Weird things can happen here. Try disabling all bridges (use shell) and ensure you are using the physical eth0 interfaces.

    – LawrenceC
    Feb 15 at 15:50











  • I would love to see if someone answers this. I have experienced this and other bizarre bugs in GNS3 with OpenWrt. What version image are you using?

    – Tim_Stewart
    Feb 15 at 18:51






  • 1





    @LawrenceC Your comment did the trick. If you will post it as an answer, I will credit you with answering the question. What can be done is 1 - to add additional ports and use those and leave eth0 alone. Or 2 - comment out anything for eth0 / lan where it says type 'bridge' and proto 'static' (don't know if the proto needed to be commented out, but it worked for me) and reboot

    – Chris V
    Feb 16 at 9:07













  • Actually, I wasn't able to connect anything to the internet via eth0 or eth1. If you just stick with adding new ports and working with those, so far all is ok. Although I haven't tested that much yet

    – Chris V
    Feb 16 at 10:44








2




2





OpenWRT is meant for wireless routers and therefore has bridge interfaces setup--though not 100% if this is true of x86 build if you are using that. Weird things can happen here. Try disabling all bridges (use shell) and ensure you are using the physical eth0 interfaces.

– LawrenceC
Feb 15 at 15:50





OpenWRT is meant for wireless routers and therefore has bridge interfaces setup--though not 100% if this is true of x86 build if you are using that. Weird things can happen here. Try disabling all bridges (use shell) and ensure you are using the physical eth0 interfaces.

– LawrenceC
Feb 15 at 15:50













I would love to see if someone answers this. I have experienced this and other bizarre bugs in GNS3 with OpenWrt. What version image are you using?

– Tim_Stewart
Feb 15 at 18:51





I would love to see if someone answers this. I have experienced this and other bizarre bugs in GNS3 with OpenWrt. What version image are you using?

– Tim_Stewart
Feb 15 at 18:51




1




1





@LawrenceC Your comment did the trick. If you will post it as an answer, I will credit you with answering the question. What can be done is 1 - to add additional ports and use those and leave eth0 alone. Or 2 - comment out anything for eth0 / lan where it says type 'bridge' and proto 'static' (don't know if the proto needed to be commented out, but it worked for me) and reboot

– Chris V
Feb 16 at 9:07







@LawrenceC Your comment did the trick. If you will post it as an answer, I will credit you with answering the question. What can be done is 1 - to add additional ports and use those and leave eth0 alone. Or 2 - comment out anything for eth0 / lan where it says type 'bridge' and proto 'static' (don't know if the proto needed to be commented out, but it worked for me) and reboot

– Chris V
Feb 16 at 9:07















Actually, I wasn't able to connect anything to the internet via eth0 or eth1. If you just stick with adding new ports and working with those, so far all is ok. Although I haven't tested that much yet

– Chris V
Feb 16 at 10:44





Actually, I wasn't able to connect anything to the internet via eth0 or eth1. If you just stick with adding new ports and working with those, so far all is ok. Although I haven't tested that much yet

– Chris V
Feb 16 at 10:44










0






active

oldest

votes












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%2f1406137%2fhow-to-make-openwrt-work-properly-in-gns3%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















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%2f1406137%2fhow-to-make-openwrt-work-properly-in-gns3%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

Mouse cursor on multiple screens with different PPI

Agildo Ribeiro

Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”