IPV6 on wlan not working plus subnetting /56 prefix

RouterOS General
1

Hi everybody,
I have the following problem - my provider gives me a 56 prefix. I have 1 core router where I terminate the my ISP connectivity and remote site OVPN, and second router with wlan that runs my dhcp etc. Now, getting the 56 prefix via the dhcp client on the first router, I create a /60 pool for the second. The dhcp client on the second receives the /60 prefix and creates a /64 for my networks, including WLAN. On the routers everything works fine, however my WLAN clients do not get address.
Then I disabled all my real pools and clients, removed all addresses, routes etc and created a dummy /64 pool, assigned to the wlan. Again - my wireless clients do not receive address.

Any ideas what could be the problem? Thank you in advance

2

Hi,
Can you post an export of your config and a diagram of your network so that it will be easier to see what’s gong on.

I use an ISP for a number of clients that gives out /56 IPv6 and have been using a mixture of mipsbe and CCR’s without issue for some time.

Usually break it up into 256 /64’s to keep it simple.

Depending on your network you could route internally using Link Local or Unique Local Address’s.

3

I turned on the logging of the dhcp and saw that the discovery reaches my primary router (in bindings I see that prefix is offered), however for some reason the solicitation doesn’t complete. As can be seen here:
23:59:14 dhcp,debug,packet dhcp: send 6to4-tunnel1 → ff02::1:2%11
23:59:14 dhcp,debug,packet dhcp: type: solicit
23:59:14 dhcp,debug,packet dhcp: transaction-id: 6745cb
23:59:14 dhcp,debug,packet dhcp: → clientid: 00030001 e48d8c2f 05f6
23:59:14 dhcp,debug,packet dhcp: → oro: 23
23:59:14 dhcp,debug,packet dhcp: → elapsed_time: 62
23:59:14 dhcp,debug,packet dhcp: → ia_pd:
23:59:14 dhcp,debug,packet dhcp: t1: 1800
23:59:14 dhcp,debug,packet dhcp: t2: 2880
23:59:14 dhcp,debug,packet dhcp: id: 0xf
23:59:17 dhcp,debug dhcp: discovering…
23:59:17 dhcp,debug,packet dhcp: send 6to4-tunnel1 → ff02::1:2%11
23:59:17 dhcp,debug,packet dhcp: type: solicit
23:59:17 dhcp,debug,packet dhcp: transaction-id: f38d7e
23:59:17 dhcp,debug,packet dhcp: → clientid: 00030001 e48d8c2f 05f6
23:59:17 dhcp,debug,packet dhcp: → oro: 23
23:59:17 dhcp,debug,packet dhcp: → elapsed_time: 0
23:59:17 dhcp,debug,packet dhcp: → ia_pd:
23:59:17 dhcp,debug,packet dhcp: t1: 1800
23:59:17 dhcp,debug,packet dhcp: t2: 2880
23:59:17 dhcp,debug,packet dhcp: id: 0xf
23:59:18 dhcp,debug,packet dhcp: send 6to4-tunnel1 → ff02::1:2%11
23:59:18 dhcp,debug,packet dhcp: type: solicit
23:59:18 dhcp,debug,packet dhcp: transaction-id: f38d7e
23:59:18 dhcp,debug,packet dhcp: → clientid: 00030001 e48d8c2f 05f6
23:59:18 dhcp,debug,packet dhcp: → oro: 23
23:59:18 dhcp,debug,packet dhcp: → elapsed_time: 1
23:59:18 dhcp,debug,packet dhcp: → ia_pd:
23:59:18 dhcp,debug,packet dhcp: t1: 1800
23:59:18 dhcp,debug,packet dhcp: t2: 2880
23:59:18 dhcp,debug,packet dhcp: id: 0xf
23:59:20 dhcp,debug,packet dhcp: send 6to4-tunnel1 → ff02::1:2%11
23:59:20 dhcp,debug,packet dhcp: type: solicit
23:59:20 dhcp,debug,packet dhcp: transaction-id: f38d7e
23:59:20 dhcp,debug,packet dhcp: → clientid: 00030001 e48d8c2f 05f6
23:59:20 dhcp,debug,packet dhcp: → oro: 23
23:59:20 dhcp,debug,packet dhcp: → elapsed_time: 3
23:59:20 dhcp,debug,packet dhcp: → ia_pd:
23:59:20 dhcp,debug,packet dhcp: t1: 1800

4

Got it working ! The solution is - GRE tunnel. 6to4 doesn’t provide for proper solicitation. Reading the Cisco documentation - turns out GRE does it. So I started GRE tunnel over my OVPN - works like charm.