-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kali gns3 uBridge is not available #2424
Comments
uBridge is an additional software that you must install. Also, how have you installed GNS3? Do you run the GNS3 server as a service already? Thanks. |
I installed it according to this official tutorial , I started it by running gns3 directly in the terminal, and according to the feedback from lsof, I should have enabled the gns3server program. (The following operation is an accidental touch, please ignore it) |
(The above operation is an error, please don't need to ignore it) I try to start separately, start the GNS3Server in the terminal, and then start the GNS3-GUI. When the new path is built, the path is not allowed, but my file path/home/CX330/desktop/2 is a legal path. At the default path, he can start normally, but still unable to pull the line, report an error |
You can find something useful here |
@Cx330-dev we don't official package uBridge (and GNS3) for Kali Linux so the best is to follow the steps listed in the document provided by @smart2128 to manually install it. |
My OS version: Kali-Rolling 2024.3
GNS3 version: 2.2.49
I tried to pull the cable for the c3600 device, and gns3-gui returned an error message:
Error while creating link: uBridge is not available, path doesn't exist, or you just installed GNS3 and need to restart your user session to refresh user permissions.
I suspected that there was a problem with gns3-server, so I opened another command line and ran gns3-server. It stopped after running some python script commands.
I suspected that port 3080 might be occupied, which caused gns3-server to not connect properly. So I checked the usage of port 3080 through lsof, which showed that port 3080 was being used by gns3-server.
I searched and found that someone had raised this issue in gns 2.1, but I checked the issue he raised and found that his situation did not match mine. Here is the link to his issue for your reference. #1247
The text was updated successfully, but these errors were encountered: