Wireless Daemon for Linux
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: Mauro Condarelli <mc5686@mclink.it>, iwd@lists.linux.dev
Subject: Re: Setup help request
Date: Tue, 2 Jan 2024 11:52:01 -0800	[thread overview]
Message-ID: <353502c4-2da3-40e8-a6b2-7535b5c864a2@gmail.com> (raw)
In-Reply-To: <d747eb7b-f345-4867-9dbb-738535bab25c@mclink.it>

Hi Mauro,

On 1/2/24 9:45 AM, Mauro Condarelli wrote:
>
>
> On 1/2/24 18:30, James Prestwood wrote:
>>
>> On 1/2/24 9:09 AM, Mauro Condarelli wrote:
>>> Thanks James,
>>> comments inline below.
>>>
>>>
>>> On 1/2/24 16:36, James Prestwood wrote:
>>>> Hi Mauro,
>>>>
>>>> On 1/2/24 7:11 AM, Mauro Condarelli wrote:
>>>>> SNIP!
>>>>>
>>>>
>>>> Ok, so I'm not seeing any request to even connect from the AP side 
>>>> of things. Since your clients aren't even asking for a password I 
>>>> suspect it thinks there is some issue with compatibility. You could 
>>>> try using hostapd with a very basic configuration and see if that 
>>>> works, then we can go from there:
>>>>
>>>> hw_mode=g
>>>> channel=1
>>>> ssid=testssid
>>>>
>>>> wpa=1
>>>> wpa_pairwise=TKIP
>>>> wpa_passphrase=secret123
>>>>
>>> I had to add `interface=wlan0`, but that works... almost.
>>>
>>> It actually asks for password, connects and then fails because 
>>> there's (currently) no DHCP active (so no IP).
>>> I think that's expected.
>>> Behavior is the same with both clients.
>>>
>>> Do you have any further suggestions?
>>
>> Ok perfect, at least it connected. Could you run iwmon before hostapd 
>> and connect (same as you did with IWD), and send me those pcaps/logs. 
>> I'll be able to compare and see what its doing differently.
> I changed the script to:
>
> #!/bin/bash
>
> iwmon --write /tmp/iwmon.pcap >/tmp/iwmon.log 2>&1 &
> IWMON_PID=$!
> systemctl start hostapd
>
> mc
>
> systemctl stop hostapd
> kill $IWMON_PID
>
> cd /tmp
> tar cJf iw.tar.xz iwmon.pcap iwmon.log

Thanks for doing this. I do see some slight differences between hostapd 
and IWD but its difficult to know exactly what is causing the problem. 
Hostapd is very old compared to IWD and has had a lot of time to get 
working with every possible driver and client device. This also means 
there is a lot of extra cruft that has no effect anymore. I hate to 
"mimic" hostapd to a tee because it would likely add unnecessary bloat. 
What client devices are you using to connect? Also, what wifi hardware 
is in your beelink miniPC? maybe I have something similar I can try and 
replicate the issue.

For the time being it may be easier to use hostapd for your specific 
needs. As I said AP mode is experimental in IWD, and my day-to-day work 
priorities aren't really with AP mode. I can poke around with it on the 
side, and maybe provide patches to try out sometime in the future.

Thanks,

James

>
>
>>
>>>
>>> TiA!
>>> Mauro
>>

  reply	other threads:[~2024-01-02 19:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-01 19:26 Setup help request Mauro Condarelli
2024-01-01 23:03 ` James Prestwood
2024-01-02  0:34   ` Mauro Condarelli
2024-01-02 13:01     ` James Prestwood
2024-01-02 14:07       ` Mauro Condarelli
2024-01-02 14:40         ` James Prestwood
2024-01-02 17:10           ` Denis Kenzior
2024-01-02 15:11         ` Mauro Condarelli
2024-01-02 15:36           ` James Prestwood
2024-01-02 17:09             ` Mauro Condarelli
2024-01-02 17:30               ` James Prestwood
2024-01-02 17:45                 ` Mauro Condarelli
2024-01-02 19:52                   ` James Prestwood [this message]
2024-01-02 20:30                     ` Mauro Condarelli

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=353502c4-2da3-40e8-a6b2-7535b5c864a2@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    --cc=mc5686@mclink.it \
    /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