From: eoli3n <eoli3n@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gns3 : could not start vpcs
Date: Sat, 06 May 2023 22:36:27 +0200 [thread overview]
Message-ID: <20230506203627.0ksyTMN7RApdKPSVT0qJqKJ2KE8gL116ThYBvVUXW3E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43766@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1168 bytes --]
New comment by eoli3n on void-packages repository
https://github.com/void-linux/void-packages/issues/43766#issuecomment-1537218997
Comment:
[Official documentation](https://docs.gns3.com/docs/getting-started/installation/linux) asks to add user to the ``ubridge`` group.
ubridge is installed but no ubridge group exists on my system.
```
$ xbps-query ubridge
architecture: x86_64
filename-sha256: 4011c4a1e278371ccd7b9e3a259b37e4065d06d693618334980e3811fee6538d
filename-size: 33KB
homepage: https://github.com/GNS3/ubridge
install-date: 2023-05-05 22:45 CEST
install-script: 711B
installed_size: 80KB
license: GPL-3.0-or-later
maintainer: Cameron Nemo <cam@nohom.org>
metafile-sha256: 211fdfdafbde75023efcb6f447d6e573a07d8697399a387e9a6bd5bb4c758bbc
pkgname: ubridge
pkgver: ubridge-0.9.18_2
repository: https://repo-default.voidlinux.org/current
run_depends:
glibc>=2.36_1
iniparser>=4.1_1
libpcap>=1.1.1_1
shlib-requires:
libc.so.6
libiniparser.so.1
libpcap.so.1
short_desc: Bridge for UDP tunnels, Ethernet, TAP and VMnet interfaces
source-revisions: ubridge:f50f428fbe
state: installed
$ grep ubridge /etc/group
$
```
next prev parent reply other threads:[~2023-05-06 20:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 21:06 [ISSUE] gns3 eoli3n
2023-05-06 19:53 ` gns3 : could not start vpcs eoli3n
2023-05-06 20:36 ` eoli3n [this message]
2023-05-23 2:09 ` sgn
2023-05-23 15:44 ` eoli3n
2024-05-15 18:15 ` [ISSUE] [CLOSED] " classabbyamp
2024-05-15 18:15 ` classabbyamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230506203627.0ksyTMN7RApdKPSVT0qJqKJ2KE8gL116ThYBvVUXW3E@z \
--to=eoli3n@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).