From: Denis Kenzior <denkenz at gmail.com>
To: iwd at lists.01.org
Subject: Re: iwd configure location and files
Date: Tue, 30 Nov 2021 17:53:40 -0600 [thread overview]
Message-ID: <070b7088-2ab6-67bf-63a1-7a1be95a58f7@gmail.com> (raw)
In-Reply-To: CAA=hcWRD26NoeS5bgZ3kdBFz2c7n=kpan2etQkXhRKv1UavYJw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 2351 bytes --]
Hi Jupiter,
> My bad, here is DHCP debugging, looks like failed to get DHCP server response:
>
> ../iwd-1.19/src/station.c:station_autoconnect_next() autoconnect:
> '34:08:04:12:b1:a2' freq: 2437, rank: 2722, strength: -6500
> ../iwd-1.19/src/station.c:station_enter_state() Old State:
> autoconnect_full, new state: connecting (auto)
> ../iwd-1.19/src/station.c:station_netdev_event() Associating
> ../iwd-1.19/src/station.c:station_handshake_event() Setting keys
> ../iwd-1.19/src/station.c:station_connect_cb() 14, result: 0
> ../iwd-1.19/src/station.c:station_connect_ok()
> netconfig: Failed to start DHCPv4 client for interface 14
> WARNING: ../iwd-1.19/src/station.c:station_connect_ok() condition
> !netconfig_configure(station->netconfig,
Ugh, not sure what happens here. First, can you update to iwd 1.20? I don't
think anything was touched around this for several releases, but I'd hate to try
and debug an old version. Also, share the full log of iwd when this happens...
Can you strace iwd and see what syscall might be failing around this time? You
may also need to step through l_dhcp_client_start to see why it is failing. It
really shouldn't under normal circumstances, hence we have no debugs in this area.
> station_netconfig_event_handler, station) failed
> [DHCPv4] dhcp_client_timeout_resend:526
> [DHCPv4] dhcp_client_send_discover:346
> [DHCPv4] dhcp_client_timeout_resend:526
> [DHCPv4] dhcp_client_send_discover:346
> [DHCPv4] dhcp_client_timeout_resend:526
> [DHCPv4] dhcp_client_send_discover:346
> [DHCPv4] dhcp_client_timeout_resend:526
> [DHCPv4] dhcp_client_send_discover:346
And this is even more strange. If l_dhcp_client_start() fails, then the resend
timer shouldn't even be set and you shouldn't even see this sequence.
Can you try compiling with optimizations off (./configure --enable-debug
--disable-optimization) and see if the behavior changes?
>
> Is netconfig from iwd?
yes
>
> I think the DHCP server is running from the home WiFi modem, right? My
> laptop is also connected to the same WiFi modem SSID JupiterIoT which
> should rule out home WiFi network DHCP server issues.
Given the fact that we fail to start dhcp client, I'm not sure we even send any
discover packets. So your server might be just fine.
Regards,
-Denis
next reply other threads:[~2021-11-30 23:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 23:53 Denis Kenzior [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-12-14 20:42 iwd configure location and files Denis Kenzior
2021-12-13 4:39 Jupiter
2021-12-02 15:47 Daniel Wagner
2021-12-01 9:24 Jupiter
2021-11-30 23:25 Jupiter
2021-11-30 22:51 Jupiter
2021-11-30 22:46 James Prestwood
2021-11-30 22:42 Denis Kenzior
2021-11-30 22:38 Jupiter
2021-11-30 22:36 KeithG
2021-11-30 22:01 Denis Kenzior
2021-11-30 21:40 James Prestwood
2021-11-30 21:29 Jupiter
2021-11-30 20:52 James Prestwood
2021-11-30 20:45 Jupiter
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=070b7088-2ab6-67bf-63a1-7a1be95a58f7@gmail.com \
--to=iwd@lists.linux.dev \
/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