26 November 2025
Akhmed Allright#nodes-troubleshooting
If you encounter issues with a node not starting or immediately stopping after clicking the start button, consider the following checklist and potential solutions:
Common Checks:
1. Image Integrity:
- Verify that the image is not corrupted. Compare the size of the image on your server with the size of the image from the source (e.g., LabHub).
For IOL Images:
1. Generate License File:
- Ensure that the license file is generated. Send #generate_license in this chat to receive instructions on how to generate the license file.
For QEMU Images:
1. Virtualization Support:
- Confirm that virtualization is supported on your system. Send #check-vt in this chat to receive instructions on how to check for virtualization support.
2. Fix Permissions:
- Correct permissions either through the GUI (click the button under "Settings" on PNetLab) or by running the following command in the terminal:
/opt/unetlab/wrappers/unl_wrapper -a fixpermissions
3. Follow the naming conventions:
- Adhere to the naming conventions required for PNetLab to detect imported qcow2 files as VMs. Refer to the conventions outlined here: https://www.eve-ng.net/index.php/documentation/qemu-image-namings/
By following these steps, you can address potential issues related to image integrity, licensing for IOL images, virtualization support for QEMU images, and permissions. If the problem persists after performing these checks and fixes, please let us know.
Akhmed Allright#generate_license
Файл
CiscoIOUKeygen.py · 1 KB · click to show
CiscoIOUKeygen.py · 1 KB · click to show
Instructions to generate iourc license
1. Move to the bin directory:
cd /opt/unetlab/addons/iol/bin/
2. Execute the keygen in that location with python2
python CiscoIOUKeygen.py > iourc
Done, iol images should be working now
⚠️ Notes:
- Install python2 if you don't have it installed.
- If the keygen does not exist in that directory, use the one attached to these notes.
- If you're using ishare2, you can just issue the command: ishare2 relicense
27 November 2025
AlbertoIf I choose telnet I get the container bash, not the stdin
normally, you can running portainer on your pnetlab server. After install portainer, you will get a web for portainer page, and on the page you will have the containers running on the pnetlab server. And then you can access them with /bin/bash or /bin/sh , and log also.
༺ꃲ༻text not yet in the index
use the guide from eve-ng on how to upload an nx-os image in pnetlab and same naming convention in the folder
Jackynormally, you can running portainer on your pnetlab server. After install portainer, you will get a web for portainer page, and on the page you will have the containers running on the pnetlab server. And then you can access them with /bin/bash or /bin/sh , and log also.
Thanks, Jacky. I will look over it
Another docker question. Arista cEOS allows me bind its eth0 interface to any network I want to. Now, I am deploying another container, but its eth0 is greyed out with the message "Management Only" and it is bound to the docker0 bridge. I have already taken a look in the device_ceos.php, but I can't figure out how that works for cEOS, but not works for my container. Could anyone point the right way to do it?
@Ndawendua NetoGood afternoon.
Could someone share the package of these icons for pnetlab?
Thank you.
i'm looking for theses icons too
28 November 2025
Mukesh KumarI want practice of sdwan on pnetlab.anyone suggested this plateform is best for sdwan practice
yes if you have good resources.