Re: Problems attempting to use ad-hoc mode, link state remains dormant

Re: Problems attempting to use ad-hoc mode, link state remains dormant

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 438 bytes --]

Hi Diego,

> However, I have another device with an Atheros QCA6174 (ath10k_pci driver) and if I put it into ap mode no other station sees it (Windows laptop, Linux laptop, iPhone). Do you know if there is anything special to do to use ap mode on these devices?
> 

I'm not aware of any, but admittedly we're not actively focused on AP 
mode at the moment, so it is a 'less developed' area of the iwd codebase.

Regards,
-Denis

RE: Problems attempting to use ad-hoc mode, link state remains dormant

[Diego Santa Cruz]

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]

Hi Denis,
> Hi Diego,
> 
> > However, I have another device with an Atheros QCA6174 (ath10k_pci
> driver) and if I put it into ap mode no other station sees it (Windows laptop,
> Linux laptop, iPhone). Do you know if there is anything special to do to use ap
> mode on these devices?
> >
> 
> I'm not aware of any, but admittedly we're not actively focused on AP
> mode at the moment, so it is a 'less developed' area of the iwd codebase.

OK, got it. I actually just tried out using hostapd instead and it works nicely with the above wireless card, I could successfully connect from my iPhone (open, no auth).

BTW, could you share what is the status of the wired 802.1x support? Is it something that can be relied upon?
 
Best,
Diego

-- 
Diego Santa Cruz, PhD
Technology Architect
spinetix.com

Re: Problems attempting to use ad-hoc mode, link state remains dormant

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

Hi Diego,

>> The tricky part is that adhoc doesn't initialize its own rtnl object, so
>> I need to think about a good fix for this.
>>
> 
> Thanks for the information, indeed it looked to me that there was something missing but I could not really figure it out for sure from the code. I do not think I can help out there.

This should now be fixed upstream.

Regards,
-Denis

RE: Problems attempting to use ad-hoc mode, link state remains dormant

[Diego Santa Cruz]

[-- Attachment #1: Type: text/plain, Size: 813 bytes --]

> -----Original Message-----
> From: Denis Kenzior <denkenz@gmail.com>
> Sent: 08 April 2020 23:35
> To: Diego Santa Cruz <Diego.SantaCruz@spinetix.com>; iwd(a)lists.01.org
> Subject: Re: Problems attempting to use ad-hoc mode, link state remains
> dormant
> 
> Hi Diego,
> 
> >> The tricky part is that adhoc doesn't initialize its own rtnl object, so
> >> I need to think about a good fix for this.
> >>
> >
> > Thanks for the information, indeed it looked to me that there was
> something missing but I could not really figure it out for sure from the code. I
> do not think I can help out there.
> 
> This should now be fixed upstream.

Great! I gave it quick test to the patches and it works.

Many thanks,

Diego

-- 
Diego Santa Cruz, PhD
Technology Architect
spinetix.com

Re: Problems attempting to use ad-hoc mode, link state remains dormant

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

Hi Diego,

> BTW, could you share what is the status of the wired 802.1x support? Is it something that can be relied upon?

Not sure what to say?  It works on the networks we have access to.  Are 
there improvements that can be made? Sure..

The last question I can't really comment on.  This is an open source 
project and comes with no warranties.  You'll have to perform your own 
due diligence to answer that.

Regards,
-Denis

RE: Problems attempting to use ad-hoc mode, link state remains dormant

[Diego Santa Cruz]

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

Hi Denis,
> 
> Hi Diego,
> 
> > BTW, could you share what is the status of the wired 802.1x support? Is it
> something that can be relied upon?
> 
> Not sure what to say?  It works on the networks we have access to.  Are
> there improvements that can be made? Sure..
> 
> The last question I can't really comment on.  This is an open source
> project and comes with no warranties.  You'll have to perform your own
> due diligence to answer that.
> 

Thanks as I could not find much info on the status of the wired 802.1x on iwd or documentation I was not sure that if it was at a "proof of concept" level or if it was working. Given your answer I will go ahead and try it out for integration into our product.

I was not looking for any warranties, just your feeling about the level of development. I will report any problems that I find, with patches if possible :-)

Thanks for your help.

Best,

Diego

-- 
Diego Santa Cruz, PhD
Technology Architect
spinetix.com

Re: Problems attempting to use ad-hoc mode, link state remains dormant

[Denis Kenzior]

[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]

Hi Diego,

> However, “ip link show dev wlan0" shows “NO-CARRIER” on both devices 
> with state DORMANT and mode DORMANT.
> 
> 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq 
> state DORMANT mode DORMANT group default qlen 1000
> 
>      link/ether 34:e1:2d:24:03:42 brd ff:ff:ff:ff:ff:ff
> 
> When doing it manually with iw the state was UP and the mode DEFAULT, so 
> I manually changed the state with “ip link set wlan0 state up". After 
> that “ip link” no longer shows NO-CARRIER and pings worked. Changing the 
> mode was not necessary.
> 
> Is there something that I am missing? Or maybe something which is 
> missing in iwd in adhoc mode?

