Hi,
> Handling global configuration changes automatically when
> an IPv6 prefix changes is a separate problem.
> A grotesque solution would be to wrap tcpdump(8) to monitor
> RA messages or read route(9) to trigger a monstrous script.
Why not use something like
`dhcp6leasectl -l <iface> | awk '/IA_PD/ {print $NF}’` ?
Place the result to a file and then “diff” it.
Tcpdump looks like an overkill.
Talking about overkills, you could use perl and p5-IO-KQueue
to monitor the dhcp6leased lease for changes
and possibly use something that supports a templating
language to modify all the configuration reliably.
> ULAs seem to cause source address choice to do unexpected things.
> Host with global & local addresses sending to a local address:
> Source address used is global. Perhaps harmless?
> Perhaps a configuration error on my part?
> An issue to investigate.
This doesn’t match my experience.
Are you using mDNS for hostname discovery?
I’m using SLAAC, rad, ULAs and unbound.
Unbound sample entry:
local-data: "panas.internal.fqdn.org. IN A 192.168.x.24”
local-data: "panas. IN A 192.168.x.24”
local-data: "panas.internal.fqdn.org. IN AAAA fdc4:x:a7de:121:ba27:x:x:f5a6”
local-data: "panas. IN AAAA fdc4:x:a7de:121:ba27:x:x:f5a6”
All hosts feature GUAs and ULAs, but every time I connect to a lan
host via IPv6 the src addr is always the ULA. For example:
laptop$ host panas
panas has address 192.168.121.24
panas has IPv6 address fdc4:32ad:a7de:121:ba27:ebff:fe9a:f5a6
latop$ ssh panas
...
panas$ echo $SSH_CLIENT
fdc4:x:a7de:121:892:x:x:6eee …
--
Panagiotis (atmosx) Atmatzidis
