I would love to know too !. It's not affecting routing, but is it OK to leave the WAN interface as a link-local address? Or is it simply fine to request the user use one of the /64 in their delegated pool for their WAN?
That is a shortcoming in MT. Other platforms I have worked with allow you to assign the pool prefix by "index" number.My ISP uses DHCPv6-PD and I can simply assign addresses from the pool to internal interfaces, but unfortunately
MikroTik has no option to lock a certain subnet to a certain interface. When configuration is changed or software
behaviour changes, the addresses move around at random, which is not nice when you have externally accessible
servers on IPv6.
My ISP does just that! I get a static /48 prefix that will only change when there are technical reasons, not at random moments.What I want to hear from ISP is "welcome dear customer, here's your static 2001:db8::/48 prefix, it's all yours for as long as you're with us, use it any way you like and enjoy".
Strange... I used a Draytek router for a while and it requests a /64 for its WAN and one for its LAN.Depends on your configuration. We use /64s and /60s for residential users. Nobody has used a /60 yet.
My ideal config would be real static, i.e. numbers on the paper, no DHCPv6. But it doesn't look like it will be a common thing.But I need to fetch prefixes using DHCPv6-PD!
When you add address with from-pool=<dhcpv6 pool>, RouterOS already keeps the last 64 bits. So all they need to do is to extend it to keep last 128 - <received prefix length> bits and it would be perfect for this case, as long as the prefix length would stay the same.So what I want is to specify the subnet (16-bit in my case) for each network that I assign an IPv6 address, ...
I will add "set priority" in Mangle Rule of IPv6 Firewall, I am not able to do prioritize packets and doing QOS on IPv6My most-wanted IPv6 features:
Ability to send AAAA records in dyndns updates
Stateless DHCPv6 server
Stateless NAT64 (CLAT function of 464XLAT deployment, a very useful feature for ISPs - they can make their network work with v6-only on the access and distribution layers, with a centralized stateful NAT64 for IPv4 connectivity to work)
DHCP server -> static DNS entry auto-generation (so hosts can be accessed by name on your local network)
Fixed routing bugs in IPv6: /128 loopbacks advertised from Cisco routers are ignored in OSPFv3, recursive next-hop lookup issues with iBGP, especially with link-local next hop
Stateful DHCPv6 server (for those who want to have more central control over hosts being able to join the network)
Stateless NAT66-PT (prefix translation for working around those pesky dynamic ISPs... but on the other hand, if this feature doesn't exist, then more pressure will be placed on ISPs to go static)
Zywall do the same as well !Strange... I used a Draytek router for a while and it requests a /64 for its WAN and one for its LAN.
In my MikroTik config I have a separate guest WiFi network and it has its own /64 plus the /64 for my LAN (ether+WiFi bridged).
The AVM Fritzbox my ISP provides does the same thing.
So needing more than one /64 should not be that uncommon.
I don't agree... at work we have a different ISP and it uses only static addresses, but it is a drag and error-prone to have toMy ideal config would be real static, i.e. numbers on the paper, no DHCPv6. But it doesn't look like it will be a common thing.