From: James Prestwood <prestwoj@gmail.com>
To: "Rafael Ávila de Espíndola" <rafael@espindo.la>, iwd@lists.linux.dev
Subject: Re: Making udhcpc get a new lease when iwd connects to a network
Date: Mon, 22 Jan 2024 04:21:33 -0800 [thread overview]
Message-ID: <e1a35af8-0c7c-450b-9d96-fa8987e4c0d4@gmail.com> (raw)
In-Reply-To: <87h6j670ye.fsf@espindo.la>
Hi Rafael,
On 1/21/24 2:53 PM, Rafael Ávila de Espíndola wrote:
> Hi,
>
> I know that iwd has a builtin dhcp client, but I am using it in alpine
> linux and would like to use the same dhcp client with both wired and
> wireless interfaces. The default client in alpine is udhcpc.
>
> As far as I can tell, the impedance mismatch between udhcpc and iwd is
> that udhcpc expect commands via unix signals and iwd send property
> changes via dbus.
>
> I wrote a bit of glue code and posted it to
> https://codeberg.org/espindola/iwd2udhcpc. It works, at least on my
> laptop, but I am wondering if anyone knows of a simpler way.
I think the intended way is for the DHCP daemon to listen for the
interface to set carrier up (from RTNL). This is how systemd-networkd
does it, and AFAIK dhcpd. I'm surprised udhcpd doesn't although I
suspect since its heavily stripped down they leave it up to some other
entity to tell it to start.
Listening for IWD's connected state is effectively the same thing. One
thing to keep in mind is you don't want to start DHCP again when
transitioning from roaming->connected.
>
> Thanks,
> Rafael
>
next prev parent reply other threads:[~2024-01-22 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 22:53 Making udhcpc get a new lease when iwd connects to a network Rafael Ávila de Espíndola
2024-01-22 12:21 ` James Prestwood [this message]
2024-01-22 15:01 ` Denis Kenzior
2024-01-22 20:59 ` Rafael Ávila de Espíndola
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=e1a35af8-0c7c-450b-9d96-fa8987e4c0d4@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=rafael@espindo.la \
/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