public inbox for iwd@lists.linux.dev
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Fabian Herb <fabian.herb@xtonomy.ai>
Cc: "iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: How to Autoconnect Two WiFi Cards?
Date: Tue, 23 Jan 2024 06:15:16 -0800	[thread overview]
Message-ID: <d8e965da-ae8b-45cf-b29b-2b75faa73805@gmail.com> (raw)
In-Reply-To: <E8931256-9BC5-4563-8A26-6A346560F34A@xtonomy.ai>

Hi Fabian,

On 1/23/24 5:36 AM, Fabian Herb wrote:
> Hi James,
>
>> Am 18.01.2024 um 13:18 schrieb James Prestwood <prestwoj@gmail.com>:
>>
>> On 1/18/24 3:51 AM, Fabian Herb wrote:
>>>> Without implementing a new feature with per-phy profiles about the only thing you could do would be:
>>>>
>>>>   - Create a network namespace (e.g. ns0)
>>> Thanks! I’ll look into that idea. At a first glance it looks quite cumbersome though. Maybe this could be done with LXC or Docker...
>> Yeah I actually hesitated to even suggest it :) Though once you've done it its not _that_ bad. We do this in our autotests framework to simulate networks, and run multiple instances of IWD. You may be able to do it with a container as well.
> I tried with systemd-nspawn, but that didn't work so well. For one you can’t put the phy into the container with the provided tools because it’s not a regular network interface (setting the ns manually works though). And also starting iwd inside the container gives me a „Module rfkill failed to start: -2“, even if I bind /dev/rfkill into the container…
I only ever did this with low level namespaces, but yeah, its a quirky 
setup to achieve what you want.
>
> I’m starting to think that it might be easier to add a feature to iwd that does what I want :). But I’m still a bit lost in the source code.
>
>>>> What exactly are you trying to accomplish by connecting to separate SSID’s?
>>> That’s for redundancy. The machine is moving around quite a bit, so there’s lots of roaming. Reception can be bad in some areas. And with two WiFi connections and 802.11r Fast Transition if possible, I hope to get network interruptions close to zero. Redundancy itself is done on application level.
>> So this very same thing is being added in WiFi 7, called Multi-Link Operation (MLO). It doesn't help you now as IWD doesn't have any logic for it but just putting it out there (and maybe AP support is also needed). They've been working on this feature in the kernel for quite some time now.
> Yes, WiFi 7 is certainly interesting. You can already buy WiFi-7-capable hardware now. UniFi promises MLO support to be available in February with a firmware update for example.
>
> Is there a time frame when MLO support might be added to iwd? Or is the work on kernel support still ongoing?

It very much seems like its in active development in the 
kernel/wpa_supplicant. There time-frame to add it to IWD but at the very 
least we'd want the kernel support to be stable. Another factor to 
adding larger features, simply put, is corporate agendas. Unfortunately, 
gone are the days of us IWD devs getting paid to add whatever we want, 
whenever we want (that's at least my situation).

So as for MLO yes I could see it being added at some point, but its not 
really a priority. My company is just now starting to add WiFi 6e. When 
WiFi 7 becomes more widespread I could probably get MLO support on the 
agenda as it seems like it would add connection reliability but I won't 
lie, its a long way off. Anyone else is welcome to implement before then 
though :)

Thanks,

James

>
> Best regards,
> Fabian
>

  reply	other threads:[~2024-01-23 14:15 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 [this message]
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
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=d8e965da-ae8b-45cf-b29b-2b75faa73805@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=fabian.herb@xtonomy.ai \
    --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