Snap: vibevpn
Interface: network-control
Requested: auto-connection, for the vibevpn.tun daemon only
What the snap is: a desktop client for Xray proxy servers. In VPN mode
traffic goes through a TUN device (tun2socks).
Why network-control is needed: the root daemon vibevpn.tun creates the
TUN interface, adds policy routing (ip rule, ip route) and adjusts
rp_filter for it. Without the interface connected VPN mode fails until
the user runs sudo snap connect vibevpn:network-control.
The GUI app (vibevpn) does not plug network-control; it only uses
network and network-bind.
The snap is strictly confined (the earlier classic request, topic 53738,
was withdrawn).
Source: vibeVpnT/vibeVpnT on GitHub, desktop/ directory
(snapcraft.yaml.in, tun_linux.go).
Given the functionality of the snap, network-control makes sense to me. Hence +1 from me to grant auto-connection of network-control interface after successful publisher vetting.
The first post was hidden as promotional — sorry, that was not the intent.
I can’t edit it anymore (the edit window has passed). The request in short:
Snap vibevpn, interface network-control, auto-connection for the
vibevpn.tun daemon only. The daemon creates the TUN device and sets
policy routing (ip rule / ip route, rp_filter); without the interface
VPN mode fails until sudo snap connect vibevpn:network-control.
The GUI app does not plug network-control.
Source: vibeVpnT/vibeVpnT on GitHub, desktop/ directory.
@shishirsub10@jslarraz could you please ask a moderator to unhide the
first post, or treat this reply as the request? Thanks.
Done, sorry for the inconvenience…
The system automatically marks posts as spam if they are created really quickly after user creation (assuming you’re a bot then)
+2 votes for, 0 votes against, publisher is successfully vetted, granting auto-connection of network-control interface to vibevpn snap, this is now live.