Hi, I have error when i try to force wpa_supplicant to start before connmand by puting it in @ extdepends or @ optsdepends of connmand service file.

Full error: 
# 66-enable -S -F -v4 connmand
66-enable(src/lib66/parser_enabled.c: parse_service_before(): 42): tracing: start parse process of service: /usr/lib/66/service/connmand
66-enable(src/lib66/parser_enabled.c: parse_service_before(): 82): tracing: read service file of: /usr/lib/66/service/connmand
66-enable(src/lib66/parser_enabled.c: parse_service_deps(): 241): tracing: /usr/lib/66/service/connmand: haven't dependencies
66-enable(src/lib66/parser_enabled.c: parse_service_before(): 42): tracing: start parse process of service: /usr/lib/66/service/dbus
66-enable(src/lib66/parser_enabled.c: parse_service_before(): 82): tracing: read service file of: /usr/lib/66/service/dbus
66-enable(src/lib66/parser_enabled.c: parse_service_deps(): 241): tracing: /usr/lib/66/service/dbus: haven't dependencies
66-enable(src/lib66/parser_enabled.c: parse_add_service(): 370): tracing: add service: /usr/lib/66/service/dbus
66-enable(src/lib66/parser_enabled.c: parse_service_before(): 42): tracing: start parse process of service: /usr/lib/66/service/wpa_supplicant
66-enable(src/lib66/parser_enabled.c: parse_service_before(): 82): tracing: read service file of: /usr/lib/66/service/wpa_supplicant
66-enable(src/lib66/parser_enabled.c: parse_add_service(): 370): tracing: add service: /usr/lib/66/service/wpa_supplicant
66-enable(src/lib66/parser_enabled.c: parse_add_service(): 370): tracing: add service: /usr/lib/66/service/connmand
66-enable(src/lib66/parser_write.c: write_services(): 110): tracing: Write service dbus ...
66-enable(src/lib66/ss_environ.c: env_import_version_file(): 300): warning: same configuration file version for: dbus -- nothing to import
66-enable(src/lib66/ssexec_enable.c: start_write(): 114): tracing: write resolve file of: dbus
66-enable(src/lib66/ssexec_enable.c: start_write(): 126): tracing: Service written successfully: dbus
66-enable(src/lib66/parser_write.c: write_services(): 110): tracing: Write service wpa_supplicant ...
66-enable(src/lib66/ss_environ.c: env_import_version_file(): 300): warning: same configuration file version for: wpa_supplicant -- nothing to import
66-enable(src/lib66/ssexec_enable.c: start_write(): 114): tracing: write resolve file of: wpa_supplicant
66-enable(src/lib66/ssexec_enable.c: start_write(): 126): tracing: Service written successfully: wpa_supplicant
66-enable(src/lib66/parser_write.c: write_services(): 110): tracing: Write service connmand ...
66-enable(src/lib66/ss_environ.c: env_import_version_file(): 300): warning: same configuration file version for: connmand -- nothing to import
66-enable(src/lib66/ssexec_enable.c: start_write(): 114): tracing: write resolve file of: connmand
66-enable(src/lib66/ssexec_enable.c: start_write(): 126): tracing: Service written successfully: connmand
s6-rc-compile: tracing: from s6-rc-compile internals: adding identifier s6rc-oneshot-runner of type longrun
s6-rc-compile: tracing: from s6-rc-compile internals: adding identifier s6rc-fdholder of type longrun
s6-rc-compile: info: parsing /tmp/root:miDcyx/db/source/Master
s6-rc-compile: info: Master has type bundle
s6-rc-compile: tracing: from /tmp/root:miDcyx/db/source: adding identifier Master of type bundle
s6-rc-compile: tracing: from Master: adding identifier connmand-log of type unknown
s6-rc-compile: tracing: from Master: adding identifier dbus-log of type unknown
s6-rc-compile: tracing: from Master: adding identifier dbus of type unknown
s6-rc-compile: tracing: from Master: adding identifier wpa_supplicant-log of type unknown
s6-rc-compile: tracing: from Master: adding identifier wpa_supplicant of type unknown
s6-rc-compile: tracing: from Master: adding identifier connmand of type unknown
s6-rc-compile: info: parsing /tmp/root:miDcyx/db/source/connmand
s6-rc-compile: info: connmand has type longrun
s6-rc-compile: tracing: from /tmp/root:miDcyx/db/source: adding identifier connmand of type longrun
s6-rc-compile: tracing: previously encountered identifier connmand now has type longrun
s6-rc-compile: tracing: from connmand: adding identifier dbus of type unknown
s6-rc-compile: tracing: identifier dbus was already declared with type unknown
s6-rc-compile: tracing: from connmand: adding identifier wpa_supplicant of type unknown
s6-rc-compile: tracing: identifier wpa_supplicant was already declared with type unknown
s6-rc-compile: tracing: from connmand: adding identifier connmand-log of type unknown
s6-rc-compile: tracing: identifier connmand-log was already declared with type unknown
s6-rc-compile: info: connmand is a producer for connmand-log
s6-rc-compile: info: parsing /tmp/root:miDcyx/db/source/connmand-log
s6-rc-compile: info: connmand-log has type longrun
s6-rc-compile: tracing: from /tmp/root:miDcyx/db/source: adding identifier connmand-log of type longrun
s6-rc-compile: tracing: previously encountered identifier connmand-log now has type longrun
s6-rc-compile: tracing: from connmand-log: adding identifier connmand of type unknown
s6-rc-compile: tracing: identifier connmand was already declared with type longrun
s6-rc-compile: info: connmand-log is a consumer for connmand
s6-rc-compile: info: parsing /tmp/root:miDcyx/db/source/dbus
s6-rc-compile: info: dbus has type longrun
s6-rc-compile: tracing: from /tmp/root:miDcyx/db/source: adding identifier dbus of type longrun
s6-rc-compile: tracing: previously encountered identifier dbus now has type longrun
s6-rc-compile: tracing: from dbus: adding identifier dbus-log of type unknown
s6-rc-compile: tracing: identifier dbus-log was already declared with type unknown
s6-rc-compile: info: dbus is a producer for dbus-log
s6-rc-compile: info: parsing /tmp/root:miDcyx/db/source/dbus-log
s6-rc-compile: info: dbus-log has type longrun
s6-rc-compile: tracing: from /tmp/root:miDcyx/db/source: adding identifier dbus-log of type longrun
s6-rc-compile: tracing: previously encountered identifier dbus-log now has type longrun
s6-rc-compile: tracing: from dbus-log: adding identifier dbus of type unknown
s6-rc-compile: tracing: identifier dbus was already declared with type longrun
s6-rc-compile: info: dbus-log is a consumer for dbus
s6-rc-compile: info: making bundles for pipelines
s6-rc-compile: info: resolving bundle names
s6-rc-compile: fatal: during resolution of bundle Master: undefined service name wpa_supplicant-log
66-enable(src/lib66/db_compile.c: db_compile(): 79): warning: unable to compile: /tmp/root:miDcyx/db/root
66-enable(src/lib66/ssexec_enable.c: ssexec_enable(): 341): fatal: unable to compile /tmp/root:miDcyx/root
Is this expected behavior, I just want to avoid the error:

