Reddit Feeds

Sign up and stay connected to your favorite communities.

sign uplog in

GNS3 safe on corporate network?

I've decided to move on from Packet Tracer into GNS3. So far I've got IOSv installed on the GNS3 VM (sorry, I'm not sure if that sentence makes any sense; I'm new to VM's, which is why I'm worried about this issue).

Every now and then I get a bit of free time at work to poke around, and I just wanted to make sure GNS3 was 100% isolated from the real network. I see I now have two virtual NICs, which is also new to me.

Is there any possible way for GNS3 to bleed into a real network?

100% Upvoted
What are your thoughts? Log in or Sign uplog insign up

First off, get explicit permission from your boss to put a VM on work infrastructure.

Second, usually when you configure a VM you have to setup a physical NIC to work with the VM. Generally you have a physical NIC connect to a virtual switch and apply a virtual NIC to the VM and the hyperviser handles conversion between the virtual network and the physical one. This all depends on how your virtual machines and hypervisers are configured.

Third, get explicit permission from your boss to put a VM on work infrastructure. GNS3 can get resource hungry, especially RAM, and interfere with how production systems work.

Original Poster2 points·5 days ago

Thanks, I'm glad I asked. I guess I'll have to stick to whatever I can do on Packet Tracer while I'm at work.

...or maybe do some work while I'm at work.

Not only should you ask if it is authorized to use but you must also be aware that any IOS that is used in a production environment must be properly licensed. If you acquired the IOSv image via a valid support contract, there should not be an issue with its use. However, if you obtained the image in other way, this could be a violation of the TOS and you, and your organization, could face potential fines.

Original Poster1 point·5 days ago

I did. I purchased VIRL for this purpose. At this point I probably should have just bought the hardware, but I just don't have the space in my house for it.

Original Poster1 point·5 days ago

This is out of scope here, but for my curiosity's sake, is the physical nic involved here so it can process layer 1 and 2 stuff for the VM, rather than having to emulate that in software?

I think now that I've gotten myself started on this track I might as well go home and learn a thing or two about virtualization. I hear it's all the rage these days.

CCENT1 point·5 days ago

No, it's so you can communicate with the VM.

This depends on the networking settings of the virtual machine. Which virtualization software are you using?

It is possible to give a VM privileges to use the physical NIC of the machine that is hosting the VM (such a machine is referred to as a hypervisor) .
However, this is not a default setting.

You should definitely learn about virtualization, if only the high-level contrasts. You will have to make design and configuration choices and respect virtualization technology as you advance.

E.g. before virtualization, every server got an access port configured for connectivity, and that was fine. Trunks were only used between switches and between switches and routers.

Since virtualization, you'll end up configuring server facing interfaces as trunks with a bunch of VLANS allowed.

It will only interface with a real network if you configure it to.

gns needs to be specifically configured to talk to live networks that tie to live interfaces, out the box it doesnt just like PT.

Community Details





Create Post

r/ccna Rules

No posting of illegal materials
No posting of braindumps
Be courteous and helpful
Don't ask others to complete your labs