Jelle van der Waa
Jelle van der Waa
> OK :) > > I notice that through install_dialog and `manifest.json` We can install the package on Ubuntu,Debian,Fedora,Arch... > > https://github.com/cockpit-project/cockpit/blob/3f5d4c87ef6090cb3174c402a6b64ba9e0c6723d/pkg/lib/cockpit-components-install-dialog.jsx#L55 > > But How We deal with distributions...
> * New section with Interface Vpn if any detected. > * Add wireguard button conditional to having kernel >= 5.6 > * Generate Keys button conditional to have installed...
I think the dialog should use the connection settings API ``` [jelle@t14s][~/projects/cockpit/main]%busctl call org.freedesktop.NetworkManager /org/freedesktop/NetworkManager/Settings/36 org.freedesktop.NetworkManager.Settings.Connection GetSettings a{sa{sv}} 5 "connection" 6 "id" s "home" "interface-name" s "home" "permissions" as 0...
Oh and FYI, how I found settings dbus calls was by running `sudo busctl monitor > log` and in a different terminal running `nmcli con show home` and you can...
> > I also see no wireguard support in GNOME itself > > It's supposedly a feature in GNOME 43, which has just hit beta. > > https://9to5linux.com/gnome-43-alpha-released-to-kick-off-guadec-2022-in-guadalajara-mexico > >...
With: ``` diff --git a/pkg/networkmanager/interfaces.js b/pkg/networkmanager/interfaces.js index 277ede9de..4795b681f 100644 --- a/pkg/networkmanager/interfaces.js +++ b/pkg/networkmanager/interfaces.js @@ -972,7 +972,8 @@ export function NetworkManagerModel() { "org.freedesktop.NetworkManager.Device.Bond", "org.freedesktop.NetworkManager.Device.Team", "org.freedesktop.NetworkManager.Device.Bridge", - "org.freedesktop.NetworkManager.Device.Vlan" + "org.freedesktop.NetworkManager.Device.Vlan", + "org.freedesktop.NetworkManager.Device.WireGuard"...
> 3. Need to call GetSecrets for obtain private-key from `Wireguard-Instance ` > I have found that there's a GetSecrets Method for that, and privatekey is stored there. > How...
Cool! Feel free to make a draft PR then I can take a look at the code.
With my current main:  With this PR: 
@garrett the RPI 4 actually has a PCI lane, so that's expected.