Router Telecom + Mikrotik with IPv6

RouterOS General
1

Hello,

I have a question with mikrotik work ipv6, my Telecom (Copel Telecom, Fiber2home) start work with ipv6 / 64.

The router is Huawei HG8245H work in dualstak IPv4 and IPv6, the telecom give 2 IP, one ipv4 working with cgnat and ipv6.

The problem is how i delivery to my clients (not pppoe) ipv6 using in my mikrotik DhcpClient6 to get a IPv6 from router and give to all PC´s from my network a IPV6 ?!?! i try same configuration

[rpsolution@Telecel] > /ipv6 dhcp-client add pool-name=copel-ipv6 pool-prefix-length=64 interface=1-INTERNET add-default-route=yes
[rpsolution@Telecel] > /ipv6 dhcp-client print detail 
Flags: D - dynamic, X - disabled, I - invalid 
 0  I interface=(unknown) pool-name="copelv6" pool-prefix-length=64 status=stopped duid="00030001001cc

 1    interface=1-INTERNET pool-name="copel-ipv6" pool-prefix-length=64 status=bound prefix=2001:1284:
      add-default-route=yes 
[rpsolution@Telecel] > /ipv6 pool print
Flags: D - dynamic 
 #   NAME                                                                                             
 0 D copel-ipv6                                                                               
 
[rpsolution@Telecel] > ping [:resolve ipv6.google.com]
HOST                                     SIZE TTL TIME  STATUS                                                                                                                       
2607:f8b0:4002:c0c::71                     56  55 135ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 135ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 135ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 135ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 134ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 135ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 135ms echo reply                                                                                                                   
2607:f8b0:4002:c0c::71                     56  55 134ms echo reply                                                                                                                   
    sent=8 received=8 packet-loss=0% min-rtt=134ms avg-rtt=134ms max-rtt=135ms 

[rpsolution@Telecel] >

In mikrotik ping ipv6 address, in my internal network don get IPv6 and do not ping

2

Solution ? our howto IPv6 config ?!

3

When you get only 1 IPv6 /64 network address from your provider it is not possible to route it in your MikroTik!
You need to get a larger range from your provider, e.g. a /48 or /56.
Then your DHCPv6 client can request a prefix from your provider, put it in the pool, and you can get
addresses from your internal network from that pool.

4

Actually it is possible.
The thing is just not to assign it to the WAN.

Get it to a pool via the DHCP client and assign it to the LAN and then let RA do its job. Also let’s not forget the firewall:

/ipv6 dhcp-client
add add-default-route=yes interface=WAN pool-name=ipv6-pool request=prefix
/ipv6 address
add from-pool=ipv6-pool interface=bridge-lan
/ipv6 nd
set [ find default=yes ] advertise-dns=yes hop-limit=64 interface=bridge-lan

/ipv6 firewall filter
add chain=input comment=ICMPv6 protocol=icmpv6
add chain=input comment="DHCPv6 client" dst-port=546 protocol=udp
add chain=input comment="Established, related" connection-state=established,related
add chain=input comment="Local input" in-interface=bridge-lan
add action=drop chain=input comment="Drop the rest"
add chain=forward comment=Outgoing in-interface=bridge-lan out-interface=WAN
add chain=forward comment="Established, related" connection-state=established,related
add chain=forward comment="Drop the rest"