From: Benjamin Drung <benjamin.drung@profitbricks.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, Benjamin Drung <benjamin.drung@profitbricks.com>
Subject: [Qemu-devel] [PATCH 0/1] slirp: Add domainname option to slirp's DHCP server
Date: Fri, 16 Feb 2018 13:55:03 +0100 [thread overview]
Message-ID: <20180216125504.25955-1-benjamin.drung@profitbricks.com> (raw)
Hi,
The DHCP server in QEMU does neither support specifying a domainname nor
a classless static route option [1]. I implemented the former (which was easy),
but I am not sure if and how to implement the classless static route option.
An example classless static route option configured in ISC's DHCP server look
like
option rfc3442-classless-static-routes 24, 10, 0, 2, 10, 0, 2, 2, 16, 192, 168, 10, 0, 2, 2;
This translates to the routes:
10.0.2.0/24 via 10.0.2.2
192.168.0.0/16 via 10.0.2.2
Should the command line option just behave like the ISC's DHCP server and
allow specifying the byte stream passed to the client? E.g.
-net staticroutes=24.10.0.2.10.0.2.2.16.192.168.10.0.2.2
Or should the command line option be simpler, but how should it be specified
then? Maybe
-net staticroute=10.0.2.0/24via10.0.2.2,staticroute=192.168.0.0/16via10.0.2.2
I am open for your ideas.
[1] https://tools.ietf.org/html/rfc3442
Benjamin Drung (1):
slirp: Add domainname option to slirp's DHCP server
net/slirp.c | 7 ++++---
qapi/net.json | 3 +++
qemu-options.hx | 7 +++++--
slirp/bootp.c | 8 ++++++++
slirp/libslirp.h | 2 +-
slirp/slirp.c | 4 +++-
slirp/slirp.h | 1 +
7 files changed, 25 insertions(+), 7 deletions(-)
--
2.14.1
next reply other threads:[~2018-02-16 13:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 12:55 Benjamin Drung [this message]
2018-02-16 12:55 ` [Qemu-devel] [PATCH 1/1] slirp: Add domainname option to slirp's DHCP server Benjamin Drung
2018-02-16 15:15 ` Eric Blake
2018-02-16 15:18 ` Benjamin Drung
2018-02-16 17:55 ` [Qemu-devel] [PATCH v2] " Benjamin Drung
2018-02-16 19:23 ` Philippe Mathieu-Daudé
2018-02-16 19:32 ` Benjamin Drung
2018-02-27 16:04 ` Benjamin Drung
2018-02-27 16:06 ` [Qemu-devel] [PATCH 1/2 v4] " Benjamin Drung
2018-02-27 16:06 ` [Qemu-devel] [PATCH 2/2] slirp: Add classless static routes support to " Benjamin Drung
2018-03-04 21:06 ` Samuel Thibault
2018-03-08 18:57 ` [Qemu-devel] [PATCH 2/2 v2] " Benjamin Drung
2018-03-08 19:46 ` Eric Blake
2018-03-08 20:07 ` Benjamin Drung
2018-03-08 20:21 ` Eric Blake
2018-03-14 19:07 ` Benjamin Drung
2018-03-04 20:43 ` [Qemu-devel] [PATCH 1/2 v4] slirp: Add domainname option to slirp's " Samuel Thibault
2018-02-26 15:52 ` [Qemu-devel] [PATCH v3] " Benjamin Drung
2018-02-17 21:16 ` [Qemu-devel] [PATCH 0/1] " Samuel Thibault
2018-02-27 16:15 ` Benjamin Drung
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=20180216125504.25955-1-benjamin.drung@profitbricks.com \
--to=benjamin.drung@profitbricks.com \
--cc=jan.kiszka@siemens.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@ens-lyon.org \
/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;
as well as URLs for NNTP newsgroup(s).