pfSense

Allow for creation of a ipv6 tunnel for he.net by creating a gif interface. This is the recommended procedure as advised by he.net
This allows for using ipv6 local and remote addresses, you will need to add a ipv6 default gateway on the routing tab

up the subnet bits from 32 to 128 so that the access can be locked down to the host for ipv6.
This will require a javascript routine that prevents a subnet mask higher then 32 bits for a ipv4 address.

Alternatively the subnet bits should be steered by javascript to prevent use of more then 32 bits on a ipv4 address. When a hostname is used all bets are off, even worse if the hostname is a combined ipv4/ipv6.

Fix the filter.inc rule generation for icmp to prevent a double inet6 in the rule
Add inet6 for user defined rules to ipv6 addresses.

Change the firewall rule generation to look for the ipprotocol tag which defines inet or inet6. This makes sure that we use ipv6 addresses and change to the correct ipv6-icmp tag.

splay the IPv6 information on status interfaces.

Run both traceroute and traceroute6 for ipv6 functionaility

So gethostbyname() does not work for ipv6, instead run both ping and ping6. That works too.

Do a gethostbyname() on the host address to get a IP address, then perform ping or ping6 for correct type.

Allow for configuring a IPv6 address on the interfaces page.
Add code to verify a ipv6 address
Let is_ipaddr() return true on a v4 and v6 address.
Change system gateways edit to fetch the global ipv6 interface ipv6 addresses and subnets
The current ipv6 function might need folding into filter_var() when that catches some documented corner cases....

Display the ICMP type (abbreviated) in the firewall rule list and show the full text when the cursor is over it for ticket #762