All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj at gmail.com>
To: iwd at lists.01.org
Subject: Re: iwd 1.21 stuck on connecting state
Date: Mon, 31 Jan 2022 14:15:41 -0800	[thread overview]
Message-ID: <693ddbdafd550d947e1e9a2e4e36685a9a0de4c2.camel@gmail.com> (raw)
In-Reply-To: 20220129200358.2828.46152@ml01.vlan13.01.org

[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]

Hi,

On Sat, 2022-01-29 at 20:03 +0000,
54d22547-afc0-4701-b1fc-5a2a2e411646(a)simplelogin.co wrote:
> Sorry, didn't know that. I reproduced the problem again and uploaded
> the file here: https://transfer.sh/get/jiEvOg/dhcp.pcap
> 
> Hope this helps!

Below is a patch for ELL [1]. If its possible for you to apply it and
rebuild both IWD/ELL manually to test that would be great. The issue
should be solved but you will see an additional print when you normally
would see IWD hang and never get connected:

"Server sent another offer, using it instead"

Note: IWD_DHCP_DEBUG has to be enabled to see this.

If you are able to get a log showing this behavior we can mark this as
fixed, otherwise we can wait till this patch is in a release and see if
it fixed the issue then. Thanks for your help so far.

[1]
https://lists.01.org/hyperkitty/list/ell(a)lists.01.org/thread/DJHXIOGGOCGGFUD2E3N2XVXCUAO2X2UP/

> _______________________________________________
> iwd mailing list -- iwd(a)lists.01.org
> To unsubscribe send an email to iwd-leave(a)lists.01.org


             reply	other threads:[~2022-01-31 22:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 22:15 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 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=693ddbdafd550d947e1e9a2e4e36685a9a0de4c2.camel@gmail.com \
    --to=unknown@example.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.