2021-10-27 23:46:25.526167771 dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2021-10-27 23:46:25.526384547 dbus: Could not request service name: already registered
2021-10-27 23:46:25.526421466 Failed to initialize wpa_supplicant

Lately I cannot supervise wpa_supplicant using 66 tools because connmand starts its own wpa_supplicant before 66 has a chance to start it resulting in the error above.

To rectify I need to stop connmand manually, then force start wpa_supplicant before restarting connmand again. Need some insight.
You can take an example on the last JWM ISO flavor. You will see that wpa_supplicant is supervised.
You need to declare dbus as a dependency (@ depends or @ extdepends) for connmand. This is ensure you that dbus start before connmand. Wpa_supplicant do not depends on any service.
Also, wpa_supplicant is a classic one, so @ type = classic.
With this setup, you should be able to start/stop wpa_supplicant independently from connmand.
Ask again if it fail again.
How can I make sure wpa_supplicant starts before connmand?

Ive beeen getting the error: 
2021-10-27 23:46:25.526167771  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2021-10-27 23:46:25.526384547  dbus: Could not request service name: already registered
2021-10-27 23:46:25.526421466  Failed to initialize wpa_supplicant
because connmand starts wpa_supplicant independent from 66 tools.

Edit:Maybe I put connmand in boot-user tree and wpa_supplicant in root tree for now.
How can I make sure wpa_supplicant starts before connmand?
Classic service always start before atomic, bundle service and always stop after atomic, bundle service.
Maybe I put connmand in boot-user tree and wpa_supplicant in root tree for now.
The boot tree should only contain necessary service for the boot sequence.
Can please you show us the output of 
# 66-intree -zg
eric wrote Classic service always start before atomic, bundle service and always stop after atomic, bundle service.
Hmm, interesting that longrun connmand which is bundle service seems to be starting before classic service wpa_supplicant in my system. My trees seem fine:
# 66-intree -zg
Name         : boot
Initialized  : yes
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(209,Enabled,classic) tty-earlier@ tty12
               ├─(up,Enabled,oneshot) system-hostname
               ├─(up,Enabled,oneshot) mount-run
               ├─(up,Enabled,oneshot) populate-run
               ├─(up,Enabled,oneshot) mount-tmp
               ├─(up,Enabled,oneshot) populate-tmp
               ├─(up,Enabled,oneshot) mount-proc
               ├─(up,Enabled,oneshot) mount-sys
               ├─(up,Enabled,oneshot) populate-sys
               ├─(up,Enabled,oneshot) mount-dev
               ├─(up,Enabled,oneshot) mount-pts
               ├─(up,Enabled,oneshot) mount-shm
               ├─(up,Enabled,oneshot) populate-dev
               ├─(up,Enabled,oneshot) mount-cgroups
               ├─(up,Enabled,bundle) 00
               ├─(up,Enabled,bundle) all-Mount
               ├─(up,Enabled,oneshot) system-hwclock
               ├─(up,Enabled,oneshot) modules-kernel
               ├─(up,Enabled,oneshot) system-random
               ├─(up,Enabled,oneshot) modules-system
               ├─(up,Enabled,oneshot) system-sysctl
               ├─(311,Enabled,longrun) udevd-log
               ├─(443,Enabled,longrun) udevd
               ├─(up,Enabled,oneshot) udevadm
               ├─(up,Enabled,oneshot) system-fontnkey
               ├─(up,Enabled,oneshot) system-fsck
               ├─(up,Enabled,oneshot) mount-fstab
               ├─(up,Enabled,bundle) all-System
               ├─(up,Enabled,oneshot) mount-rw
               ├─(up,Enabled,oneshot) mount-netfs
               ├─(up,Enabled,oneshot) local-loop
               ├─(up,Enabled,oneshot) local-sethostname
               ├─(up,Enabled,oneshot) local-time
               ├─(up,Enabled,oneshot) local-authfiles
               ├─(up,Enabled,oneshot) local-tmpfiles
               ├─(up,Enabled,oneshot) local-rc
               ├─(up,Enabled,oneshot) local-dmesg
               ├─(up,Enabled,bundle) all-Local
               ├─(up,Enabled,oneshot) all-Runtime
               ├─(up,Enabled,bundle) All
               ├─(1050,Enabled,longrun) tty-rc@ tty2
               ├─(1051,Enabled,longrun) tty-rc@ tty1
               └─(up,Enabled,module) boot@ system

