From: Mauro Condarelli <mc5686@mclink.it>
To: James Prestwood <prestwoj@gmail.com>, iwd@lists.linux.dev
Subject: Re: Setup help request
Date: Tue, 2 Jan 2024 21:30:44 +0100 [thread overview]
Message-ID: <e5248b75-1615-4286-ab26-c135106f66a1@mclink.it> (raw)
In-Reply-To: <353502c4-2da3-40e8-a6b2-7535b5c864a2@gmail.com>
On 1/2/24 20:52, James Prestwood wrote:
> Hi Mauro,
>
> 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
Thanks James.
I am using standard Debian (Sid) NetworkManager client on Linux and Android client on my smartphone for testing,
but target is to provide generic network access to whoever is in range (and allowed, of course), from family devices
to security cameras.
I am already digging into hostapd, but I always wanted to promote IWD, as much as possible, so I *will* be available
for testing if you will need it.
For reference:
- my "Beelink" has `02:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)` on PCIe.
- this miniPC is used as network frontend sporting a OPNsense VM firewall and a couple of "server containers"
on DMZ, all of this virtualized under Incus (which could add noise to the issue).
- target would be to add a bridged AP connected to interface going to my internal LAN.
Thanks for all your good work and feel free to contact directly me if you need some "independent testing".
Have a Very Happy New Year!
Mauro
prev parent reply other threads:[~2024-01-02 20:45 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
2024-01-02 20:30 ` Mauro Condarelli [this message]
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=e5248b75-1615-4286-ab26-c135106f66a1@mclink.it \
--to=mc5686@mclink.it \
--cc=iwd@lists.linux.dev \
--cc=prestwoj@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).