On Mon, Jul 13, 2015 at 04:39:39PM +0000, Christian Weisgerber wrote:
> On 2015-07-02, Patrik Lundin <pat...@sigterm.se> wrote:
>
> > In summary, using the following commands (together with ip6
> > forwarding enabled) allows us to have a working setup without any
> > other manual intervention:
> >===
> > # ifconfig em0 inet6 autoconf
> > # ifconfig em1 inet6 autoconf
> > # dhcp6c -Df -c /etc/dhcp6c.conf em0
> > # rtadvd em1
> >===
> >
> > But like stated initially, we do not really like the idea of
> > enabling autoconf on em1.
>
> Once you get that far, you might notice that dynamic addresses for
> your network are rather inconvenient. You'll need to update all
> references to your internal hosts in
> * pf.conf
> * DNS zones
> * ... any other daemons that might refer to them ...
>
> You'll also need to distribute the addresses to your hosts. If you
> don't like SLAAC-style addresses, you'll need DHCPv6. Which you might
> also need for the nameserver, NTP server, etc.
>
> Out of the box, OpenBSD is poorly equipped for all of this.
I found setting up IPv6 on a Comcast home network to be very painful.
Part of it was that you need inbound IPv6 ICMP and UDP ports open. This
seems like a fundamentally bad idea because it prevents client machines
from just blocking all incoming connections (something I've done since
starting with OpenBSD). Also, DHCPv4 seems to do fine without incoming
connections. Maybe there's a good reason for them, though.
Here's the guide that solved my pf woes:
http://pivotallabs.com/configuring-freebsd-9-1-as-an-ipv6-dhcp-client/
I was considering trying to develop a tool to make it a smoother
process. However, it increasingly seems like a consequence of DHCPv6
being unnecessarily complex.