Name         : virt
Initialized  : no
Enabled      : no
Starts after : None
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(0,Enabled,longrun) virtlogd-log
               ├─(0,Enabled,longrun) virtlogd
               ├─(unitialized,Enabled,oneshot) virtlockd-socket
               ├─(0,Enabled,longrun) virtlockd-log
               ├─(0,Enabled,longrun) virtlockd
               ├─(0,Enabled,longrun) libvirtd-log
               └─(0,Enabled,longrun) libvirtd

Name         : root
Initialized  : yes
Enabled      : yes
Starts after : None
Current      : yes
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(909,Enabled,classic) openntpd-log
               ├─(900,Enabled,classic) cupsd-log
               ├─(902,Enabled,classic) cupsd
               ├─(910,Enabled,classic) wpa_supplicant-log
               ├─(907,Enabled,classic) acpid-log
               ├─(1053,Enabled,classic) wpa_supplicant
               ├─(911,Enabled,classic) acpid
               ├─(908,Enabled,classic) openntpd
               ├─(927,Enabled,longrun) dbus-log
               └─(931,Enabled,longrun) dbus

Name         : boot-user
Initialized  : yes
Enabled      : yes
Starts after : root
Current      : no
Allowed      : root
Symlinks     : svc->source db->source
Contents     : /
               ├─(up,Enabled,oneshot) setenv@ orb
               ├─(985,Enabled,longrun) svscan@ orb-log
               ├─(1041,Enabled,longrun) svscan@ orb
               ├─(up,Enabled,module) scandir@ orb
               ├─(986,Enabled,longrun) seatd-log
               ├─(1001,Enabled,longrun) seatd
               ├─(up,Enabled,module) console-tracker@ seatd
               ├─(up,Enabled,oneshot) mount-run@ orb
               ├─(984,Enabled,longrun) sddm-log
               ├─(1009,Enabled,longrun) sddm
               ├─(up,Enabled,module) display-manager@ sddm
               ├─(up,Enabled,module) boot-user@ orb
               ├─(988,Enabled,longrun) consolekit-log
               ├─(991,Enabled,longrun) connmand-log
               ├─(1005,Enabled,longrun) connmand
               └─(1006,Enabled,longrun) consolekit
