I’ve read the full thread and this show the total lack of touch from the guys from Latvia. They are completely stubborn and it seems as much as people show the need for that feature they seem to play a kids’ game and say “I am not doing it”.
We are in middle-2018 and IPv4 has ran out for a long time ago and there is not even a clue about this issue. They don`t give a damn. They are concerned about other totally different things.
It shows also a complete lack of management skills from the people in charge for bringing the necessary features in time and from those who have to develop it. Show general mess from top to bottom. Worst is: people in charge must believe they are doing a fantastic job by prioritizing “who knows what”.
This is yet another example of this total mess and huge ego from these guys.
This post probably will be censored as soon as they read it and they will probably find it “unfair”.
Stop fooling yourselves asking repetitively for them to do this as a beggar does. They are probably laughing of it.
Apparently now is supported this attribute after some years… according to the wiki.
Which says it was added the Delegated-IPv6-Prefix to radius client on 6.43rc.
Has anyone managed to work with radius delivering the prefix-delegation to the client router, using the Delegated-IPv6-Prefix attribute? It still does not work here.
I used a
DLink DIR-615 Hardware version .: T1 Firmware .: 20.11
and a ONU Fiberhome AN5506-04-F Hardware Version .: WKE2.134.285F2G Software Version .: RP2599 (00.00)
RADIUS should not “deliver the delegation to the client router”, instead it should somehow configure the DHCPv6 server on the router to hand out a specified prefix to the client instead of just any available prefix. Do you see any visible indication that it has done this when the client router connects? Are you testing this with PPPoE or just plain IPv6/DHCP?
CCR1016-12G 6.43.1 - “Delegated-IPv6-Prefix” attribute for PPPoE not work.
Billing gives radius attributes, but the router does not create a dynamic DHCP IPV6 server
We are testing through pppoe.
Using the framed ipv6 addres attribute for the ppp connection and the delegated-ipv6-prefix attribute to create the Dynamic DHCP server in Mikortik and assign the prefix delegation to the client router.
In the Mikrotik radius settings, we set ppp and dhcp.
In case it establishes the ppp connection, it creates the dynamic server in the mikrotik dhchpv6 server, but does not dynamically binding, and the client router does not receive the PD prefix.
I noticed that in this version, even if you let Mikrotik deliver the pool, setting the DHCP POOL-PD profile or using the Prefix-Delagation-Pool attribute and pointing to the pool created in Mikrotik, it does not work, while in version 6.42 .7 works.
Verify that under IPv6->Addresses the PPPoE client is getting an IPv6 link local address assigned. If not, it is because IPv6CP negotiation is not happening, this happens if IPv6 was set to “no” in the profile on the client side, and in this case a DHCPv6 server will not be created.
Since it is a new option, I’m also not sure if in the concentrator’s PPP profile you perhaps need to choose the DHCPv6 PD pool option along with a “default” pool that it should assign from if the customer has no Delegated-IPv6-Prefix?
In my case, in version 6.42.7 with the same configuration on cliente router , when i set only ipv6-framed to be delivery by radius and use Mikrotik-Delagated-IPv6-Pool to use a pool created on Mikrotik, works fine.
I hoped with this option, I could deliver both the prefix for the ppp connection and the prefix-delagation through the radius.
But this does not happen, and the attribute that worked in version 6.42.7, stopped working in version 6.43. That is the question.
In case the IPV6 CP negotiation occurs normally, because it receives the block / 64 set in the radius, create the dynamic dhcp server in the Mikrotik, but the client router (the same used in test with 6.42.7 version) does not receive the pool.
In addition to not solving this management question all allocation of ip by radius, it stopped working what already worked in the previous version.
I wonder if the reason it stopped working is because they added the new attribute: Delegated-IPv6-Prefix-Pool
The old attribute Mikrotik-Delegated-IPv6-Pool may no longer be needed (since it is the same thing as Delegated-IPv6-Prefix-Pool) and they have removed it? Or maybe they didn’t mean to remove it, but adding the new attribute Delegated-IPv6-Prefix-Pool that does the same thing somehow unintentionally broke the old one.
Try using Delegated-IPv6-Prefix-Pool instead of Mikrotik-Delegated-IPv6-Pool
I try Delegated-IPv6-Prefix-Pool and have the same situation.
Dynamic DHCP server is created, but binding is not done and the router does not receive the PD.
On client side PPPoE client is getting an IPv6 link local address assigned - fe80::f/64 and nothing Global IPV6
Why would I assign a DHCPv6 PD pool manually in PPP-profile? I think it should be assigned automatically.
Ok, I set manually in the DHCPv6 PD pool name in profile. After reconnecting the PPP client, the DHCP server was dynamically created, but the ipv6 is not assigned to the client. Is there any instruction from a Mikrotik-developers how to do it correctly?
Same problem here. Even though upgrading to version 6.43.1, the problem still continues.
On the same routerboard if I return to version 6.40.9, the DHCPv6 PD Pool returns to normal operation. Without changing any configuration on the routeros.
A problem exists, you can be sure of that.
In version 6.43 in both DHCP Server or PPPoE the Dynamic DHCP server is created, but binding is not done and the CPE does not receive the PD.
Downgrading to version 6.42.7 makes it work again.
If radius parameters wasn’t working as expected it would not even create the dynamic DHCP Server upon connection. Also this has been tested with all parameters local with and without PPPoE and none worked.
