Cheers

Keep safe everyone.

Pootler

so why would dylanaraps go to all the trouble of building iwd without dbus?

Dylan is utterly fanatical about minimalism and will go to almost any lengths to reduce the code base.

EDIT: I removed all of the xinerama ifdefs from my custom dwm packages for Alpine, Debian & OpenBSD for a similar reason. It saved a few hundred SLOC IIRC.

iwd doesn't have a dbus dependency and works just fine without it, dbus activation is only needed if iwd is being used as a backend for NetworkManager or connman.

@OP: sorry for the diversion, I'll stop now.

so why would dylanaraps go to all the trouble of building iwd without dbus?

https://github.com/dylanaraps/eiwd

Why are you sorry, the OP has probably gone back to windows or ubuntu, mint.

@OP: sorry for the diversion, I'll stop now.

dice wrote:

Ill probably switch to iwd when/if it is ready for devuan

The iwd maintainer wouldn't add the init scripts to the package without a proper diff but they did modify it so that non-systemd dbus activation should work. This means that the version in testing/unstable should work as a backend for NetworkManager or connman but an init script would still have to be added for standalone usage.

See https://bugs.debian.org/cgi-bin/bugrepo … bug=966518 for the details.

I wonder if this eiwd is worth looking into for a no dbus dependancy, still would need an init script created for it though. Might give it a try myself. Although it looks like dylanaraps has left this project to gather some dust for one reason or another.

https://github.com/dylanaraps/eiwd/releases

Ill probably switch to iwd when/if it is ready for devuan

The iwd maintainer wouldn't add the init scripts to the package without a proper diff but they did modify it so that non-systemd dbus activation should work. This means that the version in testing/unstable should work as a backend for NetworkManager or connman but an init script would still have to be added for standalone usage.

See https://bugs.debian.org/cgi-bin/bugrepo … bug=966518 for the details.

I prefer iwd over wpa_supplicant because it is lighter, more secure, has fewer dependencies and it can be used as a complete wireless networking solution by itself (it has built-in dhcp functionality). The only drawbacks are that the Devuan package lacks a sysvinit script and the version in beowulf is pre-release.

Ill probably switch to iwd when/if it is ready for devuan. Ive used it in bleeding edge arch and it works quite well, easy to configure using iwctl.

This issue possibly because you dont have libelogind0 installed?

do

sudo apt install libelogind0

and then yes to remove libsystemd0

then try to install network manager again.

I believe this is the issue, i could be wrong...

edit: I was successfully able to install network manager on devuan beowulf just now.

In that case getting Network Manager working is probably a better idea, its usually just click and connect, disconnect.

If you have the file /etc/network/interfaces make sure to comment out any networks in relation to your wifi or ethernet as i believe Network Manager handles this in its own way.

Ive used NetworkManager in the past and it does the job.

Try installing it like this.

sudo apt install network-manager network-manager-gnome

reboot

get this from terminal:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
network-manager : Depends: libpolkit-agent-1-0 (>= 0.99) but it is not going to be installed
                   Depends: libpolkit-gobject-1-0 (>= 0.104)
                   Depends: libpam-systemd
                   Depends: policykit-1 but it is not going to be installed
                   Recommends: modemmanager but it is not going to be installed
network-manager-gnome : Depends: policykit-1-gnome but it is not going to be installed or
                                  polkit-1-auth-agent
E: Unable to correct problems, you have held broken packages.

This is a fresh install and has been updated and upgraded?

as root user do the following.

wpa_passphrase ESSID PASSPHRASE > /etc/wpa_supplicant/wpa_supplicant.conf

It is possible to use ifupdown without creating a wpa_supplicant configuration file.

Just define the SSID and password directly in /etc/network/interfaces, like this:

auto wlan0
iface wlan0 inet dhcp
   wpa-ssid $ssid
   wpa-psk $password

Replace $ssid with the name of the access point and replace $password with the password (or use the obfuscated psk line from the wpa_passphrase output but note that the hashing is performed unsalted so it should not be considered secure).

See also https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK

But having said that a wpa_supplicant configuration file would allow for the use of wpagui, which needs these lines added to the top of the configuration file:

ctrl_interface=/run/wpa_supplicant
update_config=1

The GUI is fairly "friendly" and may be suitable for the OP's needs.

I prefer iwd over wpa_supplicant because it is lighter, more secure, has fewer dependencies and it can be used as a complete wireless networking solution by itself (it has built-in dhcp functionality). The only drawbacks are that the Devuan package lacks a sysvinit script and the version in beowulf is pre-release.

I had a flaky wireless network card that thankfully also got added to mainline kernel tree around the time I had to drop wicd, so I was never sure if it was the flaky driver or wicd.

If you have the file /etc/network/interfaces make sure to comment out any networks in relation to your wifi or ethernet as i believe Network Manager handles this in its own way.

Ive used NetworkManager in the past and it does the job.

Try installing it like this.

sudo apt install network-manager network-manager-gnome

reboot

Nice to talk to you again :-)

Thanks for the info - will try your method , but unfortunately I am not the only one using the laptop, so it needs to be ''uber friendly''.

Cheers

pootler

basic wifi wpa_supplicant setup.

as root user do the following.

wpa_passphrase ESSID PASSPHRASE > /etc/wpa_supplicant/wpa_supplicant.conf

edit /etc/network/interfaces to look something like below.

auto lo
iface lo inet loopback

auto wlan0
iface wlan0 inet dhcp
        wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf

allow-hotplug usb0
iface usb0 inet dhcp

you can control wifi by using sudo ifup wlan0 to bring wifi up and sudo ifdown wlan0 to bring it down.

In any case having auto wlan0 in /etc/network/interfaces will connect automatically on boot if you are using devuan beowulf.

You can have multiple wifi wpa_supplicant networks as well and connect to them manually with a bit of editing.