I am running an application on my Mac called Dynagen/Dynamips that emulates Cisco routers. This application has the ability to connect the Virtual router to a real ethernet interface in order to connect to physical devices.
I am able to connect to the physical Ethernet on my Mac by configuring a Dynamips text .net file with the following configuration statements;
[[ROUTER r1]]
model = 3660
f0/0 = S1 1
[[ethsw S1]]
1 = access 1 NIO_gen_eth:en0
this means that;
RouterR1, Fastethernet0/0 is connected to switch S1 port1
Switch S1 is connected to NIO_gen_eth:en0
This works ok; the vitual router is bridged to the physical ethernet adaptor on my MAC, and can access the ethernet network.
-//-
However, I want to use VMware to run Unified Communications applications such as Cisco Unified Call Manager, and IP Blue Softphone, and I want to connect these to the virtual routers emulated in Dynamips/Dynagen. But I do not seem to be able to bridge the virtual router to the VMware virtual network interface.
I configure the VM to use host only networking (and it gets an ip from the vmnet1 ip address range)
I configure the Dynagen .net file like this;
[[ROUTER r1]]
model = 3660
f0/0 = S1 1
[[ethsw S1]]
1 = access 1 NIO_gen_eth:vmnet1
But the Dynagen application on my Mac does not seem to be able to connect to the vmnet1 virtual network interface; I get this error;
*** Warning: Connecting S1 port 1 to access 1 NIO_gen_eth:vmnet1 resulted in:
206-unable to create generic ethernet NIO
Is this a VMware issue with the way host only virtual networks are implemented? Is there any way around it?
VMware Fusion version is Version 2.0.1 (128865)
I have also submitted a query to the dynamips/dynagen boards, but have not receieved an answer yet. http://7200emu.hacki.at/viewtopic.php?p=26747#26747
I am having the exact same issue on my Mac.
I have tried running GNS as root as many people have found this resolved their issues, but this does not work. Still cannot add vmnet1.
This application has the ability to connect the Virtual router to a real ethernet interface in order to connect to physical devices.
vmnet1 is a Virtual Ethernet Adapter not a Physical Ethernet Adapter and if the Dynagen/Dynamips application that emulates Cisco routers is designed to connect to Physical Ethernet Adapter then there's your answer.
The vmnet1 interface shows up under ifconfig -a, so I doubt there is a difference between physiucal and virtual as my Mac sees both.
I also have exactly the same problem trying to connect GNS/dynamips to a physical interface.
The vmnet1 interface shows up under ifconfig -a, so I doubt there is a difference between physiucal and virtual as my Mac sees both.
First of all I have not looked at the System Requirements for the software the OP is using however the OP stated "This application has the ability to connect the Virtual router to a real Ethernet interface in order to connect to physical devices." and I take the operative word "real" to mean "physical" vs "virtual" and there is a difference! Also just because it shows under ifconfig doesn't mean a thing if the requirements are for a physical network adapter and while at the moment I can't recall the last time I ran into this issue I do recall that because VMware VMnet's are Virtual not Physical I was unable to do what I was attempting to do with the virtual adapters yet had no issue using the physical adapters so it can make a difference. I don't have time to look into the software the OP is using however the intent of my original reply was for the OP to validate that the software can work with virtulaized adapters and if yes what type or requirements are necessary.
Note: I have also read different posts over the last couple of years where because Parallels Virtual Ethernet Adapters actually show up in the Hardware Tree that some things where possible with them that weren't with VMware's Virtual Ethernet Adapters because of the limitations of VMware's Virtual Ethernet Adapters not showing in the Hardware Tree.
Anyway it is something for the OP to check as it can be an issue if the software is requiring a physical adapter or might work with one like how Parallels virtualizes it vs how VMware does.
Seems to work for others:
Like I already said I didn't look at the System Requirements of the Software the OP is using and was suggesting that if binding to a physical adapter was required as the OP had stated then it may be an issue, I never said it couldn't be done!!!
Looking at the format of the OP's configuration and the configuration in the link you provided it may be the the OP's configuration is not formated correctly however before you respond again let me state that aside from reading this thread that the thread you linked I haven't looked at anything else regarding this issue and am not nor was I trying to provide specific or detail support for the OP's issue as I just don't have the time at the moment to offer anymore then what I have which admittedly isn't much but certainly starting with validating System Requirements is a good logical place to start. Also I was not nor am I attempting to address your issue as my original reply was to the OP not you, however hopefully the OP will get something from the link you provided and you will also find resolution for your issue too.
