From: Peter Delevoryas <peter@pjd.dev>
To: Samuel Thibault <samuel.thibault@gnu.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, clg@kaod.org,
garnermic@fb.com, patrick@stwcx.xyz, zhdaniel@fb.com
Subject: Re: slirp: Can I get IPv6-only DHCP working?
Date: Thu, 25 Aug 2022 16:15:26 -0700 [thread overview]
Message-ID: <YwgCjqC90KhDKUnr@pdel-fedora-MJ0HJWH9> (raw)
In-Reply-To: <20220825225610.oio5h5bflp4gmaph@begin>
On Fri, Aug 26, 2022 at 12:56:10AM +0200, Samuel Thibault wrote:
> Hello,
>
> Peter Delevoryas, le jeu. 25 août 2022 15:38:53 -0700, a ecrit:
> > It seems like there's support for an IPv6 dns proxy, and there's literally a
> > file called "dhcpv6.c" in slirp, but it has a comment saying it only supports
> > whatever is necessary for TFTP network boot I guess.
>
> For which DNS support is welcome :)
>
> > Maybe there's no support then?
>
> It seems there is:
>
> if (ri.want_dns) {
> *resp++ = OPTION_DNS_SERVERS >> 8; /* option-code high byte */
> *resp++ = OPTION_DNS_SERVERS; /* option-code low byte */
> *resp++ = 0; /* option-len high byte */
> *resp++ = 16; /* option-len low byte */
> memcpy(resp, &slirp->vnameserver_addr6, 16);
> resp += 16;
> }
Well, that's great, but actually I just care about whether slirp supports DHCPv6
address requests. Sorry if I didn't explain that properly.
My goal is to run:
qemu-system-arm -machine fby35-bmc -nographic -mtdblock image-bmc \
-net nic,model=ftgmac100,netdev=nic \
-netdev user,id=nic,hostfwd=::2222-:22
And then see that the BMC received an IPv6 address assignment.
But, slirp currently just supports IP address assignment through BOOTP? I
didn't realize that until looking a little closer at the code. But, since the
DHCPv6 hook "dhcpv6_input" is already there, maybe I can just get something
going through there? I suppose I might need some IPv6 NDP packets to work too,
to ssh through a hostfwd port.
root@bmc-oob:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr FA:CE:B0:02:20:22
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fec0::f8ce:b0ff:fe02:2022/64 Scope:Site
inet6 addr: fe80::f8ce:b0ff:fe02:2022/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:107 errors:0 dropped:0 overruns:0 frame:0
TX packets:136 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:13316 (13.0 KiB) TX bytes:10022 (9.7 KiB)
Interrupt:33
Anyways, I'll do some more investigation on my own, thanks!
Peter
>
> Samuel
next prev parent reply other threads:[~2022-08-25 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:38 slirp: Can I get IPv6-only DHCP working? Peter Delevoryas
2022-08-25 22:56 ` Samuel Thibault
2022-08-25 23:15 ` Peter Delevoryas [this message]
2022-08-25 23:20 ` Samuel Thibault
2022-08-26 7:21 ` Thomas Huth
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=YwgCjqC90KhDKUnr@pdel-fedora-MJ0HJWH9 \
--to=peter@pjd.dev \
--cc=clg@kaod.org \
--cc=garnermic@fb.com \
--cc=patrick@stwcx.xyz \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.org \
--cc=zhdaniel@fb.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.