ChatCrawlersearch across public Telegram Open the app
P

PNETLAB platform Group

snapshot for November 2025
November 2025 ×
22 November 2025
R
T#generate_license
Файл
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
23 November 2025
I am currently experiencing a challenge with my PNET. I discovered that I could not log in at some point, I do not know why but I re-installed the VM and now I cannot download images
I keep getting the error
Фотография
click to show
I can resolve DNS names
but I do not know why this is happening
I am unable to pull images
V
Can I get some assistance please
S
Фотография
click to show
Фотография
click to show
Hi does anyone knows nd-9.3.2.1l cli password. On web service UI i can login with which i assigned the credentials but can not log in to cli. And can not deploy via cli cause of second image error.
R
Replymessage unavailable
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.
24 November 2025
Фотография
click to show
Hello Team I am working on Palo alto Eve-ng Lab and facing some issue and need guidance. Default Route on Palo Alto 0.0.0..0/0 next hop 20.1.1.2 Default Route on Router 0.0.0.0/0 next hop 192.168.1.1 Router can reach to 192.168.1.1 and 8.8.8.8 both. Palo alto can reach to 192.168.1.150 but cannot reach to 192.168.1.1 and 8.8.8.8 Am I missing anything?
D
Palo alto version is 11.2.5
R
if this is internal then you need route back from 192.168.1.1 towards 192.168.1.150 for the Palo subnet)
Open in Telegram Каталог площадок Искать в ChatCrawler

A snapshot of an open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog