From: James Prestwood <prestwoj at gmail.com>
To: iwd at lists.01.org
Subject: Re: iwd 1.21 stuck on connecting state
Date: Thu, 03 Feb 2022 13:41:33 -0800 [thread overview]
Message-ID: <d023066c93eda551abca134bb130afeb706888e7.camel@gmail.com> (raw)
In-Reply-To: 20220203201055.3721.56890@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On Thu, 2022-02-03 at 20:10 +0000,
54d22547-afc0-4701-b1fc-5a2a2e411646(a)simplelogin.co wrote:
> > This actually got merged an hour or two ago
>
> I noticed right after posting. Classic hehe.
>
> Issue seems solved. I get connectivity and according to logs iwd is
> discarding previous DHCP requests:
>
> [DHCPv4] dhcp_client_send_discover:346
> [DHCPv4] l_dhcp_client_start:1210 Entering state:
> DHCP_STATE_SELECTING
> [DHCPv4] dhcp_client_timeout_resend:526
> [DHCPv4] dhcp_client_send_discover:346
> [DHCPv4] dhcp_client_rx_message:832
> [DHCPv4] dhcp_client_receive_offer:762
> [DHCPv4] dhcp_client_handle_offer:805 Entering state:
> DHCP_STATE_REQUESTING
> [DHCPv4] dhcp_client_send_request:396
> [DHCPv4] dhcp_client_rx_message:832
> [DHCPv4] dhcp_client_receive_offer:762
> [DHCPv4] dhcp_client_receive_offer:786 Server sent another offer,
> using it instead
Perfect, glad to see it worked.
> [DHCPv4] dhcp_client_handle_offer:805 Entering state:
> DHCP_STATE_REQUESTING
> [DHCPv4] dhcp_client_send_request:396
> [DHCPv4] dhcp_client_rx_message:832
> [DHCPv4] dhcp_client_receive_ack:684
> [DHCPv4] dhcp_client_rx_message:905 Entering state: DHCP_STATE_BOUND
> [DHCPv4] dhcp_client_rx_message:939 T1 expiring in 21600784 ms
> [DHCPv4] l_acd_start:447 Skipping probes and sending announcements
> [DHCPv4] announce_wait_timeout:166 No conflicts found for
> 192.168.1.39, announcing address
> [DHCPv4] acd_send_packet:146 sending packet with target IP
> 192.168.1.39
>
> Would you create a release soon?
Yes, I think this is happening very soon.
>
> Thanks!
> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org
next reply other threads:[~2022-02-03 21:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:41 James Prestwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-03 20:10 iwd 1.21 stuck on connecting state 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-02-03 17:28 James Prestwood
2022-02-03 16:05 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-31 22:15 James Prestwood
2022-01-31 20:09 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-31 19:31 Denis Kenzior
2022-01-31 17:28 James Prestwood
2022-01-29 20:03 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-27 19:00 James Prestwood
2022-01-27 17:51 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-18 17:39 James Prestwood
2022-01-18 11:43 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-14 20:51 James Prestwood
2022-01-14 20:08 54d22547-afc0-4701-b1fc-5a2a2e411646
2022-01-13 17:22 James Prestwood
2022-01-13 11:27 54d22547-afc0-4701-b1fc-5a2a2e411646
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=d023066c93eda551abca134bb130afeb706888e7.camel@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