a journal of interesting technical ideas . . . a journal of interesting technical ideas . . .
This is a long post, but most of it is file contents. Keep reading!
GNS3 appliance files are descriptions of virtual machines used in network simulations. The appliance files have suffixes of .gns3a and are included with the GNS3 download. You can update the files and create new ones. The goal of this article is to walk through the process of working with appliance files and contributing them back to the community.
On a personal note, submitting a new GNS3 appliance was the first time I contributed to an open-source project. I’m still learning, but a few years ago I knew nothing. Jeremy Grossman, with GNS3, was patient and helped me understand the process of using Git. Contributing - even in this minor way - was a real high for me and I’d love for you to be able to share that feeling and contribute to this and other projects. GNS3a was my “gateway drug” into being a contributor and not just a consumer of open source.
One of the files I’ve contributed is the Security Onion appliance. Security Onion is a Linux distribution that focuses on security tools. Below is the current version (9/1/20) of the GNS3A file. Before we create a new appliance, let’s update this one.
Overview
What’s included
Why this setup appeals
Strengths
Weaknesses and risks
Practical tips
Who should consider this
Who should avoid it
Bottom line The MHH AUTO VMware package of Diagbox 7.02–7.57 is a highly convenient, practical solution for getting Diagbox running quickly across multiple versions. It shines for testing, training, and occasional diagnostics, provided you accept the legal and security caveats and take precautions (scans, snapshots, verified adapters). For mission-critical or commercial work where full vendor support and compliance matter, invest in properly licensed, vendor-supported installations instead.
Version 7.57 is a significant leap forward. It bridges the gap to support newer hardware and protocols (like CAN FD in some newer models). Why 7.57 specifically?
The Problem: Native 7.57 installed on a physical Windows 7 or 10 machine often has severe security checks. It tries to "brick" cloned interfaces by corrupting the VCI firmware. This is why the community uses VMware.
For those unfamiliar, MHH AUTO (mhhauto.com) is the largest online forum dedicated to automotive diagnostics, coding, and modification. It is the digital library of Alexandria for mechanics.
When you search for "Diagbox 7.02 -plus 7.57- VMWARE" and see "MHH AUTO - Page 1", it means you have found the primary thread. Page 1 of that thread typically contains:
The search keyword "Diagbox 7.02 -plus 7.57- VMWARE - MHH AUTO - Page 1" is a precise, technical query. It tells us the user knows exactly what they want:
If you have followed this guide, you should now have a fully functional, virtualized Diagbox environment capable of handling almost any PSA vehicle from 2001 to 2018.
Remember: Always take a snapshot before updating. Always use a stable power supply. And always thank the uploaders on Page 1 of the MHH AUTO thread—they are the unsung heroes of the automotive diagnostic world.
Have you successfully used Diagbox 7.57 on VMware? Did you encounter the "VCI Not Recognized" error? Scroll back to Page 1 of the MHH AUTO forum for the latest patch, or leave a comment below.
The Diagbox 7.02 to 7.57 update, often used via , is a widely used diagnostic solution for Citroën and Peugeot vehicles, supporting offline telecoding and model coverage up to 2015
. Running this software in a virtual machine simplifies installation on modern 64-bit systems, providing a stable environment for dealer-level diagnostics using an XS Evolution Lexia-3 interface. For more details, visit Diagbox 7.57 на Windows 10 64bit - Drive2
Title: Exploring Diagbox 7.02 and 7.57 on VMWARE with MHH AUTO
Introduction:
In the world of automotive diagnostics, having the right tools and software is crucial for efficient and effective vehicle maintenance and repair. One such tool that has gained popularity among mechanics and automotive professionals is Diagbox, a comprehensive diagnostic software used for a wide range of vehicle systems. In this blog post, we'll delve into the specifics of using Diagbox versions 7.02 and 7.57 on a VMWARE virtual machine, along with the benefits of utilizing MHH AUTO.
What is Diagbox?
Diagbox is a powerful diagnostic software designed to interface with vehicle systems, allowing users to diagnose and troubleshoot issues, as well as perform advanced functions such as coding and configuration. With its user-friendly interface and extensive vehicle coverage, Diagbox has become a go-to tool for many automotive professionals.
VMWARE and Virtualization:
Virtualization technology, such as VMWARE, allows users to create a virtual machine (VM) on a single physical host, enabling multiple operating systems to run simultaneously. This provides a flexible and isolated environment for testing and running software, including Diagbox. By running Diagbox on a VMWARE virtual machine, users can ensure a stable and secure environment for diagnostic work.
MHH AUTO: A Valuable Resource
MHH AUTO is a renowned online platform providing automotive professionals with access to a vast library of diagnostic tools, software, and resources. By combining Diagbox with MHH AUTO, users can leverage a comprehensive suite of diagnostic capabilities, including advanced vehicle coverage, troubleshooting guides, and technical support.
Benefits of Using Diagbox 7.02 and 7.57 on VMWARE with MHH AUTO:
By utilizing Diagbox versions 7.02 and 7.57 on a VMWARE virtual machine with MHH AUTO, automotive professionals can enjoy numerous benefits, including:
Conclusion:
In conclusion, combining Diagbox 7.02 and 7.57 with VMWARE virtualization and MHH AUTO provides automotive professionals with a powerful diagnostic solution. By leveraging these tools and technologies, users can enhance their diagnostic capabilities, improve efficiency, and stay up-to-date with the latest vehicle systems and technologies. Whether you're a seasoned mechanic or an automotive enthusiast, exploring Diagbox and MHH AUTO is definitely worth considering.
The Diagbox 7.02 (plus 7.57) VMware image from MHH AUTO is highly regarded for its stability in offline telecoding on pre-2015 PSA vehicles, providing a stable, plug-and-play diagnostic solution. While praised for avoiding high costs of official subscriptions, users note that this version requires specific hardware and is best suited for older models rather than those post-2015. Read the full community discussion at MHH AUTO. Diagbox 7.02 (plus 7.57) VMWARE - MHH AUTO - Page 1 Diagbox 7.02 -plus 7.57- VMWARE - MHH AUTO - Page 1
Diagbox 7.02, updatable to version 7.57, serves as a stable, dealer-level diagnostic solution for Peugeot and Citroën vehicles, often implemented via VMware to bypass modern OS compatibility issues and activation hurdles. Commonly sourced through automotive forums like MHH Auto, these pre-configured virtual machines allow for reliable installation of the software, which is crucial for full diagnostics and programming. For comprehensive, pre-configured VM versions of this software, visit MHHAutoShop Diagbox V7.57 Installation Guide | PDF - Scribd
This specific thread on refers to a pre-configured VMware virtual machine containing Diagbox v7.02 , updated to
. This software is the dealer-level diagnostic tool used for Core Content Overview The content of "Page 1" typically includes the following: Software Version: Diagbox 7.02 base with updates applied up to 7.57. A VMware Workstation virtual machine image (
). This is popular because Diagbox is notoriously difficult to install on modern Windows 10/11 systems; the VM provides a stable, pre-installed Windows XP or Windows 7 32-bit environment. Key Features: Full dealer diagnostics, fault code reading, and clearing. Real-time data monitoring and component testing. ECU configuration and programming (telecoding). Requirements: Lexia 3 (XS Evolution) interface. VMware Player or Workstation. Minimum 4GB RAM and virtualization enabled in BIOS. Typical "Page 1" Layout on MHH AUTO The "Thanks + Rate" Requirement:
Like most MHH AUTO threads, the download links are usually hidden until you click the "Thanks" and "Rate" buttons. Installation Instructions: Download and extract the RAR parts. Open the virtual machine in VMware.
Select "I Moved It" when prompted (to keep the hardware ID intact).
Connect the Lexia interface via USB and ensure it is "connected to the VM."
Often, the archive password is provided in the post or requires a Private Message (PM) to the uploader.
To access the actual files, you must have an active account on , which usually requires a small one-time registration fee. installation steps for this specific VM, or are you looking for newer versions of Diagbox?
Diagbox: This is likely referring to a diagnostic software tool used for vehicles. Diagnostic tools are crucial for identifying and troubleshooting issues in modern vehicles.
Versions 7.02 and 7.57: The mention of specific version numbers (7.02 and 7.57) could indicate that the reviewer is discussing updates, improvements, or compatibility issues between these versions of the Diagbox software.
VMWARE: This is a virtualization platform that allows users to run multiple operating systems on a single physical machine. The mention of VMWARE suggests that the reviewer might be using the Diagbox software in a virtualized environment, possibly to ensure compatibility with different operating systems or to isolate the diagnostic software from the host system.
MHH AUTO: This could be related to a community, a resource, or a specific tool used in conjunction with automotive diagnostics. MHH Auto might offer resources, forums, or software patches for automotive technicians.
Given the context, the review seems to be targeting users who are interested in or currently using Diagbox for automotive diagnostics, specifically those who might be looking to use it within a VMWARE environment and are seeking information or experiences related to versions 7.02 and 7.57.
If you're looking for information on how to use Diagbox in a VMWARE environment or details about its versions, here are some general steps you might consider:
You're looking for a guide on using Diagbox 7.02 and 7.57 with VMWARE, specifically with MHH AUTO. I'll provide a general outline of the steps, but please note that I'll be providing a condensed version, and you should consult the official documentation or forums for more detailed and up-to-date information.
Diagbox and VMWARE Overview
Prerequisites
Step-by-Step Guide
Additional Tips and Considerations
By following these general steps, you should be able to set up Diagbox 7.02 and 7.57 on a VMWARE virtual machine with MHH AUTO resources. If you encounter issues, refer to the official documentation and forums for more detailed assistance.
Understanding Diagbox 7.02 & 7.57 on VMware (MHH AUTO Solutions)
For PSA (Peugeot and Citroën) enthusiasts and mechanics, maintaining a reliable diagnostic environment is often a challenge due to operating system incompatibilities. One of the most popular solutions found on the automotive forum MHH AUTO involves using a pre-configured VMware virtual machine containing Diagbox 7.02 plus the 7.57 update.
This setup is widely discussed on "Page 1" of relevant forum threads as it provides a stable, "plug-and-play" environment for the Lexia 3 and PP2000 diagnostic tools. Why Use Diagbox in a VMware Virtual Machine?
The primary reason users turn to VMware for Diagbox 7.xx is compatibility. Modern versions of Windows (10 and 11) often struggle with the legacy drivers required for the Lexia 3 interface.
Legacy Support: Versions like 7.02 and 7.57 are essential for older Peugeot and Citroën models that may not be fully supported by newer "standalone" versions.
Isolation: Running the software in a virtual machine prevents it from conflicting with other programs on your main computer.
Ease of Setup: Instead of a complex multi-stage installation on your native OS, you can simply "open" the virtual machine file. Key Features of the 7.02 and 7.57 Combo
The Diagbox 7.02 base installation serves as the foundational platform, while the 7.57 update adds critical vehicle coverage and bug fixes.
Advanced Diagnostics: Provides deep access to ECU coding, fault clearing, and real-time data monitoring.
Lexia 3 / PP2000 Integration: Seamlessly switches between the Lexia interface (for Citroën) and Peugeot Planet 2000 (for Peugeot) depending on the vehicle connected.
Stable Versioning: While versions up to 7.83 exist, many users on MHH AUTO prefer 7.57 for its renowned stability and lower resource requirements. How to Install the VMware Image Review: Diagbox 7
Based on common guides found on technical forums and tutorials from Tools4Car, here is the general process:
Download VMware: Install a compatible version like VMware Workstation Player.
Extract the Files: Use a tool like 7-Zip to unpack the Diagbox VM image (often provided in multiple parts).
Open the Virtual Machine: Launch VMware and select "Open a Virtual Machine." Navigate to your extracted folder and select the .vmx file.
The "I Moved It" Step: When prompted, always select "I moved it" to ensure VMware retains the correct hardware IDs for the software's activation.
Connect Your Hardware: Plug your Lexia 3 interface into your USB port. In the VMware menu, go to Removable Devices and select "Connect (Disconnect from Host)" for the PSA USB device. Troubleshooting Tips from MHH AUTO
VCI Not Detected: Ensure you are using a "Full Chip" Lexia 3 interface for the best compatibility with version 7.57.
Network Settings: Some VM images require you to disable the internet connection within the virtual machine to prevent the software from attempting an unauthorized "auto-update".
Resolution: If the window is too small, you can adjust the screen resolution inside the Windows 7 environment of the VM or install VMware Tools for automatic scaling. Diagbox 7.02 -plus 7.57- Vmware - Mhh Auto - Page 1
Diagbox 7.02–7.57, often deployed via MHH Auto as a VMware image, provides essential diagnostic capabilities for Peugeot and Citroën vehicles, bridging compatibility between older, 16-bit software (Lexia/PP2000) and modern 64-bit operating systems. Utilizing a virtual machine avoids common installation errors, allowing users to run required updates, such as version 7.57, to support newer vehicle models. For more details, visit the MHH Auto forum thread: MHH Auto.
Diagbox 7.02 -plus 7.57- Vmware - Mhh Auto - Page 1 [verified]
This text appears to be a thread title from , a popular automotive forum used by technicians for sharing diagnostic software. Diagbox 7.02 - 7.57
: Refers to specific versions of the PSA (Peugeot/Citroën) diagnostic software. Version 7.57 is notable because it is one of the last versions where "Telecoding" (offline configuration) was fully cracked and accessible without an official PSA server subscription. : Indicates the software is provided as a pre-configured Virtual Machine
image. This allows users to run the older, sensitive software (which often requires Windows XP or 32-bit environments) on modern 64-bit operating systems without complex installation.
: A specialized automotive forum where members share "cracked" or modified diagnostic tools, firmware, and repair manuals.
Essentially, this is a resource for DIY mechanics or independent shops looking to perform deep-level diagnostics and programming on Peugeot or Citroën vehicles without paying for official manufacturer access. for Diagbox or information on the (like the Lexia 3 interface) required to use it? AI responses may include mistakes. Learn more i-MiEV and Lexia 3 and Diagbox | Page 2
This guide outlines the process for setting up a pre-configured Diagbox 7.02 to 7.57 VMware environment to facilitate diagnostics for Peugeot and Citroën vehicles. Key steps include ensuring BIOS virtualization is enabled, extracting the image, selecting "I moved it" upon launching the .vmx file in VMware, and connecting the Lexia interface via USB redirection. For detailed, user-reported installation instructions, see this YouTube video.
Diagbox 7.57 + Can Clip 213, pre-installed VMware version - tools4car
The forum thread "Diagbox 7.02 -plus 7.57- VMWARE - MHH AUTO - Page 1" provides crucial diagnostic software for Peugeot and Citroën vehicles, particularly for managing complex fault codes like the "Depollution System Fault." Users emphasize running the software within a VMWare environment to prevent damage to the host operating system's registry. You can explore the user discussions and file links at MHH Auto.
The search for Diagbox 7.02 plus 7.57 VMWARE via MHH AUTO refers to a popular community-driven solution for Citroën and Peugeot vehicle diagnostics. This specific version set is highly regarded on automotive forums for its stability and compatibility with older Lexia 3 interfaces. The Evolution of Diagbox 7.02 to 7.57
Version 7.02 Baseline: This is the core installation version. It provides the foundation for the Lexia (Citroën) and PP2000 (Peugeot) software, but it lacks support for many vehicles manufactured after 2012.
The 7.57 Milestone: Update 7.57 is widely considered the "sweet spot" for hobbyists and independent mechanics. It extends vehicle coverage up to late 2015 models while maintaining the ability to perform offline "telecoding" (configuration changes), which was restricted in later versions.
The VMware Solution: Because Diagbox 7.xx requires a specific environment (ideally Windows 7 32-bit) and can be difficult to install natively on modern Windows 10/11 machines, community members on MHH AUTO created pre-configured VMware Virtual Machine (VM) images. Key Benefits of the MHH AUTO Version
Plug-and-Play: Users download a single large file, open it in VMware Workstation, and select "I Moved It" to bypass activation issues.
Stability: Incremental updates (e.g., 7.44 to 7.49 to 7.57) are already applied, saving users hours of manual installation and potential errors.
Interface Compatibility: These versions are optimized to work with cloned "Full Chip" Lexia 3 VCIs (Vehicle Communication Interfaces). Installation Highlights from MHH AUTO Guides
Preparation: Download the VM image (often hosted on MEGA or Google Drive) and install the 7-Zip archive extractor. VM Setup: Open the .vmx file in VMware Workstation Player.
Hardware Connection: Connect the Lexia cable to your USB port and select "Connect to a Virtual Machine" so the guest OS can see the hardware.
Interface Check: Many MHH AUTO versions include a "PSA Interface Checker" on the desktop to verify the firmware version of your cable before launching the main software.
For further assistance, you can find active discussions and download links on the MHH AUTO Forums under the "Automotive Software" section. mhh auto forums.
Diagbox 7.02 -plus 7.57- VMWARE - MHH AUTO: A Comprehensive Guide
In the world of automotive diagnostics, having the right tools and software is essential for efficient and effective troubleshooting. One such tool that has gained popularity among mechanics and automotive professionals is Diagbox, a powerful diagnostic software used for diagnosing and repairing vehicles. In this article, we will explore the features and benefits of Diagbox 7.02 and 7.57, and how it can be used in conjunction with VMWARE and MHH AUTO. Diagbox is a well-known diagnostic suite for PSA
What is Diagbox?
Diagbox is a diagnostic software developed by Lexia, a leading provider of automotive diagnostic solutions. It is designed to work with a range of vehicles, including those from PSA Group (Peugeot, Citroen, DS, and Opel). The software allows users to diagnose and repair a wide range of vehicle systems, including engine, transmission, brakes, and electrical systems.
Diagbox 7.02 and 7.57: What's New?
Diagbox 7.02 and 7.57 are two of the most popular versions of the software, offering a range of new features and improvements. Some of the key features of these versions include:
Using Diagbox with VMWARE
VMWARE is a popular virtualization platform that allows users to run multiple operating systems on a single physical machine. By using Diagbox with VMWARE, users can create a virtual environment for the software, providing a range of benefits, including:
MHH AUTO: A Comprehensive Diagnostic Solution
MHH AUTO is a leading provider of automotive diagnostic solutions, offering a range of tools and software for vehicle diagnosis and repair. By combining Diagbox with MHH AUTO, users can access a comprehensive diagnostic solution that provides:
Benefits of Using Diagbox 7.02 -plus 7.57- VMWARE - MHH AUTO
By using Diagbox 7.02 and 7.57 with VMWARE and MHH AUTO, users can enjoy a range of benefits, including:
Conclusion
In conclusion, Diagbox 7.02 and 7.57 are powerful diagnostic software solutions that offer a range of advanced features and benefits. By using the software with VMWARE and MHH AUTO, users can access a comprehensive diagnostic solution that provides improved diagnostic efficiency, increased productivity, and enhanced customer satisfaction. Whether you are a mechanic, automotive professional, or fleet manager, Diagbox 7.02 and 7.57 with VMWARE and MHH AUTO are essential tools for efficient and effective vehicle diagnosis and repair.
Technical Specifications
System Requirements
Troubleshooting Tips
Frequently Asked Questions
A "Telecoding Sandbox & Snapshot Integration" feature for Diagbox 7.02–7.57 on VMware would enhance safety by utilizing automated snapshots to protect against ECU "bricking" during manual offline telecoding. This tool would include a configuration diff feature and one-click restores to protect older, unstable interface clones. Discuss these diagnostic enhancements and similar topics in the specialized discussions at MHH Auto. AI responses may include mistakes. Learn more Diagbox versions - which do I need? 7.62! - Berlingo Forum
The specific package found on MHH AUTO (Page 1 of that thread) is widely considered the most stable and versatile setup for Peugeot and Citroën vehicles. It is often preferred over newer versions (like 9.x) because it is less resource-intensive and supports older Lexia 3 clones reliably.
Step 1: Prepare the Virtual Machine
Step 2: Install Diagbox 7.02
C:\PSA\Diagbox (default path)..dll crack files found in the MHH AUTO pack.Step 3: Upgrade to 7.57
.exe or .7z patch).Step 4: The VMWare "USB Arbitration" Fix Often, Diagbox 7.57 will freeze at "Initializing..." because it cannot see the USB VCI.
.vmx file of your VM. Add the line:
usb.generic.allowHID = "TRUE"Page 1 | Diagnosis | PSA Vehicles | Virtualization
If you have landed on this page, you are likely already deep in the trenches of automotive diagnostics—specifically for the PSA Group (Peugeot, Citroën, DS, and some newer Opel models). The keywords we are dissecting today are a mouthful: Diagbox 7.02, 7.57, VMWARE, and MHH AUTO. But for technicians and enthusiasts, this string represents the holy grail of cost-effective, powerful vehicle diagnostics.
In this long-form article, we will explore why this specific combination of software versions and hardware virtualization has become the gold standard on forums like MHH AUTO (Page 1 of the search results for a reason). We will cover installation, version differences, hardware configuration, common pitfalls, and why VMware remains the superior deployment method.
VMware Setup:
\\.\pipe\diagbox). Critical for VCI passthrough later.Windows 7 Prep inside VM:
Installation Process:
Diagbox_7.02_Install.exe as Administrator.C:\PSA\Diagbox (default).Update to 7.57:
Update_7.xx_to_7.57.exe (approx 450 MB).Activation (Crucial step):
license_v4.sig to C:\PSA\Diagbox\.Diagbox_Patch.exe (Admin mode).By using VMware Workstation (or Player), you create a sandbox. Here is why the MHH AUTO community insists on VMware:
Most of this is pretty straight forward. The structure looks like:
A descriptive section
Next is the Qemu section that describes how the VM environment should be constructed. This is straightforward as well. Console types are VNC or telnet. You may have to try different ethernet adapters to see what works, but I recommend starting with the Intel e1000 because this model is supported by most VMs. Using a para-virtualized adapter may give better performance, so you may also want to try vmxnet3. Most architectures will be 64bit and RAM requirements will usually be on the website.
That leaves two sections - Images and Versions. There should be a matching entry in both places. The images section is a list of virtual hard drives and CD-ROM images to use in the VM and includes:
Let’s update this file. There are a lot of old images listed as options. I’ll remove the image and version sections for 14.04.5.3 and add the most recent (16.04.7.1). That will leave users with the last 14.x and two images in 16.x including the latest. Whether dealing with a distribution or a commercial image, changes made between versions may introduce new processes or bugs so leaving some older images gives users an easy workaround. Here’s the updated file. Scroll below the output for a discussion of submitting this back to the project.
{
"name": "Security Onion",
"category": "guest",
"description": "Security Onion is a Linux distro for intrusion detection, network security monitoring, and log management. It’s based on Ubuntu and contains Snort, Suricata, Bro, OSSEC, Sguil, Squert, ELSA, Xplico, NetworkMiner, and many other security tools. The easy-to-use Setup wizard allows you to build an army of distributed sensors for your enterprise in minutes!",
"vendor_name": "Security Onion Solutions, LLC",
"vendor_url": "https://securityonion.net/",
"documentation_url": "https://github.com/Security-Onion-Solutions/security-onion/wiki",
"product_name": "Security Onion",
"product_url": "https://securityonion.net/",
"registry_version": 3,
"status": "stable",
"maintainer": "Brent Stewart",
"maintainer_email": "brent@stewart.tc",
"usage": "Your default account will have sudo priviledges. Squil and Squert username and password are configured in the Setup wizard. MySQL root is set to null. For more info see https://github.com/Security-Onion-Solutions/security-onion/wiki/Passwords.",
"symbol": "securityonion-logo.png",
"qemu": {
"adapter_type": "e1000",
"adapters": 2,
"ram": 3072,
"arch": "x86_64",
"console_type": "vnc",
"kvm": "allow"
},
"images": [
{
"filename": "securityonion-16.04.7.1.iso",
"version": "16.04.7.1",
"md5sum": "6bd811a05c1ec7973b8fca5c34cec13e",
"filesize": 2132803584,
"download_url": "https://github.com/Security-Onion-Solutions/security-onion/releases/",
"direct_download_url": "https://github.com/Security-Onion-Solutions/security-onion/releases/download/v16.04.7.1_20181010/securityonion-16.04.7.1.iso"
},
{
"filename": "securityonion-16.04.6.1.iso",
"version": "16.04.6.1",
"md5sum": "ca835cef92c2c0daafa16e789c343d1d",
"filesize": 2020605952,
"download_url": "https://github.com/Security-Onion-Solutions/security-onion/releases/",
"direct_download_url": "https://github.com/Security-Onion-Solutions/security-onion/releases/download/v16.04.6.1_20181010/securityonion-16.04.6.1.iso"
},
{
"filename": "securityonion-14.04.5.4.iso",
"version": "14.04.5.4",
"md5sum": "9c7cab756b675beb10de4274a3ad3bc6",
"filesize": 1874853888,
"download_url": "https://github.com/Security-Onion-Solutions/security-onion/releases/",
"direct_download_url": "https://github.com/Security-Onion-Solutions/security-onion/releases/download/v14.04.5.4_20171031/securityonion-14.04.5.4.iso"
},
{
"filename": "empty30G.qcow2",
"version": "1.0",
"md5sum": "3411a599e822f2ac6be560a26405821a",
"filesize": 197120,
"download_url": "https://sourceforge.net/projects/gns-3/files/Empty%20Qemu%30disk/",
"direct_download_url": "https://sourceforge.net/projects/gns-3/files/Empty%20Qemu%20disk/empty30G.qcow2/download"
}
],
"versions": [
{
"name": "16.04.7.1",
"images": {
"hda_disk_image": "empty30G.qcow2",
"cdrom_image": "securityonion-16.04.7.1.iso"
}
},
{
"name": "16.04.6.1",
"images": {
"hda_disk_image": "empty30G.qcow2",
"cdrom_image": "securityonion-16.04.6.1.iso"
}
},
{
"name": "14.04.5.4",
"images": {
"hda_disk_image": "empty30G.qcow2",
"cdrom_image": "securityonion-14.04.5.4.iso"
}
}
]
}
In GNS3, go to File > Import Appliance and make sure that your appliance imports correctly. GNS3 will provide guidance if there’s a formatting error. Looking at the JSON above, you can imagine that a common mistake is unmatched brackets!
If the GNS3a file loads, test it by creating an instance. You need to test at least any new versions you added. Make sure the appliance boots without error and that expected interfaces are available.
Once the pieces are working, submit the appliance to the community by cloning the GNS3-registry on Github and adding in your file.
git clone https://github.com/GNS3/gns3-registry.git
If you’ve already cloned it, make sure that your branch is up to date. Upstream is the original source (in this case the GNS3 copy).
git fetch upstream
Two Python programs are included in the repo. Run them both on your copy before continuing. These are QA processes that look for issues before you submit. They will take a little time to run.
pip3 install -r requirements.txt # this does __pip3 install jsonschma__ and __pip3 install pycurl__
python3 check.py
python3 check_url.py
Next push your local copy to your github copy. In Github terms, origin is your copy on Github, and master is the local copy.
git add .
git commit -m "Updated Security Onion"
git push -f origin master
Now we have an up to date local copy of the gns3-registry that includes our updated gns3a appliance and we’ve updated our fork on Github. Next, we offer our update to the project via a Pull Request. You are going to be one of the cool kids!
Go to the gns3-registry repository on Github and select the Pull Requests tab and click the big green New pull request button. Under Compare, select the link to compare across forks (since your copy is a fork) and select your fork. It should show you the changes to files so take a moment to digest that and make sure this PR is doing what you want. Finally, submit the Pull Request. Github will email you when there’s an update to the request. If the GNS3 team has a question, they’ll submit a comment on the PR and leave it open for you to resolve. Otherwise, it will get merged in and all the other GNS3 users will be able to enjoy your hard work!
Thanks!