Jeremy,
As per your request on GitHub, I'm in the middle of implementing a Fortigate appliance for a client and having never worked with the device before, I'm attempting to simulate its operation. Now, I've managed to get it all working, but it appears to cause a lot of clutter in my topology.
In the image below, each interface on the Fortigate VM requires its own cloud device. This works as expected barring the clutter!
Attachment:
File comment: Multiple cloud devices simulating an interface on the Fortigate appliance! For this instance, I'm only using 4 interfaces on the Fortigate to simulate 4 VLANs.
fortigate-experiment-multi-cloud.gns3- — GNS3_009.png [ 123.37 KiB | Viewed 6334 times ]
In the image below, it only works for the first link I attach to the cloud device. So, if I attach interface 1 to the IOU device first followed by the others, only traffic for VLAN1 will flow. If I attach interface 2 to the IOU device first followed by the others, only traffic for VLAN2 will flow and so on and so forth, yadi yada...
Attachment:
File comment: Single cloud device with 4 vmnet host-only interfaces configured that attach to 4 interfaces on the Fortigate appliance to simulate 4 VLANs.
fortigate-experiment-single-cloud.gns3- — GNS3_007.png [ 127.58 KiB | Viewed 6334 times ]
My enhancement request was to enable a single cloud to be used thereby reducing clutter.
During my attempts to declutter my topology, I also tried adding a nio_gen_linux interface but the following error appeared on the console where I launched gns3:
Code:
[I 140628 19:01:32 base:213] ZeroMQ client (iou) sending JSON-RPC custom error: Requested NIO does not exist or is not supported: nio_linux_ethernet for call id b41cf442-c346-446f-b2e1-7981174ff761
[E 140628 19:01:32 iou_device:425] error while adding an UDP NIO for IOU1: Requested NIO does not exist or is not supported: nio_linux_ethernet
Cheers,
ak.
Edit: Here's the link on Github:
https://github.com/GNS3/gns3-gui/issues/67
Login
FAQ
Search
