Hello Guys, I am not able to get the prefix 64 from my ISP. The dhcpv6 client just keeps looking. I tested other models of routers and they all worked, but MK v7.7 is not working. Can someone help me?
# jan/15/2023 00:29:32 by RouterOS 7.7
#
# model = RBD52G-5HacD2HnD
/interface pppoe-client
add add-default-route=yes disabled=no interface=ether1 name=pppoe-out1 \
use-peer-dns=yes user=
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface lte apn
set [ find default=yes ] ip-type=ipv4 use-network-apn=no
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk eap-methods="" mode=\
dynamic-keys supplicant-identity=MikroTik
/ip pool
add name=dhcp ranges=192.168.88.10-192.168.88.30
/ip dhcp-server
add address-pool=dhcp interface=bridge lease-time=40m name=defconf
/routing bgp template
set default disabled=no output.network=bgp-networks
/routing ospf instance
add disabled=no name=default-v2
add disabled=no name=default-v3 version=3
/routing ospf area
add disabled=yes instance=default-v2 name=backbone-v2
add disabled=yes instance=default-v3 name=backbone-v3
/interface bridge port
add bridge=bridge comment=defconf ingress-filtering=no interface=ether2
add bridge=bridge comment=defconf ingress-filtering=no interface=ether3
add bridge=bridge comment=defconf ingress-filtering=no interface=ether4
add bridge=bridge comment=defconf ingress-filtering=no interface=ether5
add bridge=bridge comment=defconf ingress-filtering=no interface=\
"wlan 2.4ghz"
add bridge=bridge comment=defconf ingress-filtering=no interface="wlan 5ghz"
/ip neighbor discovery-settings
set discover-interface-list=none protocol=""
/ip settings
set max-neighbor-entries=8192 rp-filter=strict
/ipv6 settings
set accept-router-advertisements=yes max-neighbor-entries=8192
/interface detect-internet
set detect-interface-list=all internet-interface-list=WAN lan-interface-list=\
LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
add interface=pppoe-out1 list=WAN
/interface ovpn-server server
set auth=sha1,md5
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=\
192.168.88.0
/ip cloud
set ddns-enabled=yes
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=\
192.168.88.1 netmask=24
/ip dns static
add address=192.168.88.1 comment=defco
Today I upgraded to beta version 7.8Beta2, to check if the version has an update for these issues.
But I’m still having problems for SLAAC ipv6 on my MK, which are not receiving the 64 prefix from my ISP. I tried several settings here on the forum and none worked.
I discovered that my ISP uses huawei equipment as IPV6 providers, and I believe that for this reason there is some incompatibility.
I’ve tested equipment like Unifi, DDWRT and Huawei and all worked perfectly with ipv6 SLAAC or ipv6 dhcp.
But unfortunately the MK doesn’t work, I’m using HAP ac2 and HAP Lite and none of them worked.
Can someone help me?
You have concepts slightly confused. SLAAC is stateless self-configuration where devices construct their own IPv6 addresses aftrr they receive router advertisement (RA) which is broadcast by router periodically. ROS does support this kind of address acquisition for its WAN address if accept-router-advertisements option is set to yes (default is different). However, such address is not shown when using usual commands (e.g. print) due to long outstanding bug. And more importantly, such address is not useful at all (it only provides router with global IPv6 address), it’s not possible to have LAN subnets only with that info. And point to point links (such as PPPoE) definitely don’t need global IPv6 address associated.
And then there’s DHCPv6, which can give out addresses (ROS server doesn’t support that) and/or prefixes … and only if ROS receives prefix it’s possible to have LAN subnets with IPv6. Your DHCPv6 client config seems almost fine, I have it very similar on a few different ISPs (some use PPPoE, some “native” ethernet) running just fine. I’m using prefix-hint setting of “::/56” (or you can try even to unset it), your setting of ::0 might upset your ISP’s DHCPv6 server.
So I guess you should ask your ISP about that (after changing prefix-hint setting).
