Added appliance definitions for various Mikrotik hardware models simulated through the use of the Mikrotik CHR platform.

[AzorianMatt]

I have created 10 Mikrotik appliances based on the CHR image that will simulate various router and switch models as it pertains to CPU count, RAM, and network interfaces.

Unfortunately, CHR does not pickup these interface names so one must manually update the interface names in the OS after first run. This is because CHR is designed to give standard naming to it's virtual Ethernet interfaces.

If I knew how to create a standard image from their other models then I could script a method for building them from the NPK formatted updates. In that scenario, QEMU emulation could be leveraged to create a more accurate simulation of the hardware.

---

When updating an existing appliance:

• [ ] The new version is on top.
• [ ] The filenames in the "images" section are unique, to avoid appliances / version overwriting each other.

• [ ] If you forked the repo, running check.py doesn't drop any errors for the updated file.

  When creating a new appliance:

• It's tested locally, i.e.
  • [x] You dragged an instance into a project on your box, got it installed (if necessary), and did some basic network checks (ping, UI reachable, etc.).
  • [X] GNS3 VM can run it without any tweaks.
  • [X] The device is in the right category: router, switch, guest (hosts), firewall
  • [X] You filled in as much info as possible (checks the schemas and other appliance files for some guidance).
• [ ] When adding a container: it builds on Docker Hub and can be pulled.
• [X] The filenames in the "images" section are unique (to avoid appliances and/or versions overwriting each other).
• [X] If you forked the repo, running check.py doesn't drop any errors for the new file.
• [ ] Optional: a symbol has been created for the new appliance.

[AzorianMatt]

@grossmj you're welcome and my apologies for wasting your time on something so obvious! I'll get some fixes pushed today for this. I'm testing a method with the x86 image to see if it's a more suitable fit for a few of these.

Thanks for the fast feedback!

[grossmj]

@grossmj you're welcome and my apologies for wasting your time on something so obvious!

No worries at all.

Just one last note, the following appliances can be downgraded to registry version 5 because they don't use custom adapters: https://github.com/GNS3/gns3-registry#versioning

• mikrotik-rb1100ahx4-dude-edition.gns3a
• mikrotik-rb450gx4.gns3a
• mikrotik-rb450g.gns3a

Thanks! :)

[AzorianMatt]

All handled, thanks @grossmj!