I’m able to reproduce the same behavior with from-pool and add-default-route. Details are in this thread: http://forum.mikrotik.com/t/comcast-dhcpv6-pd-problems-with-5-19/58227/1
I think there are two separate bugs in 5.19:
- add-default-route actually adds a route for the prefix received via dhcpv6-pd, not a default route. I can reproduce this and it looks like you can too.
- /ipv6 address attribute from-pool does not seem to be effective.
I was able to get home IPv6 up and running, albeit in a hacky configuration, by:
- disabling add-default-route, but manually adding a default route pointing to v6 LL address of the CMTS
- manually addressing my internal interface with the prefix handed out by dhcpv6-pd
Can anyone else reproduce this behavior? If so, we should confirm as a bug and submit to mikrotik support.