Hmm, interesting that longrun connmand which is bundle service seems to be starting before classic service wpa_supplicant in my system
According to your output, connmand service is a longrun one, not a bundle. The tree boot-user start after the root tree, so wpa_supplicant is started before any services found at boot-user tree.
I'm a little confuse now. Your trees seems correct and apparently the wpa_supplicant seem running fine.
So, do you have any other troubles?
Sorry for the confusion, what is the difference between longrun&bundle service? Problem only happens when I put wpa_supplicant&connmand in root tree together.

A clue to whats wrong with my system may be in at shutdown when all-runtime crashes every time, yet my system shuts down just fine. Any way to check shutdown logs without chroot from different system?

66-inservice wpa_supplicant just shows the output I posted earlier with dbus name already registered error if I put both wpa_supplicant& connmand in root tree. I'm not sure it happens evey time, but seems to happen at initialization.
longrun is one service whereas bundle is a set of service.
wpa_supplicant&connmand in root tree together.
this is curious.
Any way to check shutdown logs without chroot from different system
edit your /etc/66/rc.shutdown and replace 
# redirfd -w 1 /dev/console
by 
redirfd -w 1 /var/log/shutdown
and see your logs at this file.

Where did come from your dbus package?
My dbus package comes from obcore but my connman package is connman-git so this may be the cullprit. I will mark it solved if installing the connman package from obcommunity fixes it.

For some reason 66 tools has trouble controlling the service when connman-git is installed. Thank you for the tip, my shutdown file looks like:
[Starts rc.shutdown...]
all-Runtime: info: stops...
66-all(src/lib66/ssexec_stop.c: ssexec_stop(): 236): tracing: stop atomic services ...
s6-rc: info: bringing selected services down
s6-rc: info: service mount-run@ orb: stopping
s6-rc: info: service svscan@ orb: stopping
s6-rc: info: service sddm: stopping
s6-rc: info: service consolekit: stopping
s6-rc: info: service connmand: stopping
s6-ipcclient: connected to /run/66/tree/0/boot-user/servicedirs/s6rc-oneshot-runner/s
s6-rc: info: service mount-run@ orb successfully stopped
s6-rc: info: service consolekit successfully stopped
s6-rc: info: service consolekit-log: stopping
s6-rc: info: service consolekit-log successfully stopped
s6-rc: info: service connmand successfully stopped
s6-rc: info: service connmand-log: stopping
s6-rc: info: service connmand-log successfully stopped
s6-rc: info: service svscan@ orb successfully stopped
s6-rc: info: service setenv@ orb: stopping
s6-rc: info: service svscan@ orb-log: stopping
s6-ipcclient: connected to /run/66/tree/0/boot-user/servicedirs/s6rc-oneshot-runner/s
s6-rc: info: service setenv@ orb successfully stopped
s6-rc: info: service svscan@ orb-log successfully stopped
s6-rc: info: service sddm successfully stopped
s6-rc: info: service seatd: stopping
s6-rc: info: service sddm-log: stopping
s6-rc: info: service sddm-log successfully stopped
s6-rc: info: service seatd successfully stopped
s6-rc: info: service seatd-log: stopping
s6-rc: info: service seatd-log successfully stopped
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: boot-user@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: boot-user@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: display-manager@ sddm
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: display-manager@ sddm
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: sddm
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: sddm
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: sddm-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: sddm-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: mount-run@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: mount-run@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: console-tracker@ seatd
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: console-tracker@ seatd
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: seatd
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: seatd
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: seatd-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: seatd-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: scandir@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: scandir@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: svscan@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: svscan@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: svscan@ orb-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: svscan@ orb-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: setenv@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: setenv@ orb
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: consolekit
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: consolekit
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: consolekit-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: consolekit-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 147): warning: unable to stop: connmand
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: connmand
66-all(src/lib66/ssexec_dbctl.c: check_status(): 163): tracing: Write state file of: connmand-log
66-all(src/lib66/ssexec_dbctl.c: check_status(): 169): info: Stopped successfully: connmand-log
66-all(src/lib66/ssexec_stop.c: ssexec_stop(): 238): fatal: unable to stop atomic services
all-Runtime: fatal: crashed!
system-random: info: stops...
system-hwclock: info: stops...
populate-sys: info: stops...
populate-dev: info: stops...
mount-cgroups: info: stops...
mount-shm: info: stops...
mount-pts: info: stops...
mount-tmp: info: stops...
[rc.shutdown completed successfully]
edit: installing connman package from obcore solved all-Runtime crash at shutdown but it did not solve connmand using wpa_supplicant independent from 66 supervision when both adde to root tree.

