From: James Prestwood <prestwoj at gmail.com>
To: iwd at lists.01.org
Subject: Re: iwd 1.21 stuck on connecting state
Date: Tue, 18 Jan 2022 09:39:22 -0800 [thread overview]
Message-ID: <a37fbc925b5695daedd33be9f110d13d2776eaf3.camel@gmail.com> (raw)
In-Reply-To: 20220118114332.2807.583@ml01.vlan13.01.org
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi,
It looks like the DHCP server sent some packet that we did not accept.
There isn't enough debug printing to know what exactly so we'll need to
get a network capture PCAP and see what data it sent. You can use
tcpdump/wireshark to get this. Just ensure you see DHCP packets in the
capture.
Something like:
tcpdump -i <iface> port 67 or port 68 -s 0 -w dhcp.pcap
Thanks,
James
On Tue, 2022-01-18 at 11:43 +0000,
54d22547-afc0-4701-b1fc-5a2a2e411646(a)simplelogin.co wrote:
> These are the logs with IWD_DHCP_DEBUG=1.
>
> https://termbin.com/yn9k
>
> On first attempt I didn't manage to get a connection due to DHCP, but
> after stopping/starting it worked.
> _______________________________________________
> 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-01-18 17:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 17:39 James Prestwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-03 21:41 iwd 1.21 stuck on connecting state James Prestwood
2022-02-03 20:10 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 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=a37fbc925b5695daedd33be9f110d13d2776eaf3.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