>> 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.
Instead of calling display(""), explicitly use the sequence of
commands to force readline to properly update its internal state
and re-display the prompt.
client/display.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/client/display.c b/client/display.c
index 4bcf51a2..cf74326d 100644
@@ -534,7 +534,14 @@ void display_enable_cmd_prompt(void)
+ * The following sequence of rl_* commands forces readline to properly
+ * update its internal state and re-display the new prompt.
> 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.
> 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.
> 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.