From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 3/3] dhcp: Honour broadcast flag (RFC 2131, 4.1)
Date: Mon, 25 Nov 2024 09:30:15 +0100 [thread overview]
Message-ID: <20241125093015.6e91899b@elisabeth> (raw)
In-Reply-To: <Z0POxsviMg_kt7u_@zatzit>
On Mon, 25 Nov 2024 12:11:34 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> On Mon, Nov 25, 2024 at 01:04:23AM +0100, Stefano Brivio wrote:
> > It's widely considered a legacy option nowadays, and I've haven't seen
> > clients setting it since Windows 95, but it's convenient for a minimal
> > DHCP client not using raw IP sockets such as what I'm playing with for
> > muvm.
> >
> > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > ---
> > dhcp.c | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/dhcp.c b/dhcp.c
> > index aa0ad96..f1416ee 100644
> > --- a/dhcp.c
> > +++ b/dhcp.c
> > @@ -107,6 +107,8 @@ struct msg {
> > uint32_t xid;
> > uint16_t secs;
> > uint16_t flags;
> > +#define FLAG_BROADCAST htons_constant(0x8000)
> > +
> > uint32_t ciaddr;
> > struct in_addr yiaddr;
> > uint32_t siaddr;
> > @@ -280,10 +282,10 @@ int dhcp(const struct ctx *c, const struct pool *p)
> > {
> > size_t mlen, dlen, offset = 0, opt_len, opt_off = 0;
> > char macstr[ETH_ADDRSTRLEN];
> > + struct in_addr mask, dst;
> > const struct ethhdr *eh;
> > const struct iphdr *iph;
> > const struct udphdr *uh;
> > - struct in_addr mask;
> > unsigned int i;
> > struct msg *m;
> >
> > @@ -398,7 +400,13 @@ int dhcp(const struct ctx *c, const struct pool *p)
> > opt_set_dns_search(c, sizeof(m->o));
> >
> > dlen = offsetof(struct msg, o) + fill(m);
> > - tap_udp4_send(c, c->ip4.our_tap_addr, 67, c->ip4.addr, 68, m, dlen);
> > +
> > + if (m->flags & FLAG_BROADCAST)
> > + dst = (struct in_addr){ 0xffffffff };
>
> It would be nice to add a symbolic constant ("in4addr_broadcast"?) to
> ip.h for this.
Sure, added as in4addr_broadcast.
> > + else
> > + dst = c->ip4.addr;
> > +
> > + tap_udp4_send(c, c->ip4.our_tap_addr, 67, dst, 68, m, dlen);
> >
> > return 1;
> > }
--
Stefano
prev parent reply other threads:[~2024-11-25 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 0:04 [PATCH 0/3] dhcp: Add support for Rapid Commit, broadcast replies Stefano Brivio
2024-11-25 0:04 ` [PATCH 1/3] dhcp: Use -1 as "missing option" length instead of 0 Stefano Brivio
2024-11-25 1:08 ` David Gibson
2024-11-25 8:30 ` Stefano Brivio
2024-11-25 9:18 ` David Gibson
2024-11-25 0:04 ` [PATCH 2/3] dhcp: Introduce support for Rapid Commit (option 80, RFC 4039) Stefano Brivio
2024-11-25 1:09 ` David Gibson
2024-11-25 0:04 ` [PATCH 3/3] dhcp: Honour broadcast flag (RFC 2131, 4.1) Stefano Brivio
2024-11-25 1:11 ` David Gibson
2024-11-25 8:30 ` Stefano Brivio [this message]
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=20241125093015.6e91899b@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).