From: David Laight <David.Laight@ACULAB.COM>
To: 'Dan Williams' <dcbw@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: David Ahern <dsahern@kernel.org>
Subject: RE: Getting the IPv6 'prefix_len' for DHCP6 assigned addresses.
Date: Thu, 3 Feb 2022 18:37:18 +0000 [thread overview]
Message-ID: <b3d1e478fb02420ab6414e889fd10259@AcuMS.aculab.com> (raw)
In-Reply-To: <f3c5248cd47dd38fbd215d13e430ff184df2b8d9.camel@redhat.com>
From: Dan Williams
> Sent: 03 February 2022 14:52
> > > On Wed, 2022-02-02 at 16:58 +0000, David Laight wrote:
> > > > I'm trying to work out how DHCP6 is supposed to work.
> > > >
> > > > I've a test network with the ISC dhcp6 server and radvd running.
> > > > If I enable 'autoconf' I get a nice address with the prefix from
> > > > radvd and the last 8 bytes from my mac address, prefix_len 64.
> > > > I get a nice address from dhcp6 (busybox udhcpc6) with the same
> > > > prefix.
Today it was working.
Not sure what was going on last time I tried.
But I do have to look very hard to find the IPv6 routes.
Running:
ip route show table all
does give them, but nothing else seems to.
The busybox netstat doesn't grok -6.
But I've the full version of 'ip' to get namespace support.
Talking of namespaces, is it possible to mount the namespace
version of /proc/sys/net somewhere in the filesystem?
I've got programs that really want to open nodes in the
'init' namespace and a named one.
I can use:
ip netns exec namespace program 3</proc/sys/net and
then use openat(3, "path") to get items in the 'init' namespace.
But it is a bit horrid.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2022-02-03 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-02 16:58 Getting the IPv6 'prefix_len' for DHCP6 assigned addresses David Laight
2022-02-02 18:54 ` Dan Williams
2022-02-02 22:31 ` David Laight
2022-02-03 14:51 ` Dan Williams
2022-02-03 18:37 ` David Laight [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=b3d1e478fb02420ab6414e889fd10259@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=dcbw@redhat.com \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.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).