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: Thu, 18 Jan 2024 04:18:10 -0800	[thread overview]
Message-ID: <ef97ec13-8f6c-4198-bf19-ff50a3e596f1@gmail.com> (raw)
In-Reply-To: <D88835CF-16B7-4658-8852-65C4C3767E9C@xtonomy.ai>

On 1/18/24 3:51 AM, Fabian Herb wrote:
> Hello James,
>
>> 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.
>
>> 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.
>
> Best regards,
> Fabian

  reply	other threads:[~2024-01-18 12:18 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 [this message]
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
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=ef97ec13-8f6c-4198-bf19-ff50a3e596f1@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