Using Iwd in Proxmox

[Jessedw]

Hi,

When trying to setup a Wireless Bridge towards my VMs i first am trying to setup a Wifi connection.
I found this user friendly wireless deamon written by intel iwd, but I can't get it to work.

I follow the simple user guide, but get stuck at the point of connection.

This are the networks available at scan:

[iwd]# station wlp7s0 get-networks
                               Available networks                             
--------------------------------------------------------------------------------
    Network name                    Security          Signal
--------------------------------------------------------------------------------
    Mothership                      psk               **** 
    Verachtert                      psk               ****
    telenet-800EB                   psk               ****
    ATLANTIS                        psk               ****
    L&L                             psk               ****
    deroeck                         psk               ****
    telenet-DE98C86                 psk               ****

The first one is mine, so I try:

iwd]# station wlp7s0 connect Mothership                                       
Type the network passphrase for Mothership psk.                                 
Passphrase: ********                                                           
Operation failed

also when passing the psk directly:

[iwd]# station wlp7s0 connect Mothership [B34mM3Up]
Invalid network name 'Mothership'

I get a response which doesn't make sense to me.

To further trobleshoot I took a look at the status of the iwd service

iwd.service - Wireless service
     Loaded: loaded (/lib/systemd/system/iwd.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2022-09-18 15:11:18 CEST; 23min ago
   Main PID: 1826406 (iwd)
      Tasks: 1 (limit: 76705)
     Memory: 2.4M
        CPU: 122ms
     CGroup: /system.slice/iwd.service
             └─1826406 /usr/libexec/iwd

Sep 18 15:11:18 Labsever iwd[1826406]: Loaded configuration from /etc/iwd/main.conf
Sep 18 15:11:18 Labsever systemd[1]: Started Wireless service.
Sep 18 15:11:18 Labsever iwd[1826406]: [General].APRanges must be set for DHCP
Sep 18 15:11:18 Labsever iwd[1826406]: Wiphy: 0, Name: phy0
Sep 18 15:11:18 Labsever iwd[1826406]:         Permanent Address: 2c:fd:a1:cf:c1:1b
Sep 18 15:11:18 Labsever iwd[1826406]:         Bands: 2.4 GHz 5 GHz
Sep 18 15:11:18 Labsever iwd[1826406]:         Ciphers: CCMP TKIP BIP
Sep 18 15:11:18 Labsever iwd[1826406]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Sep 18 15:11:18 Labsever iwd[1826406]: Wiphy phy0 will only use the default interface
Sep 18 15:11:26 Labsever iwd[1826406]: Unexpected connection related event -- is another supplicant running?

I don't know if there is another supplicant running, I tried this command systemctl --type=service --state=running

and got:

root@Labsever:/# systemctl --type=service --state=running
  UNIT                     LOAD   ACTIVE SUB     DESCRIPTION
  chrony.service           loaded active running chrony, an NTP client/server
  cron.service             loaded active running Regular background program processing daemon
  dbus.service             loaded active running D-Bus System Message Bus
  dm-event.service         loaded active running Device-mapper event daemon
  getty@tty1.service       loaded active running Getty on tty1
  iscsid.service           loaded active running iSCSI initiator daemon (iscsid)
  iwd.service              loaded active running Wireless service
  ksmtuned.service         loaded active running Kernel Samepage Merging (KSM) Tuning Daemon
  lxc-monitord.service     loaded active running LXC Container Monitoring Daemon
  lxcfs.service            loaded active running FUSE filesystem for LXC
  ovs-vswitchd.service     loaded active running Open vSwitch Forwarding Unit
  ovsdb-server.service     loaded active running Open vSwitch Database Unit
  postfix@-.service        loaded active running Postfix Mail Transport Agent (instance -)
  pve-cluster.service      loaded active running The Proxmox VE cluster filesystem
  pve-firewall.service     loaded active running Proxmox VE firewall
  pve-ha-crm.service       loaded active running PVE Cluster HA Resource Manager Daemon
  pve-ha-lrm.service       loaded active running PVE Local HA Resource Manager Daemon
  pve-lxc-syscalld.service loaded active running Proxmox VE LXC Syscall Daemon
  pvedaemon.service        loaded active running PVE API Daemon
  pvefw-logger.service     loaded active running Proxmox VE firewall logger
  pveproxy.service         loaded active running PVE API Proxy Server
  pvescheduler.service     loaded active running Proxmox VE scheduler
  pvestatd.service         loaded active running PVE Status Daemon
  qmeventd.service         loaded active running PVE Qemu Event Daemon
  rpcbind.service          loaded active running RPC bind portmap service
  rrdcached.service        loaded active running LSB: start or stop rrdcached
  rsyslog.service          loaded active running System Logging Service
  smartmontools.service    loaded active running Self Monitoring and Reporting Technology (SMART) Daemon
  spiceproxy.service       loaded active running PVE SPICE Proxy Server
  ssh.service              loaded active running OpenBSD Secure Shell server
  systemd-journald.service loaded active running Journal Service
  systemd-logind.service   loaded active running User Login Management
  systemd-udevd.service    loaded active running Rule-based Manager for Device Events and Files
  user@0.service           loaded active running User Manager for UID 0
  watchdog-mux.service     loaded active running Proxmox VE watchdog multiplexer
  zfs-zed.service          loaded active running ZFS Event Daemon (zed)

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
36 loaded units listed.

What am I missing here?

 

[Jessedw]

Update:

After reboot I noticed the device got renamed to Wlan0,
Changing the interfaces conf accordingly did enably me to succesfully connect!

[iwd]# station wlan0 show
                                 Station: wlan0                               *
--------------------------------------------------------------------------------
  Settable  Property            Value                                         
--------------------------------------------------------------------------------
            Scanning            no
            State               connected
            Connected network   Mothership                                     
            ConnectedBss        68:02:b8:24:e9:2d   
            Frequency           5180               
            Security            WPA2-Personal       
            RSSI                -51                  dBm
            AverageRSSI         -50                  dBm
            TxBitrate           1040000              Kbit/s
            RxBitrate           6000                 Kbit/s

Next step is to get the bridge working, only here I got stuck again...
This is how i setup the bridge, using linux bridge
(since OVS gets me the error interface 'wlan0' is not defined as OVS port/bond (500))

auto vmbr2
iface vmbr2 inet manual
    bridge-ports wlan0
    bridge-stp off
    bridge-fd 0
#Wi-fi Bridge

Trying to get the interface up, i receive the next error:

root@Labsever:/etc/network# ifup vmbr2
warning: vmbr2: apply bridge ports settings: cmd '/bin/ip -force -batch - [link set dev wlan0 master vmbr2]' failed: returned 1 (Error: Device does not allow enslaving to a bridge.
Command failed -:

How should I proceed to create a bridge for my VMs?

 

[RumpleSS]

Did you manage to create a bridge?

 

[Jessedw]

Did you manage to create a bridge?

No, I abandoned this idea and used PCI passthrough to link the wifi card to the VM and connected from there...