edit2:for more insight, I post more from the wpa_supplicant log file just before the error:
2021-11-03 09:56:43.112012617  nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
2021-11-03 09:56:43.114642348  nl80211: Remove monitor interface: refcount=0
2021-11-03 09:56:43.114651250  netlink: Operstate: ifindex=3 linkmode=0 (kernel-control), operstate=6 (IF_OPER_UP)
2021-11-03 09:56:43.114706708  nl80211: Set mode ifindex 3 iftype 2 (STATION)
2021-11-03 09:56:43.114774702  nl80211: Unsubscribe mgmt frames handle 0x8888dde5228d5d39 (mode change)
2021-11-03 09:56:43.114804854  dbus: Unregister interface object '/fi/w1/wpa_supplicant1/Interfaces/3'
2021-11-03 09:56:43.114976429  dbus: bus disconnected, terminating
2021-11-03 09:56:43.114982635  dbus: Unregister D-Bus object '/fi/w1/wpa_supplicant1'
2021-11-03 09:56:43.122386267  wpa_supplicant v2.9
2021-11-03 09:56:43.122468119  dbus: Could not acquire the system bus: org.freedesktop.DBus.Error.NoServer - Failed to connect to socket /run/dbus/system_bus_socket: Connection refused
2021-11-03 09:56:43.122495886  Failed to initialize wpa_supplicant
2021-11-03 09:57:09.646778412  wpa_supplicant v2.9
2021-11-03 09:57:09.664484521  dbus: Could not acquire the system bus: org.freedesktop.DBus.Error.NoReply - Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2021-11-03 09:57:09.665328755  Failed to initialize wpa_supplicant
2021-11-03 09:57:10.536043184  wpa_supplicant v2.9
2021-11-03 09:57:10.537015354  dbus: Register D-Bus object '/fi/w1/wpa_supplicant1'
2021-11-03 09:57:10.537365932  dbus: Could not request service name: already registered
2021-11-03 09:57:10.537374211  Failed to initialize wpa_supplicant[]
Looks like there is a problem with my hardware&wpa_supplicant. No problem with 66-tools though.
I do have dbus-session@ orb in my graphics user tree working properly because packages that would otherwise require dbus-launch to work are working without it.

Good idea, Might consider using wpa_supp as module service. I have two interfaces that I use, so I dont know whether I would use 66 tools to switch between the interfaces or add two module services: wpa_supplicant@ 1 and wpa_supplicant@ 2, 1&2 representing different interfaces.
@ I is replaced by the part of the name of the instantiated service after the "@ " character, exemple:

dbus-session@ orb > @ I at the frontend file will be replaced by orb.

So if i do 66-enable wpa_supplicant@ wlan0, the frontend will be 
# ######### original frontend # #####################
[main]
@ type = classic
@ version = 0.2.0
@ description = "wpa_supplicant@ @I daemon"
@ user = ( root )
@ options = ( log env )

[start]
@ build = auto
@ execute = ( execl-cmdline -s { wpa_supplicant ${cmd_args} } )

[environment]
cmd_args=!-c/etc/wpa_supplicant/wpa_supplicant-@ I.conf -i@ I 

# ###############" final frontend at enable time # ###################
[main]
@ type = classic
@ version = 0.2.0
@ description = "wpa_supplicant@ wlan0 daemon"
@ user = ( root )
@ options = ( log env )

[start]
@ build = auto
@ execute = ( execl-cmdline -s { wpa_supplicant ${cmd_args} } )

[environment]
cmd_args=!-c/etc/wpa_supplicant/wpa_supplicant-wlan0.conf -iwlan0
This is valuable for all instantiated service even module.

Powered by Obarun