IPv6 Radius Accounting Not Working for PPPOE Clients (Delegated Prefix)

Hi Everyone,

I am a ISP in India and we have a customer base of 3k+

We are trying to implement IPv6 in our network but we are currently stuck due to no IPv6 radius accounting in Mikrotik Routers.

As an ISP we need to know which IPv6 Address is delegated to which customer, But since there is no IPv6 Radius Accounting mikrotik routers we are unable to get the data to our session logs in radius.

It would be really helpful if anyone can help us on this and also is there any alternate solution to this issue???

Not correct. This feature exists already.

Release 6.45.1 2019-07-01
What’s new in 6.45.1 (2019-Jun-27 10:23):
*) dhcpv6-server - added RADIUS accounting support with queue based statistics;

Hi Normis,

Thank you for your valuable response but still we are unable to get the Delegated IPV6 Prefix (DHCPv6 PD) in our Radius Session.

We are only able to get the Remote IPv6 Prefix.

But as per our ISP Regulations in INDIA it is mandatory for us to maintain both Delegated IPV6 Prefix (DHCPv6 PD) & Remote IPv6 Prefix so that we can identify which user got the delegation at which time (IPDR Purpose).

Hope The Images Attached herewith this post may clear your doubts.
IPv6 ND.JPG
PPP Profile.JPG
IN Radius Session.JPG
DHCPv6_Server.JPG
Expecting Your Reply at the earliest.

The feature only exists when using DHCPv6 server outside of PPP/PPPoE situations. It is not yet implemented for PPPoE. We really want to see it implemented for PPPoE situations as well.

Yes because most of the ISP and WISP is using PPPOE for connecting to Clients, Using DHCPv6 or DHCP Server in ISP Grade network in very difficult.

Hope Mikrotik Team may take this issue on priority and do the needful at the earliest.

Hmmm, I Think people are mostly not interested in IPv6 Implementation or am i the only one who is so furious in implementing IPv6…

Well i cant understand!!!

Do you have a ticket number?

I had ticket 2018070222004763 for this, but it was in the older OTRS system they used before they moved to JIRA.

Mikrotik Support Reference No.: SUP-20538

In Brazil we also have the legislation to keep the Logs of Delegated IPV6 Prefix & Remote IPv6 Prefix, and it is really frustrating the development delay of Mikrotik in relation to IPv6.

Is it really that difficult to add the RADIUS Delegated-IPv6-Prefix Attribute to v6? Or should we wait for v7?

Same Doubt i also have. Mikrotik is used by many ISP around the globe and we are requesting this feature from long time.

I believe that Mikrotik Team will do something to solve this issue. Already Mikrotik is late as all other Major Brands like Cisco, Huwai, Juniper etc are fully functional & compatable with IPv6.

Finally received a response from Mikrotik Support Team,

Hello

Thank you for contacting us. Yes, it is in our plans to add such functionality when PPP service is authenticated by the RADIUS server. However, unfortunately, I can not provide any ETA for such functionality.

Best regards

I Know they have not given any ETA, but atleast it gives all of us a hope. :slight_smile: :smiley: :slight_smile: :smiley:

They gave me this same response a year ago.

Then I think some Mikrotik Support Member will surely answer to this post!

RADIUS ACCOUNTING FOR PPP DELEGATED PREFIX… Any Update.

Please do the needful to add the same. waiting from so many years and still no updates from mikrotik team…?

We have clients that also need PPPoE + PD + Radius, please consider implementing this feature

@Normis
Please take a look at this http://forum.mikrotik.com/t/report-delegated-ipv6-prefix-attribute-for-pppoe/81239/1 to remember the problem

What’s new in 6.48beta48 (2020-Oct-14 10:26):

Other changes since v6.47.4:
*) ppp - added support for “Framed-IPv6-Route” RADIUS attribute;

Do this works for PPPoE ?

Hi!

I tried to use Delegated-Ipv6-Prefix with PPPoE and Radius in v6.48 and I get this error:
Could not add dhcpv6 with pool “poolname”: same interface for multiple servers cannot be used!

Thanks,
Marcos.

Delegated-IPv6-Prefix + PPPoE is the last part of the IPv6 puzzle. Hey Mikrotik we are looking for this change in changelog .