pfSense

here are the new fields:

<radomainsearchlist>google.com</radomainsearchlist>
<radnsserver>dead::</radnsserver>
<radnsserver>beef::</radnsserver>
<rasamednsasdhcp6/>                 <!-- presence means use same as dhcp6 -->

looking good so far. Only thing missing is the ability to set subnets for the RA. Right now, it does only advertise the subnet the router's interface is assigned to. But with IPv6, you may have a global and a UL address. (e.g. 2001:db8::/64 and fd00:db8::/64). Also, it shouldn't be required for the router to have a globally routable address.

thanks.

just added subnets and support for aliases.

and forgot to commit that work until just now

Applied in changeset 8c4ee06242721655f29d98064516d0c26f723b68.

user interface to add subnets looks great. But settings are not reflected in /var/etc/radvd.conf . Should the be? will experiment a bit more.

Small user interface nitpick (feel free to ignore): One issue I find throughout pfsense's IPv6 settings is that all subnet masks are listed in numeric order. It would make sense to first list the most common once, then all of them in numeric order. So the list would go something like:

32 - 42 - 56 - 64 - 128 ... then 1-2-3-4-5-6-7-...

It may be worthwhile to have a common list that is included in all pages offering a drop down for IPv6 subnets, instead of each page coding its own.

Sorry, forgot about the bit that actually modifies /var/etc/radvd.conf. The bit that modifies /cf/conf/config.xml is done though. :-)

Regarding the "common list" you mentioned, there seem to be quite a few minor variations of it but yeah I find that those bits are hardcoded in so many places annoying as well.

sorry for not responding earlier (haven't had a lot of time to experiment with pfsense). Just to push back a bit here: This is exactly what I am looking for: A ULA and GLA for each host, to use the GLA for outbound communications, and the ULA for internal communications. That is exactly what RFC 5220 and 4291 cover, and hosts will deal ok with it. Most of the issues I had with source address selection these days is related to the GLA not comming up before certain daemons start. But beyond that, the RFC 3484 "longest matching" rule should deal with this just fine, and does in my experiments so far.

Another option would be using RA for the GLA and DHCP for the ULA, but that appears to have some other issues right now (not sure what. still debugging and may not be a pfsense issue).