Since GNS3 2.0, something called uBridge is used to do some stuff, here's the description from [1]: "uBridge is a simple application to create user-land bridges between various technologies. Currently bridging between UDP tunnels, Ethernet and TAP interfaces is supported. Packet capture is also supported." It looks like uBridge is not available in Gentoo which is fine, but GNS3 asks root permissions, initial message: "uBridge requires root permission to interact with network interfaces. Set root permission to uBridge? All admin users on the system will be able to read packet from the network interfaces" and then offers to change the root of /home/<username> with the following commands: chown root:admin /home/<username> chmod 4750 /home/<username> What is the expected behavior in this case? Is uBridge really necessary for GNS3? Is there any way to disable this request as there's no ubridge in the system? It might be misleading as there's no clear explanation of what is this about and how to proceed. [1]: https://github.com/GNS3/ubridge
Created attachment 485648 [details] proposed ubridge ebuild
Created attachment 485650 [details, diff] a patch for the ebuild
Confirming it. The installation routine since GNS2.x requests ubridge or at least some assistant wants it to make initial configuration for this as Gleb has written. I have attached a working ubridge ebuild to the bug report, and a patch that is called in that ebuild. (works for me) There are some questions that needs to be answered before proceding further. 1) GNS3 2.x has 3 different installation modes: - running GNS3-gui and gns3-server on one host - running GNS-gui locally and gns3-server on far end server - running GNS3 with a vmware image once ubridge has been installed on the target system shall all 3 installation modes, or at least 2 installtion alternatives be covered? I have no option to test all 3 cases. It has been tested here only if runnig ubridge locally (gns3-server and gns3-gui on same host). 2) If done properly the ebuild maybe should add a system group, where all local users running gns3 would need be part of this group. Similarly to wireshark ebuild or docker ebuild. The user needs to be part of this group. I hope this makes sense. This ebuild atteched to that bug report does not do it, I change the group assignment manually. So that should be corrected in the ebuild. 3) If the GNS3 ebuild would not support ubridge. The gns3 source would be needed to be patched to prevent running this assistant each time gns is started. To be honest the attached ebuild + patch would need to be reviewed by somebody who is more experienced with gentoo then me. They work for me, but they still are not pretty.
I have borked the file names as attaching it. In my local repository these are named like below: net-misc/ubridge/ubridge-0.9.11.ebuild net-misc/ubridge/files/ubridge-Makefile-fixup.patch The installed version of ubridge over here is 0.9.11
Ubridge has been added to portage. I do not know when: [I] net-misc/ubridge Available versions: (~)0.9.14{tbz2} {+filecaps +system-iniparser} Installed versions: 0.9.14{tbz2}(19:22:08 04/03/18)(filecaps) Homepage: https://github.com/GNS3/ubridge Description: Bridge for UDP tunnels, Ethernet, TAP and VMnet interfaces Since using the version 0.9.14 of ubridge I have no further request like such in this bugreport described. Works for me. Gleb could you confirm this still is a problem?
