On Tue 14 Mar 2023 at 17:06:19 (+0800), jeremy ardley wrote:
> On 14/3/23 16:21, Tim Woodall wrote:
> > On Tue, 14 Mar 2023, Jeremy Ardley wrote:
> > > I conclude there is no IPv6 DHCP involved but there must be
> > > something that listens to RA announcements and generates a MAC
> > > derived address from that.
> > > 
> > > I still need to know how to control that as there are options
> > > relating to privacy that can do things like generate an
> > > expendable address in a different way and later generate
> > > another and deprecate earlier addresses.
> > 
> > Just add them to the ipv6 section.
> > 
> > I have
> > 
> > iface xenbr0-active inet6 auto
> >         up echo 64
> > >/proc/sys/net/ipv6/conf/$IFACE/accept_ra_rt_info_max_plen
> >         up ip token set ::128/64 dev $IFACE
> >         bridge_ports usb0
> >         bridge_stp off       # disable Spanning Tree Protocol
> >         bridge_waitport 0    # no delay before a port becomes available
> >         bridge_fd 0          # no forwarding delay

I didn't receive that post, and perhaps I wouldn't understand it
anyway until I'm running bookworm.

> I had hoped (not very hopefully) the solution wouldn't involve bashing
> kernel parameters.
> 
> From previous journeys in this area systemd-networkd does a much
> neater job and has huge numbers of options.
> 
> This is my worstation config

I hope it gets better :)

> root@client:/etc/systemd/network# cat wired_lan.network
> 
> [Match]
> Name=enp7s0
> 
> [Network]
> 
> DHCP=yes
> 
> Address=10.31.40.68/24
> Gateway=10.31.40.1
> DNS=10.31.40.4 10.31.40.5
> 
> Address=2403:5800:c101:b700:beef::44/64
> IPv6PrivacyExtensions=yes
> IPv6AcceptRA=yes
> 
> Domains=lan example.com
> 
> [IPv6AcceptRA]

Any reason for running ifupdown in preference to systemd-networkd
on the enp0s3 machine? All mine run the latter, hence being rusty
on the contents of /e/n/i.

Cheers,
David.

Reply via email to