Hi,
On Wed, 2015-08-26 at 16:54 +, Adam Moore wrote:
> In September, there was a discussion on how we should handle a situation
> where an autoconnect fails due to receipt of a connect-failed error, which
> can be seen in difficult RF environments.
>
> I understand the current recove
In September, there was a discussion on how we should handle a situation
where an autoconnect fails due to receipt of a connect-failed error, which
can be seen in difficult RF environments.
I understand the current recovery mechanism where we let wpa_supplicant
age off BSSs during a sufficiently l
Hi Marcel,
There should be no need to modify ConnMan in this case.
Besides the ugly hack they have been told to investigate, I don't think
ConnMan supports being 2 GO at same time on the same phy, not to say
about being on 2.4 on one, and 5 on the other. A the time things were
implemented,
Hi Debojyoti,
>> This should work with one wpa_supplicant, unless the chip vendor's driver is
>> weirdly done.
>> Afaik, intel or atheros work properly, but if it's none of those... ;)
> Unfortunately our chip is not Intel nor Atheros and the chip vendor suggested
> that with one supplicant this
Hello,
> This should work with one wpa_supplicant, unless the chip vendor's driver is
> weirdly done.
>Afaik, intel or atheros work properly, but if it's none of those... ;)
Unfortunately our chip is not Intel nor Atheros and the chip vendor suggested
that with one supplicant this use case can't
Hi,
Just now got the go ahead about disclosing the use cases.
Our requirement is having two P2P GO, one at 2.4 Ghz and another 5 Ghz in
parallel, and our chip vendor confirmed that will only be possible by using two
Supplicants.
This should work with one wpa_supplicant, unless the chip vend
Hello Patrik,
I have already disclosed the usa case in another mail, but no problem
disclosing it here again:
Our requirement is to configure one WLAN chip into two P2P GO, one at 2.4 Ghz
and another 5 Ghz in parallel. Our chip vendor confirmed that will only be
possible by using two Supplican
On Wed, 2015-08-26 at 12:41 +, Pal, Debojyoti wrote:
> Yes you are correct, it is really dirty hack, but we don't have any
> choice. Regarding the use cases, it is very specific to a customer
> program, I need to get go ahead from them before disclosing the use
> case. But for sure we have to u
Hello Thomasz,
Just now got the go ahead about disclosing the use cases.
Our requirement is having two P2P GO, one at 2.4 Ghz and another 5 Ghz in
parallel, and our chip vendor confirmed that will only be possible by using two
Supplicants.
Regards,
Debojyoti
-Original Message-
From: c
Hello Thomasz,
Yes you are correct, it is really dirty hack, but we don't have any choice.
Regarding the use cases, it is very specific to a customer program, I need to
get go ahead from them before disclosing the use case. But for sure we have to
use two supplicants.
Regards,
Debojyoti
That's quite a dirty hack actually.
And you still did not tell what is the use case, what's the context etc...
Tomasz
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman
Hello Patrik,
We will modify WPA Supplicant to register them with two different D-Bus, that
we have already tested, it is working.
Regards,
Debojyoti
-Original Message-
From: connman [mailto:connman-boun...@connman.net] On Behalf Of Patrik Flykt
Sent: Wednesday, August 26, 2015 5:51 PM
On Wed, 2015-08-26 at 11:36 +, Pal, Debojyoti wrote:
> As I told we have to use two supplicants, also existing ConnMan
> doesn't support two Supplicant till now, so we have to find the way to
> use two Supplicants in ConnMan.
That won't work, ever. Both wpa_supplicant instances will try to
reg
On Wed, 2015-08-26 at 11:36 +, Pal, Debojyoti wrote:
> As I told we have to use two supplicants, also existing ConnMan
> doesn't support two Supplicant till now, so we have to find the way to
> use two Supplicants in ConnMan.
There is no need to use two wpa_supplicants with ConnMan. If you us
Hi,
As long as you don't explain exactly the use case (the frequencies, the
modes...), I won't be convinced you really need 2 wpa_supplicant.
Usually, this is because people use it from command line and that is
quite painful to make it work for multiple cards yes.
(ConnMan uses it's DBus interf
Hello Tomasz,
As I told we have to use two supplicants, also existing ConnMan doesn't support
two Supplicant till now, so we have to find the way to use two Supplicants in
ConnMan.
Regards,
Debojyoti
-Original Message-
From: connman [mailto:connman-boun...@connman.net] On Behalf Of Tom
Hi,
Our requirement is to use two supplicants to handle two concurrent Wi-Fi roles
in different frequencies, this is very specific use cases and we don't have any
other choice but to use two supplicants to achieve that use case.
Now question is what should be the cleaner way to handle this sit
Hello Tomasz,
Thanks for quick response.
Our requirement is to use two supplicants to handle two concurrent Wi-Fi roles
in different frequencies, this is very specific use cases and we don't have any
other choice but to use two supplicants to achieve that use case.
Now question is what should b
Hi,
For one of our project we have to use two WPA Supplicants for some specific use
cases, now I would like to know what would be the better approach, using single
ConnMan with two Supplicant or two Connman with two Supplicant?
What I have understood by going through the Connman source code th
Hello,
For one of our project we have to use two WPA Supplicants for some specific use
cases, now I would like to know what would be the better approach, using single
ConnMan with two Supplicant or two Connman with two Supplicant?
What I have understood by going through the Connman source code
20 matches
Mail list logo
