I have also confirmed with a Packet Capture between the routerboard and radius server that that attribute (Delegated-IPv6-Prefix) is not sent, even though the pool on the Routerboard does show that a prefix has been delegated.
(Note that Framed-IPv6-Prefix is currently sent, but that only covers the addresses used on the CPE’s WAN link.)
This is important to us as an ISP because if there are abuse reports for IPv6 address, we need to have both the Delegated-IPv6-Prefix & Framed-IPv6-Prefix recorded. Delegated-IPv6-Prefix is especially important because it would tend to be the range reported in the vast majority of cases (most of our customers have routers).
This is the one thing in the way of flipping the switch to enable IPv6 for our customers.
Idea is - you set up DHCP-PD-client on your PPPoE server and get dynamic pool. Then you can set pool name in RADIUS from where prefixes has to be given out using Mikrotik-Delegated-IPv6-Pool.
If that is set, PPPoE-Server will automatically add DHCP-PD server on PPPoE interface and as a result, your pppoe client will be able to (if capable) to get prefix via DHCP-PD client
I’m sorry, I read your response but just didn’t get exactly what you are saying. You mention setting up a PD-client on the PPPoE server?
(I’m assuing this pool is for prefix delegations to happen from. Right now, I create two pools: one for the PPPoE link to have /64’s carved out of, and one for prefix delegation for /56’s to get carved out of. Generally, I don’t change what pool you get assignments from based on what customer you are. Just for clarity, the pools that the PPPoE server use are manually configured. The only thing auto configured should be the PPPoE client.)
Hm, I will say that right now that delegating prefixes to clients works, with no special IPv6 related attributes set on their radius profile.
Maybe I confused you between Authorization and Accounting? Right now, the Authorization side is working just fine for me.
What I want is the accounting side to report what prefixes were delegated to the PPPoE client. That is what I was talking about packet capturing. So I was looking at accounting packets.
I’m thinking that more useful will be support for Delegated-IPv6-Prefix in the accept message because we need assign IPv6 prefixes in managed way from RADIUS server.
The router when receive Delegated-IPv6-Prefix in the accept message creates a dynamic pool and this pool is then assigned to a dynamic DHCPv6-PD server on the top of the accepted PPPoE connection…
Nice will be too support for Delegated-IPv6-Prefix-Pool (RFC6911) in the same way how is used the private Mikrotik-Delegated-IPv6-Pool attribute.
We have a problem with IPV6 prefix delegation for PPPoE users through Radius attribute “mikrotik-delegated-ipv6-pool”.
0. Equipment RB1100 AHx2 + ROS 6.20 with IPV6 package.
On RB1100 AHx2 configured IPV6 pool “ipv6pool”
On the Radius-server is configured attribute "mikrotik-delegated-ipv6-pool=ipv6pool
RB1100 receives an attribute of the radius server, and creates a dynamic IPV6 DHCP, but addresses are not issued or issued only a one address and then only if the customer is Mirotik RV750.
We just want to attribute as Mikrotik-Address-List, but for IPV6 (Mikrotik-IPV6-Address-List) to limit the rate of users on the tariff plan in IPV6 address space.
Any good news when this will be implemented? This is what blocks my IPv6 deployment to customers - all of them have routers which get single static IPv4 addresses via PPPoE, some (not many yet) of their routers support IPv6, and while it would be possible to give them static IPv6 prefixes for the WAN side (Framed-IPv6-Prefix), they also need a separate one for the LAN side (Delegated-IPv6-Prefix), which I want to keep static as well (don’t want any dynamic pools - each customer would need a separate pool, from which exactly one prefix would be delegated).
Bump.
Any chances for Delegated-IPv6-Prefix RADIUS attribute to be supported by MikroTik PPPoE server soon, or do I have to look into other solutions (such as accel-ppp)?
Mikrotik should and must able to receive delegated-ipv6-prefix, because it’s featured standard among other BRAS vendor. Some of ISP want to assigned IPv6 to CPE LAN from radius. And also should send delegated-ipv6-prefix at accounting - request log at radius.