This is indeed a bug in iwd.  We somehow missed sending the required 
linkmode / operstate changes when adhoc is operated in the 'open' mode. 
i.e. a call to l_rtnl_set_linkmode_and_operstate is missing in 
src/adhoc.c adhoc_new_station() around line 415.

The tricky part is that adhoc doesn't initialize its own rtnl object, so 
I need to think about a good fix for this.

Regards,
-Denis

RE: Problems attempting to use ad-hoc mode, link state remains dormant

[Diego Santa Cruz]

[-- Attachment #1: Type: text/plain, Size: 1853 bytes --]

> Hi Diego,
> 
> > However, "ip link show dev wlan0" shows "NO-CARRIER" on both devices
> > with state DORMANT and mode DORMANT.
> >
> > 5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
> qdisc mq
> > state DORMANT mode DORMANT group default qlen 1000
> >
> >      link/ether 34:e1:2d:24:03:42 brd ff:ff:ff:ff:ff:ff
> >
> > When doing it manually with iw the state was UP and the mode DEFAULT,
> so
> > I manually changed the state with "ip link set wlan0 state up". After
> > that "ip link" no longer shows NO-CARRIER and pings worked. Changing the
> > mode was not necessary.
> >
> > Is there something that I am missing? Or maybe something which is
> > missing in iwd in adhoc mode?
> 
> This is indeed a bug in iwd.  We somehow missed sending the required
> linkmode / operstate changes when adhoc is operated in the 'open' mode.
> i.e. a call to l_rtnl_set_linkmode_and_operstate is missing in
> src/adhoc.c adhoc_new_station() around line 415.
> 
> The tricky part is that adhoc doesn't initialize its own rtnl object, so
> I need to think about a good fix for this.
> 

Thanks for the information, indeed it looked to me that there was something missing but I could not really figure it out for sure from the code. I do not think I can help out there.

I am looking into ap mode now and I got it to work by putting the either the Intel AC 9260 or Intel 8265 / 8275 (that is putting either in ap mode and connection from the other in station mode work fine).

However, I have another device with an Atheros QCA6174 (ath10k_pci driver) and if I put it into ap mode no other station sees it (Windows laptop, Linux laptop, iPhone). Do you know if there is anything special to do to use ap mode on these devices?

Best,
Diego

 
-- 
Diego Santa Cruz, PhD
Technology Architect
spinetix.com
 

Problems attempting to use ad-hoc mode, link state remains dormant

[Diego Santa Cruz]

[-- Attachment #1: Type: text/plain, Size: 2277 bytes --]

Hello,

I am trying to establish an ad-hoc connection between two Linux devices using iwd but so far I have not had any success without manual intervention. In short the link state remains dormant and no packets can be sent.

I succeeded to do it manually with iw inspiring me from https://wiki.lm-technologies.com/linux-wifi-ad-hoc-mode/. I did the following on each of the devices (iwd was not running).

  *   iw phy phy0 interface add ibs0 type ibss
  *   ip link set ibs0 up
  *   iw dev ibs0 ibss join ibstest 2437

After a few seconds the two devices connected and "iw dev ibs0 link" showed (same MAC address on both)
Joined IBSS 86:ac:e8:60:15:f3 (on ibs0)
                SSID: ibstest
                freq: 2437
And "ip link show dev ibs0" shows
5: ibs0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 3c:6a:a7:51:6d:dd brd ff:ff:ff:ff:ff:ff

And I can successfully ping the local-link IPv6 address of the other device.

With iwd I do the following to establish ad-hoc networking.

  *   Reboot to start with a clean state
  *   Start iwd
  *   iwctl device wlan0 set-property Mode ad-hoc
  *   iwctl ad-hoc wlan0 start_open ibstest

A few seconds later the two devices do connect, I see the a "new Station" message from one of the iwd, and "iw dev wlan0 link" shows the same MAC address on both devices, so as far as I understand they are joined.

However, "ip link show dev wlan0" shows "NO-CARRIER" on both devices with state DORMANT and mode DORMANT.
5: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state DORMANT mode DORMANT group default qlen 1000
    link/ether 34:e1:2d:24:03:42 brd ff:ff:ff:ff:ff:ff

When doing it manually with iw the state was UP and the mode DEFAULT, so I manually changed the state with "ip link set wlan0 state up". After that "ip link" no longer shows NO-CARRIER and pings worked. Changing the mode was not necessary.

Is there something that I am missing? Or maybe something which is missing in iwd in adhoc mode?

One of the devices is using an Intel Wireless AC 9260 and the other one an Intel Wireless 8265 / 8275.

Thanks,

Diego

--
Diego Santa Cruz, PhD
Technology Architect
spinetix.com


[-- Attachment #2: attachment.htm --]
[-- Type: text/html, Size: 10996 bytes --]