From: Fabian Herb <fabian.herb@xtonomy.ai>
To: Denis Kenzior <denkenz@gmail.com>
Cc: "iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: How to Autoconnect Two WiFi Cards?
Date: Wed, 24 Jan 2024 16:07:18 +0000 [thread overview]
Message-ID: <A3545185-22E7-4491-AD80-FFF9FEDCB8F1@xtonomy.ai> (raw)
In-Reply-To: <d3ccf10a-72a8-43b8-8f1c-b5e2a76214ac@gmail.com>
Hi Denis,
> - When considering a network, first check whether a network with the same SSID/security type is being connected to by other stations managed by iwd
> - This should be easy to do by looping of the station_list and checking connected_network / connected_bss members of struct station.
> - If the networks match, just skip it and continue on to the next autoconnect target.
> - This should result in each station object connecting to a different SSID. Once latched onto the SSID, station will try to roam only within that network.
Thanks for the hint! But wouldn’t that mean that it’s basically random which interface connects to which SSID? Right now I’m configuring IPs and routing via systemd-networkd for each interface, and that would stop working if the two interfaces are connected the wrong way around. The approach also screams for race conditions :D.
I was thinking about something like this:
- Add a configuration option to the network file format which holds an interface name
- When iterating the list of networks to autoconnect to, skip the entries for which the interface name is set AND it does not match the current interface.
> Well, it could work, but you'd be running multiple dbus instances and there wouldn't be any coordination between iwds. Also, you'd have to make sure each iwd instance runs with a different state directory and probably different config file (for band preferences). See 'man 8 iwd' for details on how to do that. Another hint, ell already honors DBUS_SYSTEM_BUS_ADDRESS environment variable. So you can start multiple dbus instances, record the address and point each iwd to the dbus instance via DBUS_SYSTEM_BUS_ADDRESS environment variable. No need to change any code inside iwd.
I’ll give DBUS_SYSTEM_BUS_ADDRESS a try, thanks!
Fabian
next prev parent reply other threads:[~2024-01-24 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-16 16:48 How to Autoconnect Two WiFi Cards? Fabian Herb
2024-01-16 17:15 ` James Prestwood
2024-01-18 11:51 ` Fabian Herb
2024-01-18 12:18 ` James Prestwood
2024-01-23 13:36 ` Fabian Herb
2024-01-23 14:15 ` James Prestwood
2024-01-23 16:15 ` Denis Kenzior
2024-01-24 12:34 ` Fabian Herb
2024-01-24 15:21 ` Denis Kenzior
2024-01-24 16:07 ` Fabian Herb [this message]
2024-01-24 16:18 ` Denis Kenzior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A3545185-22E7-4491-AD80-FFF9FEDCB8F1@xtonomy.ai \
--to=fabian.herb@xtonomy.ai \
--cc=denkenz@gmail.com \
--cc=iwd@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox