Basically I made a dhcp-client on my ether1, it pulls /64 prefix and address (pool prefix length 64) and creates general-pool6. If I tried pulling 60 it wouldn’t work, but oddly it assigned me a 2600:1700 address on a /60.
Then I added VLAN20, VLAN50, and VLAN100 to ipv6 address list using ::64 it pulled basically 2600:1700 blah blah :1871,1870,and1872 endings all on a /64. 2001:506 ipv6 was assigned via DHCP to my ether1. I don’t seem to have a 2600:1700 for ether1, but I assume that’s fine? There is also a link local fe80: for ether1 and all VLAN interfaces, but ether1 is fe80:a67a:blahblah while the others are fe80:c6ad:blahblah.
IPv6 shows working, but I feel like I did this wrong. Also I am not using peer DNS since I hate AT&T DNS.
I suggest you to post full IPv6 config. Get output of the following commands (obfuscate public IP addresses, but hide most significant octets, not the least significant ones as they show relevant information):
Sorry I overlooked you posted lots of information.
Disclaimer: I’m by no means an expert for IPv6 in ROS, so my analysis likely missed something.
Anyways, I don’t see anything much wrong in your setup. The only thing I’m doing differently (and I have a few VLANs with IPv6 addresses from pool which are not the same) is the way of assigning addresses … here’s my config:
Note the double-colon at the beginning of address, it actually instructs ROS to take one of /64 prefixes from pool and append the rest of cofigured address and then assign tgat address to the interface. And the address I used is the LSB part of link-local address on the same interface. You can use anything else, e.g. “address=::1” …
In my case, ISP is giving out /56 prefixes and I have 3 VLANs. And similar construct assigns addresses from different prefixes to each of interfaces.
The other difference between your and my setup is that I don’t try to run DHCPv6 server … it’s very incomplete in ROS. Instead I rely on Router Advertisements to make their magic (and they do for all different devices I have: Windows and Linux PCs, Android phones). But this difference should not cause the weirdness about same IPv6 address being assigned to multiple interfaces.