I Originally experienced some issues with an ipv6 link-local collision, upon investigation I noticed that the bridge template(and other templates) lacked any ipv6 awareness. On further investigation I discovered that the bridge template usurps the MAC Address of the last nic in the list of slaves; now for some nics, like an unused tap, it won't affect anything if nothing is using the tap, but if it is an active nic, then both the nic and the bridge will be assigned an link-local ipv6 address causing network failures.

The solution to this was to add a little more logic to the bridge template, specifically adding variables for manual MAC addresses($mac_addr), and ipv6 addresses($ipaddr6) and finally a method to specify an ipv6 gateway($gateway6)

ipv6 gateway functions were not tested, due to a lack of ipv6, but the address assignment works correctly, as does the MAC override.

sysctl calls updated to include ipv6 forwarding as well.

Once bug is closed I will update the wiki with the new information. This update is a drop in replacement, requiring no edits to existing existing bridge configurations unless they desire to enable these new features.