Report "Delegated-IPv6-Prefix" attribute for PPPoE

Azendale · Tue Sep 23, 2014 2:35 am

See

http://forum.mikrotik.com/viewtopic.php ... ix#p428369

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.

janisk · Wed Sep 24, 2014 1:20 pm

this attribute is not working.

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

Azendale · Wed Oct 01, 2014 7:34 pm

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?

this attribute is not working.

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.

(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.)

this attribute is not working.
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

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.

janisk · Fri Oct 03, 2014 12:00 pm

i was writing about auth not accounting.

Majklik · Mon Oct 06, 2014 10:21 am

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.

saaremaa · Tue Oct 21, 2014 12:18 pm

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.
1. On RB1100 AHx2 configured IPV6 pool "ipv6pool"
2. On the Radius-server is configured attribute "mikrotik-delegated-ipv6-pool=ipv6pool
3. 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.

saaremaa · Tue Oct 21, 2014 12:37 pm

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.

janisk · Tue Oct 21, 2014 3:08 pm

for ipv6 there are no accounting attributes for RADIUS server. Will check what can be done in that regard.

marekm · Mon Nov 10, 2014 12:35 am

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.

+1

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).

marekm · Fri Dec 05, 2014 11:44 am

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)?

saaremaa · Tue Jan 13, 2015 8:53 pm

for ipv6 there are no accounting attributes for RADIUS server. Will check what can be done in that regard.

Any news? We are ready to participate in testing.

awacenter · Thu Jan 15, 2015 1:03 pm

+1 PPPoE IPv6 accounting

bronx · Fri Feb 13, 2015 9:34 pm

+1 PPPoE accounting

alfawalker · Sun Mar 29, 2015 5:24 am

+1 PPPoE IPv6 accounting

+1

alfawalker · Sun Mar 29, 2015 5:26 am

+1 PPPoE accounting

+1

mistry7 · Sun Apr 12, 2015 9:37 am

+1

From me too

andersonlich · Wed May 13, 2015 4:22 pm

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.

I hope at v7 this is have been supported.

remontti · Mon Aug 31, 2015 11:33 pm

It has been solved?

littlecake · Tue Sep 08, 2015 8:08 pm

This feature is really needed by us , please do not tell that I need change all mikrotik routers to other brand .

mistry7 · Mon Sep 14, 2015 4:14 pm

+1 PPPoE accounting

+1

littlecake · Mon Sep 14, 2015 11:37 pm

I made not very nice "solution" and created for every account one pool.
The name of the pool is comming over radius.
The pools are distributed over network by PHP script which is communicating via SSH.

The most worse problem is with function DHCP-PD which is giving prefixes with 3 days timeout.

If the CPE disconnect for short time ( eg. because radio disconnect) the static IPv6 route disappears.
I cannot adjust default lease time (3 days) to shorter .

hci · Mon Jan 25, 2016 6:45 pm

Any progress made in assigning static IPv6 pools and IPv6 accounting? We need IPv6 support.

bmv · Tue Apr 26, 2016 11:04 am

We really need to set this field via RADIUS manually.
We can't assign the name via RADIUS.
We need to assign the specific /64 prefix via RADIUS.

Otherwise we have to log onto each router, add a pool with a specific name, and then add the RADIUS group against the customer.
This is an extra step which could be fixed if the RADIUS attribute could accept an actual IPv6 prefix.

andersonlich · Thu May 19, 2016 2:29 am

Yes we need this feature.

We really need
to set this field via RADIUS manually.
We can't assign the name via RADIUS.
We need to assign the specific /64 prefix via RADIUS.

Otherwise we have to log onto each router, add a pool with a specific name, and then add the RADIUS group against the customer.
This is an extra step which could be fixed if the RADIUS attribute could accept an actual IPv6 prefix.

saaremaa · Thu May 19, 2016 12:34 pm

+1
We need to assign the specific /64 (for one host) or /56 (router+network behind router) prefix via RADIUS.
and IPV6 Radius accounting information.
Without this feature we a not start testing IPV6 on our ISP network.

andersonlich · Fri May 20, 2016 8:16 am

yes mikrotik, please do this feature. cmon......

+1
We need to assign the specific /64 (for one host) or /56 (router+network behind router) prefix via RADIUS.
and IPV6 Radius accounting information.
Without this feature we a not start testing IPV6 on our ISP network.

marekm · Tue May 24, 2016 10:53 am

+1

or look into installing accel-ppp + BIRD on Linux, Delegated-IPv6-Prefix has been supported for some time now, in the latest git sources (not stable release yet) it just got RFC4638 support as well, and it's all free software / open source. Yes, it needs more work to set up - that's the main reason I haven't switched yet.

marekm · Tue Jun 07, 2016 12:01 am

Bump, on another annual IPv6 day... Any progress on this?

diorges · Sun Jun 12, 2016 11:33 pm

MikroTik we really need this!!!!!!!!!

andersonlich · Tue Jun 14, 2016 1:33 pm

when this (Delegated-IPv6-Prefix) feature should be available and also we need Mikrotik-IPv6-Address-List is able to be parsed from radius to RouterOS.

remontti · Mon Jul 11, 2016 5:07 pm

Just missing me so to begin delivering IPv6!
3 years!

user3k · Fri Jul 22, 2016 8:13 pm

Ipv6 is here. Is critical.
Mikrotik will be in the past if they can get things like this working.

marekm · Sat Jul 23, 2016 2:24 am

accel-ppp 1.11.0 is released, my PPPoE servers are aging RB1100AH's and I was hoping to replace them with nice new CCR's but now considering setting up good old Debian boxes with accel-ppp + BIRD (to redistribute PPPoE clients IPs by OSPF).

saaremaa · Sat Jul 23, 2016 6:48 pm

for ipv6 there are no accounting attributes for RADIUS server. Will check what can be done in that regard.

any news?

user3k · Wed Jul 27, 2016 11:40 pm

for ipv6 there are no accounting attributes for RADIUS server. Will check what can be done in that regard.
any news?

+1

boldsuck · Sat Jul 30, 2016 3:52 pm

accel-ppp 1.11.0 is released, my PPPoE servers are aging RB1100AH's and I was hoping to replace them with nice new CCR's but now considering setting up good old Debian boxes with accel-ppp + BIRD (to redistribute PPPoE clients IPs by OSPF).

Ubiquity Edge-Router (EdgeOS) are Debian / Vyatta based. You can 'apt-get install $missing-packets'. Perhaps this is an option for someone. EdgeOS is really Free Open Source Software in oposite to RouterOS.

mbrandl · Thu Sep 22, 2016 1:51 am

+1

Any news @Mikrotik

saaremaa · Fri Sep 23, 2016 12:38 pm

any news?

saaremaa · Tue Oct 18, 2016 3:52 pm

Any news about implementation radius attribute "Delegated-IPv6-Prefix " https://tools.ietf.org/html/rfc4818 ? It is very important! Because without it you can not assign a static ipv6 using billing.

hci · Wed Oct 19, 2016 8:15 pm

Looks like IPv4 space is going for about 13$ USD an IP at IPv4 auctions etc. Current plan is to give all users a IPv6 /64 and lower speed tier users a NATTED IPv4 rather then a public IPv4. "Delegated-IPv6-Prefix" attribute would sure be helpful.

Fri Oct 28, 2016 1:35 pm

MikroTik RouterOS 6.37 has support for the following PPP attributes,

Framed-IPv6-Prefix
Framed-IPv6-Pool
Mikrotik-Delegated-IPv6-Pool

saaremaa · Fri Oct 28, 2016 3:43 pm

Great! Make please support "Delegated-IPv6-Prefix"

savage · Fri Oct 28, 2016 5:39 pm

MikroTik RouterOS 6.37 has support for the following PPP attributes,

Framed-IPv6-Prefix
Framed-IPv6-Pool
Mikrotik-Delegated-IPv6-Pool

And yet again nothing in the changelogs, sigh...

bmv · Mon Nov 14, 2016 12:24 am

Great! Make please support "Delegated-IPv6-Prefix"

YES.
This is what we are waiting for.

When will this be available.

IPv4 can run for ever.
Mikrotik could help us massively by enabling this RADIUS attribute.

https://tools.ietf.org/html/rfc4818

saaremaa · Thu Nov 24, 2016 4:10 pm

Any news about "Delegated-IPv6-Prefix" attribute for PPPoE?

marekm · Thu Nov 24, 2016 11:44 pm

I asked support a few days ago when this will be implemented, and the response was:

"We do not have/provide such information."

bmv · Thu Nov 24, 2016 11:53 pm

And I asked and this was their response to me!!
"We are aware of this feature implementation. We will see what we can do."

mducharme · Fri Nov 25, 2016 7:35 am

+1 for this feature

mannana93 · Fri Nov 25, 2016 9:51 am

bajodel · Fri Nov 25, 2016 12:20 pm

+1 ..

saaremaa · Thu Jan 19, 2017 11:46 am

Any news about "Delegated-IPv6-Prefix" attribute for PPPoE?

Majklik · Wed Jan 25, 2017 10:18 pm

MikroTik RouterOS 6.37 has support for the following PPP attributes,

Framed-IPv6-Prefix
Framed-IPv6-Pool
Mikrotik-Delegated-IPv6-Pool

These attributes are supported long time, but still is missing Delegated-IPv6-Prefix as most important!
In second line there is too very nice attributes DNS-Server-IPv6-Address and Delegated-IPv6-Prefix-Pool which is RFC variant of the private Mikrotik-Delegated-IPv6-Pool.

petrb · Thu Jan 26, 2017 4:21 pm

yes, please implement Delegated-IPv6-Prefix for PPPoE, we have stuck in implementation of IPv6 using PPPoE (delegated IPv6 pool is not enough)

okoun · Sat Jan 28, 2017 12:49 pm

Unfortunately, I do not know what you have to do to someone mikrotik forced to finish!

andersonlich · Fri Feb 03, 2017 2:37 am

please do something with this feature.

petrb · Sat Feb 04, 2017 11:28 pm

+1 RC 6.39 nothink new

crodler · Sun Feb 05, 2017 1:22 pm

+1 for Delegated-IPv6-Prefix Attribute

crodler · Mon Feb 06, 2017 8:09 am

Hi, i want to share a fasthack workaround for our ISP

We use radiusdma server and pppoe servers with static ipv6 default route. This script runs on cron minutely and saves any change of ipv6 routes on pppoe server to file.

#!/bin/bash
dateAndTime=$(date +"%Y-%m-%d-%H.%M.%S")
basedir="/var/log/XXX"
keyfile="/xxxx/yyyy/x.x.x.x_dsa"
filename="$basedir/$dateAndTime.txt"
serverip="x.x.x.x"
serverport="yy"
user="abcd"
ssh $serverip -p $serverport -l $user -i $keyfile "/ipv6 route print detail without-paging file=ipv6routes"
sleep 2
scp -i $keyfile -P $serverport $user@$serverip:ipv6routes.txt $basedir/newtemp.txt

if diff -q <(cat $basedir/newtemp.txt | grep -v "#") <(cat $basedir/temp.txt | grep -v "#")
then rm $basedir/newtemp.txt

else
cp $basedir/newtemp.txt $filename
cp $basedir/newtemp.txt $basedir/temp.txt
rm $basedir/newtemp.txt
fi
exit 0

petrb · Mon Feb 06, 2017 8:09 pm

thanks, this script could be usefull .... i had same idea, store information about used prefix/pppoe user from routing table ... prefer static ipv6 delegated prefix, most of our client prefer same address (static AAAA dns etc ... )

crodler · Thu Feb 09, 2017 8:27 am

thanks, this script could be usefull .... i had same idea, store information about used prefix/pppoe user from routing table ... prefer static ipv6 delegated prefix, most of our client prefer same address (static AAAA dns etc ... )

To achive this you configure every client manually?

savage · Thu Feb 09, 2017 9:00 am

To achive this you configure every client manually?

We send a Framed-IPv6-Prefix (static) per customer. MT then sets up a static route once the client connects via link-local, and the customer is informed of his prefix and can manually configure the prefix on his side as the customer wants to. No need for DHCPv6, no need for Remote-IPv6-Prefix on the BRAS (when MT BRAS is used in any case). Nothing other than the single radius attribute required on the MT BRAS.

On our Cisco BRAS' we use a /64 to allocate a dynamic /128 to the client (like it should be) instead of using link-locals, and then still use Framed-IPv6-Prefix to tell the BRAS to setup the static route for the prefix to the client.

saaremaa · Thu Feb 09, 2017 9:12 am

To achive this you configure every client manually?
We send a Framed-IPv6-Prefix (static) per customer.

You use the billing? Approximately how many subscribers you have? We have over 3000 subscribers - Framed-IPv6-Prefix (static) per kustomer - it's a big problem for us because our billing support Delegated-IPv6-Prefix, not Framed-IPv6-Prefix .

savage · Thu Feb 09, 2017 9:39 am

To achive this you configure every client manually?
We send a Framed-IPv6-Prefix (static) per customer.
You use the billing?

AAA Servers combine all different types of accounting, and the combined accounting is used for billing. So whether it's IPv4, or IPv6, it makes no difference to us. A byte, is a byte, is a byte, no differentiation, or distinction between IPv4 and IPv6 from a billing perspective (although we still can if we want to by making some changes on the AAA server policies).

3K customers with a static /57 means you need less than a /45. ISP's generally get assigned a /32 (to start with), which can accommodate 33,554,432 /57'ss or 16,777,216 /56's if you want to go that way rather...

Seems the problem you're having isn't a IPv6 one, but rather a billing (systems) one

Our systems are all developed in house, we don't use 3rd party applications (like radius manager or what not). I think you'd rather need to approach your software developer to pose these questions to them. I'm fairly sure that with newer versions of FreeRadius (3.x) you'd also be able to easily rewrite Framed-IPv6-Prefix to Delegated-IPv6-Prefix, and vice versa - there's always more than one way to skin a cat

dbedani · Thu Feb 16, 2017 3:25 pm

+1 PPPoE IPv6 accounting

+1

saaremaa · Thu Feb 16, 2017 3:34 pm

3K customers with a static /57 means you need less than a /45. ISP's generally get assigned a /32 (to start with), which can accommodate 33,554,432 /57'ss or 16,777,216 /56's if you want to go that way rather...

...this is a very big crutch for a broken leg

support "Delegated-IPv6-Prefix" - imho better and the right idea

petrb · Mon Mar 06, 2017 6:59 pm

yes, delegated prefix will be great ..... creating pool for every single user and using mikrotik-delegated-pool is not the best solution

gr0mit · Fri Mar 10, 2017 5:58 pm

+1 - when is this coming? We are struggling to do a proper job of deploying v6 without Delegated-IPv6-Prefix...

hci · Fri Mar 10, 2017 7:11 pm

Really need...

Delegated-IPv6-Prefix
and
IPv6-Accounting

saaremaa · Fri Mar 24, 2017 6:10 am

Hey, Mikrotik guys!? Answer something about "Delegated-IPv6-Prefix" attribute for PPPoE and IPv6-Accounting? Should we wait or look for another vendor?

petrb · Fri Mar 24, 2017 11:37 pm

I'm sad .... now we try to get some informations about Cisco XRv and use it in VMware esxi like pppoe concentrator. But I'm afraid about high price.

https://mellowd.co.uk/ccie/?p=2777

Mikrotik, please give us some hope. Thanks

marekm · Mon Mar 27, 2017 4:26 pm

I'm sad .... now we try to get some informations about Cisco XRv and use it in VMware esxi like pppoe concentrator. But I'm afraid about high price.

https://mellowd.co.uk/ccie/?p=2777

Mikrotik, please give us some hope. Thanks

On x86 (physical or virtual) you can run your favourite Linux distro + BIRD or Quagga + accel-ppp which has Delegated-IPv6-Prefix support. It takes more work to set up, but the software is free (both as in freedom and as in beer) - that's what I plan to do when my patience waiting for Mikrotik to implement this feature runs out.

petrb · Mon Mar 27, 2017 8:59 pm

thanks .... yes and no ... I preffer debian, but stable debian (8 - jessie) have kernel that not support mpls in kernel, iproute2 version that cannot configure mpls, debian 9 stretch is now in freeze status, must wait and can be used

edit: we have pppoe in vpls/mpls

petrb · Mon Apr 17, 2017 11:53 am

Hi, any changes? Is there any change how to get "IPv6 delegated prefix from pool" information to radius accounting?

IPv6 Delegated prefix not implemented
IPv6 accounting to radius not implemented or I miss something?

We need the data retention function fully work in accordance with local laws.

I try some another way, but no success. Nothing work "out of box". Need support ldp, mpls, vpls, pppoe, "ipv6 prefix delegation" or "ipv6 accounting - get delegated pool to radius"
Debian 8 - not support mpls/vpls out of box
Debian 9 - mpls/vpls support, but terrible configuration when you have 100+ tunnels, ldp not support without patching
Vyatta/VyOS free version - not suport mpls/vpls
Brocade Vyatta based router - waiting for response from seller

Some tips ?

saaremaa · Mon Apr 17, 2017 12:00 pm

Reply from: "Sergejs (MikroTik Support)" <support@mikrotik.com> (MikroTik)
Re: [Ticket#2017040622000758] "Delegated-IPv6-Prefix" attribute for PPPoE

Thank you very much for the report.
We are aware of this feature, we will see what we can do.

Best regards,
Sergejs

saaremaa · Mon Apr 17, 2017 12:11 pm

petrb, we look towards Ericsson (RedBack) SE100 BRAS. http://rbdoc.ufanet.ru/en_lzn7830011_1_ ... CHAPTER1.2
We do not have the information whether there is Accounting

petrb · Mon Apr 17, 2017 1:05 pm

hi, great news from latvia

thanks, I'll look closer at erricsson

petrb · Tue May 23, 2017 9:58 am

Hi, any news about delegated prefix ?

Solution:
I have two separated BRAS (mikrotik pppoe servers with radius) and on both of them I create with script 2000 /56 pools wit example parameters

/ipv6 pool add name="2a01::/56" prefix="2a01::/56" prefix-length="56"
....

and in radius I have attribute for each client

mikrotik-delegated-ipv6-pool = "2a01::/56"

This way works, I also try use large ipv6 pool, but mikrotik didnt implement pppoe ipv6 accounting and I cannot find infomation in radius about delegated prefix to single user. (or I miss somethink)

saaremaa · Tue May 23, 2017 10:18 am

Solution:

Yes, it works, but our local FBR

require a static binding of the address or address pool to the consumer.

petrb · Tue May 23, 2017 10:30 am

Yes, it is static => single poll selected for single pppoe user by using mikrotik-ipv6-delegated-pool atribute in radius

saaremaa · Tue May 23, 2017 11:10 am

Yes, it is static

Ok thank you for solution. I'll transfer idea to our testing department.

mantunes · Wed Aug 23, 2017 11:43 pm

+1

tks

saaremaa · Thu Aug 24, 2017 12:54 pm

+100500

hci · Thu Aug 24, 2017 4:21 pm

If you have a thousand PPPoE users you want to give static /64 IPv6 delegations you must create a thousand pools on the Mikrotik to match.

Also, is IPv6 accounting of an sort working yet?

michellsilva · Thu Aug 24, 2017 8:42 pm

+1

Awaiting a solution....

petrb · Sat Aug 26, 2017 12:38 pm

If you have a thousand PPPoE users you want to give static /64 IPv6 delegations you must create a thousand pools on the Mikrotik to match.

Also, is IPv6 accounting of an sort working yet?

Yes, it is terrible solution, but is very easy to prepare it.

Azendale · Tue Oct 31, 2017 11:31 pm

Mikrotik, what is the status of getting the "Delegated-IPv6-Prefix" attribute reported in radius accounting packets?

I just ran into an instance in our production network where I needed this information (which our radius server is not reporting because it can't record what it doesn't get) in our production network.

It has been three years. This should not be hard, which leads me to believe 0 development time has been spent on this. I haven't seen your source code, but considering you already collect info (IP address, bytes transferred, etc) and report it in accounting packets about active PPPoE sessions, I'm guessing it would take a developer less than a day. This is important to us; if I could change the source code, I would have already spent the day of my time trying to get this done.

saaremaa · Wed Nov 01, 2017 9:37 am

IMHO no sense, but +1

hci · Wed Nov 01, 2017 3:39 pm

It would be great if they could concentrate on a carrier grade NAT and rounding out and improving IPv6 support. With the ipv4 shortage it won’t be long before some users are NAT on private IPv4 and IPv6 dual stack. Almost all cellphone connections are that way now in US.

petrb · Fri Nov 03, 2017 11:36 am

I can not understand why this takes so long. IMHO this can be implemented easily. Prefix delegation is implemented based on prefix pool and really works. You can send radius attribute mikrotik-delegated-ipv6-pool, but this pool must be prepared in router os. Half of work is done. We need from Mikrotik to create dynamic ipv6 pools based on delegated-ipv6-prefix and pair it with implemented PD.

Hello people from the Latvia, are you there?

saaremaa · Fri Nov 03, 2017 7:48 pm

We need from Mikrotik to create dynamic ipv6 pools based on delegated-ipv6-prefix and pair it with implemented PD.

In most billing systems, you can assign a prefix in the user account and send it as the Radius attribute. It's simple and it should work!
Sorry, but creating dynamic ipv6 pools on Mikrotik manually or using scripts is a lot of work and a nightmare in support.
For example, we have a segment of about 1000 users. I need to create 1000 records - pools. And we have this segment terminated on several Mikrotiks Duplicate pool records for all Mikrotiks ?.
Radius Ipv6 PD - easier. Because it's enough just to attach the IPV6 prefix in billing and all - no more manual work.

petrb · Fri Nov 03, 2017 11:58 pm

you can assign a prefix in the user account and send it as the Radius attribute.

With attribute is used in billing system? I mean it is IPv6 framed prefix ... but when is used, you need to configure each customers CPE IPv6 manually and this is the issue. Life is more simple if you used delegated ipv6 prefix (or use mikrotik "hack" with pools - you didn't need to configure DHCPv6 PD on CPE manually (most of our customers have own routers and PD must be used from CPE to customers home network).

Yes, duplicated pools for all PPPoE servers. I have two pppoe servers for more than 1000 CPE and redundancy can be done by creating only one route rule for ipv4 and one route rule for ipv6.

Sorry, but creating dynamic ipv6 pools on Mikrotik manually or using scripts is a lot of work and a nightmare in support.

I can generate more than 1000 pools in few minutes. I used http://www.gestioip.net/cgi-bin/subnet_calculator.cgi, generate 1024 pools of /56 networks, use awk/crop/echo in bash command line and I have 1024x /56 subnets prepared to import in routerOS in one minute. Import it to all pppoe concentrator, make ospf to work and it is done. (be aware to ospf storm when clients are connect/reconnect ... use stub areas)

In radius I only select right pool, on UBNT CPE only select ssid, username, password,ipv4 routing mode with nat, DHCPv6 PD mode and it's almost done. No IP address must be assigned manually at CPE. (only ipv4 LAN part, but that is really prepared)

Jesse6 · Fri Nov 17, 2017 6:39 pm

+1 for the glorious feature. Can't fully implement dynamic IPv6 for customers without RADIUS being able to record delegated prefixes.

robertik · Thu Nov 23, 2017 7:36 pm

+1 for this feature

Scripting all pppoe hubs with all prefix list is being a hustle.

marlow · Sat Dec 30, 2017 5:08 pm

When can we have "Delegated-IPv6-Prefix" ?

The IPv4 pool ran out on 14 September 2012 for the RIPE region ... that's over 5 years ago ...

and all Mikrotik gives us is a half arsed PPP/PPPoE stack for IPv6.

IPv6 was implemented with the release of RouterOS 3.x ... in 2008 .. which was late as it was. And we've not had a fully functional PPPoE stack ever since. That's 9 years of being ignored.

/M

marlow · Tue Jan 09, 2018 1:10 pm

Well ....

I went and looked back on my tickets and I've raised this issue in 2010 and was told, they had no timeline for implementing it.
I raised it again over a week ago, and all I'm told is, that it's on the todo list .. with no timeline.

/M

jhonnyp · Tue Feb 13, 2018 2:09 pm

IPv6 Delegated prefix +1
IPv6 accounting +1

fernandolv · Wed Feb 14, 2018 7:15 pm

+1

pool6 refused acquire: bad preferred prefix

my dhcp reports this error, anyone with this problem?

marlow · Wed Feb 14, 2018 9:27 pm

+1

pool6 refused acquire: bad preferred prefix

my dhcp reports this error, anyone with this problem?

Either the prefix you specified isn't set up on your router, that you're specifying. I've also seen weird errors, when the dhcp-package is disabled.

/M

fernandolv · Fri May 18, 2018 3:49 am

+1 !!!

alidamji · Sat May 19, 2018 11:42 pm

+1 !!

fredyz · Wed Jun 13, 2018 7:19 pm

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.

mducharme · Thu Aug 16, 2018 8:39 pm

Hi, I see some hint that MikroTik has quietly added partial support for Delegated-IPv6-Prefix, look here

https://wiki.mikrotik.com/wiki/Manual:I ... US_Support

They don't mention it but look at radreply. Maybe it isn't fully there yet but it looks like they are working on it.

marlow · Thu Aug 16, 2018 8:43 pm

Oh .. interesting. Time to play with rc releases.

/M

null31 · Sun Aug 19, 2018 5:43 pm

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.

https://wiki.mikrotik.com/wiki/Manual:R ... ess-Accept

Edit:

This appears on the changelog of 6.43rc51.
*) dhcpv6-server - added additional RADIUS parameters for Prefix delegation, "rate-limit" and "life-time";

saaremaa · Sun Aug 19, 2018 5:47 pm

Good news!!! It remains to wait for 6.43 and test, test and test.

thg3x · Fri Sep 14, 2018 2:20 pm

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.

marlow · Sat Sep 15, 2018 1:13 pm

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.

Which client router are you testing with ?

/M

thg3x · Mon Sep 17, 2018 3:51 pm

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)

mducharme · Tue Sep 18, 2018 4:31 am

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?

They now officially list support: https://wiki.mikrotik.com/wiki/Manual:R ... ess-Accept

"Delegated-IPv6-Prefix - IPv6 Prefix. Added in v6.43"

saaremaa · Tue Sep 18, 2018 1:49 pm

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

thg3x · Tue Sep 18, 2018 2:00 pm

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?

They now officially list support: https://wiki.mikrotik.com/wiki/Manual:R ... ess-Accept

"Delegated-IPv6-Prefix - IPv6 Prefix. Added in v6.43"

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.

mducharme · Tue Sep 18, 2018 6:03 pm

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

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?

thg3x · Tue Sep 18, 2018 6:45 pm

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
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.

mducharme · Tue Sep 18, 2018 6:54 pm

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.

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

thg3x · Tue Sep 18, 2018 7:20 pm

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.
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.

whaiser · Tue Sep 18, 2018 8:14 pm

+1
Same issue here!

saaremaa · Tue Sep 18, 2018 8:29 pm

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?

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?

gondim · Tue Sep 18, 2018 8:41 pm

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.

fredyz · Wed Sep 19, 2018 8:53 am

Same problem here as reported by thg3x

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.

minelli · Thu Sep 20, 2018 2:21 am

Same problem here.

mducharme · Thu Sep 20, 2018 4:43 am

Confirmed, I did a bit of debugging and I see what is happening - the client requests a prefix from the DHCPv6 server, the server says "binding not found" and gives a zero second lease of prefix ::/0 to the client, so the MikroTik client successfully gets a "lease" of ::/0, which expires after one second, and so the client follows up one second later to renew the lease, and every second thereafter continuously.

If I manually create the DHCPv6 binding and associate the prefix, client DUID and IAID, it gets the prefix.

Certainly a major bug - I wonder how this got through testing?

thg3x · Thu Sep 20, 2018 3:46 pm

Another thing I realized was that in version 6.42.7, mikrotik creates the dynamic dhcp-server without the use-radius option, while version 6.43, it creates the dynamic dhcp-server with the use-radius=no option.

mducharme · Thu Sep 20, 2018 8:43 pm

Another thing I realized was that in version 6.42.7, mikrotik creates the dynamic dhcp-server without the use-radius option, while version 6.43, it creates the dynamic dhcp-server with the use-radius=no option.

That's because the use-radius option was only added in 6.43, it did not exist in 6.42.7. This difference is not a mistake, it is only different because the setting did not exist before.

radekmacek · Fri Sep 21, 2018 3:50 pm

Hi, we have PPPoE customers and we want to assign IPv6 prefix /56 using Delegated-IPv6-Prefix as well. After some debugging there seems to be same issue in current version 6.43.2.

Radius server sends Delegated-IPv6-Prefix /56 to our router, but no DHCPv6 server is created for the OE tunnel.

If we create IPv6 pool: "OE_pool_v6" /40, prefix /56 , then put it to profile DHCPv6 PD pool. After that, upon connection, DHCPv6 server is created but prefix that it delegates does not match Delegated-IPv6-Prefix /56 sent by Raidus server. It takes first /56 from OE_pool_v6.
Tried the same with Delegated-IPv6-Prefix-pool set. But the result was the same.

I guess mikrotik just ignores received Delegated-IPv6-Prefix and takes the local one. Same behavior for version 6.42.7, 6.43., 6.43.1 and between tile and powerpc. Hope it will be fixed soon. Don't want to create /56 for each customer...

Fri Sep 28, 2018 2:27 pm

6.43 version introduces this feature for DHCP service. You are trying to use it with PPP service. Currently such feature is not supported.

saaremaa · Fri Sep 28, 2018 3:50 pm

You are trying to use it with PPP service. Currently such feature is not supported.

In which version will be support the "Delegated-IPv6-Prefix" attribute for PPPoE ? Very much needed.

thg3x · Fri Sep 28, 2018 10:22 pm

6.43 version introduces this feature for DHCP service. You are trying to use it with PPP service. Currently such feature is not supported.

I dont understand why the Mikrotik-IPv6-Delagated-Pool stop to working in this version while workinkg in previous version, if Mikrotik only introduces the new features for dhcp.
Sounds weird to me!

mducharme · Fri Sep 28, 2018 11:21 pm

6.43 version introduces this feature for DHCP service. You are trying to use it with PPP service. Currently such feature is not supported.
I dont understand why the Mikrotik-IPv6-Delagated-Pool stop to working in this version while workinkg in previous version, if Mikrotik only introduces the new features for dhcp.
Sounds weird to me!

It is not only Mikrotik-Delegated-IPv6-Pool that doesn't work. DHCPv6 prefix delegation over PPP tunnels is completely broken and doesn't work even if you don't use any IPv6 RADIUS attributes. The simple standard configuration of setting the "DHCPV6 PD Pool" in the PPP profile does not work, the client cannot get a DHCPv6 prefix. I do not understand why this is not fixed yet. It is not even possible currently to use this new version for the MikroTik IPv6 engineer training because the config for the training would not work.

gondim · Mon Oct 01, 2018 4:02 pm

Hi all,

What stopped working was the DHCPv6 PD Pool that is in the attached image.

DuhBatista · Mon Oct 01, 2018 6:35 pm

Good afternoon everyone,

In fact, in my tests, the DHCPv6 PD pool no longer works. Either by mikrotik in the ppp profile or via radius the way I used it here.
I have done all the tests in this version, this option is not functional, the DUAL-STACK clients do not receive the prefix via DHCPv6 via DP pool.Pv6 via DP pool

mducharme · Tue Oct 02, 2018 3:15 am

Good afternoon everyone,

In fact, in my tests, the DHCPv6 PD pool no longer works. Either by mikrotik in the ppp profile or via radius the way I used it here.
I have done all the tests in this version, this option is not functional, the DUAL-STACK clients do not receive the prefix via DHCPv6 via DP pool.Pv6 via DP pool

Yes, the same thing is happening to all of us. It has been broken for three weeks now, since 6.43 was released. It essentially breaks IPv6 services for clients.

mducharme · Tue Oct 02, 2018 5:20 pm

Looks like it is fixed in the 6.44 beta:

viewtopic.php?f=21&t=139057&start=50#p689985

*) dhcpv6-server - recreate DHCPv6 server binding if it is no longer within prefix pool when rebinding/renewing;

DuhBatista · Tue Oct 02, 2018 8:36 pm

I'm going to test today.

thg3x · Wed Oct 03, 2018 9:23 pm

Looks like it is fixed in the 6.44 beta:

viewtopic.php?f=21&t=139057&start=50#p689985

*) dhcpv6-server - recreate DHCPv6 server binding if it is no longer within prefix pool when rebinding/renewing;

I did a test yesterday, it worked again as it worked in version 6.42.7, but I still can not get radius to assign the pools, it is still necessary to create the pools in mikrotik. In my understanding nothing new, since the interests us is the full integration with the radius, not to create several pools in Mikrotik and only point these pools in radius.

DuhBatista · Thu Oct 04, 2018 1:45 pm

Truth. What else is to do the log report prefix in delegation, for security reasons to identify the user for future action. You do not have to run v6 without this dhcpv6 log.

marekm · Mon Oct 08, 2018 7:41 pm

Looks like it is fixed in the 6.44 beta:

viewtopic.php?f=21&t=139057&start=50#p689985

*) dhcpv6-server - recreate DHCPv6 server binding if it is no longer within prefix pool when rebinding/renewing;

Does this mean 6.44 will finally support running a dual-stack PPPoE server with RADIUS auth? Or are these fixes still only for DHCP?

mducharme · Mon Oct 08, 2018 8:46 pm

Does this mean 6.44 will finally support running a dual-stack PPPoE server with RADIUS auth? Or are these fixes still only for DHCP?

That fix is for everything, but 6.44 only currently supports the attribute over DHCPv6, not PPP tunnels

I would hope that they are adding support for the attribute to PPP tunnels as well, but haven't heard anything on this yet.

Wed Oct 10, 2018 1:59 pm

While implementing new features in DHCP RADIUS services we did make some changes in a way how DhCPv6 server works and as a result starting from v6.43 some of the DHCPv6 clients could not get prefix. For example, RouterOS DHCPv6 client did work just fine with our server.

Next 6.43 release and 6.44beta21 will contain fix for this problem. So PPPoE with DHCPv6 PD should work exactly the same as it did before v6.43.

marekm · Wed Oct 10, 2018 2:16 pm

Next 6.43 release and 6.44beta21 will contain fix for this problem. So PPPoE with DHCPv6 PD should work exactly the same as it did before v6.43.

So PPPoE *client* will work as it did, but how about PPPoE *server* with DHCPv6 PD and Delegated-IPv6-Prefix attribute (which didn't work without workarounds like manually creating many pools)?

saaremaa · Wed Oct 10, 2018 2:20 pm

So PPPoE with DHCPv6 PD should work exactly the same as it did before v6.43.

manually create pools again? We need to create pools automatically with Radius for PPPoE.

omidkosari · Wed Oct 10, 2018 2:55 pm

So PPPoE with DHCPv6 PD should work exactly the same as it did before v6.43.
manually create pools again? We need to create pools automatically with Radius for PPPoE.

+1

Without that ipv6 for pppoe clients is nightmare .

Wed Oct 10, 2018 3:35 pm

Changes regarding pools are not reverted. Fix changes how "solicit" packet is processed received from DHCPv6 clients that didn't have "Rapid Commit" enabled.

marekm · Wed Oct 10, 2018 7:28 pm

Changes regarding pools are not reverted. Fix changes how "solicit" packet is processed received from DHCPv6 clients that didn't have "Rapid Commit" enabled.

Could you give a clear answer about Delegated-IPv6-Prefix support in PPPoE server? Will it work in 6.44 / 6.45 / 7.x ?

Thu Oct 11, 2018 11:55 am

I will try to clear things up since sees that there has been a huge misunderstanding about RouterOS v6.43 changelog.

RouterOS before v6.43 did not support "Delegated-IPv6-Prefix" in any situations.

Then we added this feature in RouterOS:

*) dhcpv6-server - added additional RADIUS parameters for Prefix delegation, "rate-limit" and "life-time";

As topic of changelog entry states - change is made for DHCP service. We have not made any changes for PPP service.

v6.43, v6.43.1 and v6.43.2 did break communication between RouterOS DHCPv6 server and some DHCPv6 clients and in most cases it was noticeable on PPPoE configurations. Now it is fixed and version with fix will be released soon.

In short, if under "/radius" menu you have selected service "DHCP", then "Delegated-IPv6-Prefix" is supported. If under "/radius" menu you have selected "PPP" service, then "Delegated-IPv6-Prefix" is not supported at the moment.
FF0000
One step at the time - we added "Delegated-IPv6-Prefix" suport for DHCP in v6.43, we will see what we can do about PPP service in future RouterOS releases.

omidkosari · Thu Oct 11, 2018 3:20 pm

Thanks for clarification and hope for implement same feature for ppp in near time

littlecake · Thu Oct 11, 2018 4:45 pm

I hope also that they will do it, we are doing this think wery dirty way with scripts on AP and client side now.

Thu Oct 11, 2018 5:52 pm

While feature is not implemented, you may use such workaround:

1) Add new pool with prefix that you want to assign to your PPPoE client;
2) Add new PPP profile and select this pool;
3) Send from RADIUS "Mikrotik-Group" parameter which is equal with this profile name.

This option is present in RouterOS starting from v6.42:
*) ppp - allow to override remote user PPP profile via "Mikrotik-Group"

marekm · Thu Oct 11, 2018 7:51 pm

1) Add new pool with prefix that you want to assign to your PPPoE client;
2) Add new PPP profile and select this pool;
3) Send from RADIUS "Mikrotik-Group" parameter which is equal with this profile name.

The workaround may be fine when testing IPv6 on just a few customers, but doesn't scale well to hundreds/thousands of them.
The confusion is probably a result of IPv6 PPPoE also using DHCPv6 over link-local addresses configured by IPv6CP (unlike IPv4 PPPoE which configures global IPv4 addresses using IPCP, without DHCP). So when you say you fixed DHCPv6 with RADIUS attributes, it wasn't clear that PPPoE is a special case which is not yet supported.

mducharme · Sat Oct 20, 2018 2:37 am

I did a test yesterday, it worked again as it worked in version 6.42.7, but I still can not get radius to assign the pools, it is still necessary to create the pools in mikrotik. In my understanding nothing new, since the interests us is the full integration with the radius, not to create several pools in Mikrotik and only point these pools in radius.

This fix from 6.44beta is now supposedly in 6.43.4 but I am still having the same problem, whereas 6.42.7 worked fine. I'm wondering if they somehow accidentally left the fix out of 6.43.4 even though it is in the changelog. Can you test the behavior on your side with 6.43.4?

DuhBatista · Mon Oct 29, 2018 7:05 pm

6.44beta28

DHCPv6 running by lightning. Still looking forward to the PD log by Radius.

saaremaa · Wed Nov 14, 2018 3:41 pm

Any news?

fredyz · Tue Nov 27, 2018 6:14 pm

Well, a couple of weeks has passed and not signal of Delegated-IPv6-Prefix being implemented to PPP as well. It took so long for this to happen for DHCP so I hope it doesn't take the same time for PPP as well.

Seems the same people responsible to handle this are in charge for quiet a while with the same practises regardless if people using are satisfied or not.

On the top of that seems there is no understand how many ISPs are affected by the lack of this feature and how this is holding IPv6 adoption in many places as the lack of this features stops ISPs from getting the radius log of which prefix was given to a customer. And we are not asking for something "nice to have" or cosmetic.

How long more !

DuhBatista · Tue Nov 27, 2018 10:19 pm

Good afternoon,
I do not know how you talk about ipv6 with routerOS for years with this pending. We are all affected by this question.

littlecake · Tue Nov 27, 2018 10:37 pm

i do not understand Mikrotik in this case.
I hope before that mikrotik wil implement this feature, now i am looking for alternative.
Our network was running completely with mikrotik.
After comes 802.11n the mikrotik radios was bad , we implement UBNT.
Now we are running routers from mikrotik... after few years it seems that mikrotik will go completely out from our network.
I am sad, that the change will take lot of work, but i cannot accept that we will not implement IPv6 only because the mikrotik is not able to do IPv6 PD.

saaremaa · Tue Nov 27, 2018 10:41 pm

I fully agree with the message littlecake. We have a similar situation.
In the radio, we already changed Mikrotik to another vendor.
MPLS - we are looking for an alternative vendor.

omidkosari · Wed Nov 28, 2018 9:41 am

Mikrotik is expected to be more agile than the other companies but unfortunately it's the opposite

saaremaa · Fri Dec 21, 2018 11:34 am

6.43.8 (2018-Dec-21 07:10) no news and changes. Does anyone in MikroTik deal with this problem?

DuhBatista · Sat Dec 22, 2018 4:30 am

when we will have a novelty about a smooth operation, report prefix delegation. An alternative was presented in the GTER for PD logging
ftp://ftp.registro.br/pub/gter/gter46/
slide number 7

mducharme · Sun Dec 23, 2018 1:18 pm

I have hope that they are still working on this and on IPv6 RADIUS accounting. They seem to have prioritized IPv6-related enhancements in the past year or so, judging by the change logs.

marekm · Mon Dec 24, 2018 4:44 pm

+1
Mikrotik, please tell us some estimated timeframe when this feature will be finished, so we can decide: wait longer, or go with accel-ppp on Linux instead (it's a lot of work, so it would not be fun to do all this work only to find out it was unnecessary because you finally implemented this feature).

mducharme · Mon Dec 24, 2018 8:31 pm

We have been using a workaround for now, although I'm not sure whether it will work for everybody, if it does help someone I can post the script. We have a script that runs that turns any dynamic DHCPv6 PPPoE bindings into static bindings, so that if the customer disconnects and reconnects, they get the same lease. It also copies the pppoe interface name to the comment so that we know which user the binding is for.

DuhBatista · Mon Dec 24, 2018 11:24 pm

We have been using a workaround for now, although I'm not sure whether it will work for everybody, if it does help someone I can post the script. We have a script that runs that turns any dynamic DHCPv6 PPPoE bindings into static bindings, so that if the customer disconnects and reconnects, they get the same lease. It also copies the pppoe interface name to the comment so that we know which user the binding is for.

Dear friend, I could post the script.

mducharme · Tue Dec 25, 2018 1:40 am

Dear friend, I could post the script.

Here it is - we run this every 5 minutes using the scheduler:

/ipv6 dhcp-server binding;
:foreach i in=[find server~"pppoe"] do={
  make-static $i;
  set $i comment=[get $i server];
  set $i server=all;
}

It works well and users always get the same prefix after disconnecting and reconnecting. It is really just a temporary solution for us until the better solution of Delegated-IPv6-Prefix becomes available.

Because static bindings will be backed up with the router configuration backup by Oxidized, we can look in there to see what user has what binding.

I was also toying with the idea of writing a parser that would look through the backed up config from RouterOS and update RADIUS mysql accounting table with the Delegated-IPv6-Prefix, as though it were being given by RouterOS itself, as a workaround for the lack of accounting. However it wasn't a big deal for us because we only have a few PPPoE concentrators and we tunnel all customers back to these concentrators.

@saaremaa and @marekm is this workaround useful for you at all?

DuhBatista · Tue Dec 25, 2018 6:21 am

Dear friend, I could post the script.
Here it is - we run this every 5 minutes using the scheduler:
Code: Select all
/ipv6 dhcp-server binding;
:foreach i in=[find server~"pppoe"] do={
  make-static $i;
  set $i comment=[get $i server];
  set $i server=all;
}
It works well and users always get the same prefix after disconnecting and reconnecting. It is really just a temporary solution for us until the better solution of Delegated-IPv6-Prefix becomes available.

Because static bindings will be backed up with the router configuration backup by Oxidized, we can look in there to see what user has what binding.

I was also toying with the idea of writing a parser that would look through the backed up config from RouterOS and update RADIUS mysql accounting table with the Delegated-IPv6-Prefix, as though it were being given by RouterOS itself, as a workaround for the lack of accounting. However it wasn't a big deal for us because we only have a few PPPoE concentrators and we tunnel all customers back to these concentrators.

@saaremaa and @marekm is this workaround useful for you at all?

Okay, thanks for the tip.

I can aggregate to a separate log server for better control of the delegate prefix.

Hello good afternoon,
I also made this scritp to make a copy of the daily static PD for future analysis, sending to a technical email.

Code: Select all

/ipv6 dhcp-server export verbose file=IPv6LOG-PD

:log info message="enviando LOGIPV6PD por email"

:delay 5s

:global data [/system clock get date]

:global hora [/system clock get time]

:global nome [/system identity get name]

/tool e-mail send to="noc@empresa.com.br" subject="IPV6LOGPD $nome - $data às $hora" body="IPV6LGPD $nome realizado às $hora de $data." file=IPv6LOG-PD.rsc start-tls=yes

:log info message="backup do log PD enviado!"

saaremaa · Tue Dec 25, 2018 3:32 pm

@saaremaa and @marekm is this workaround useful for you at all?

In my case, this method will not help. It is required that the binding of the prefix to the client's account be in the billing and issued by the Radius attribute. This is a requirement of Roskomnadzor (Russia).

saaremaa · Tue Feb 05, 2019 11:20 pm

Any news? It seems to me - again, no.

DuhBatista · Fri Feb 08, 2019 3:27 pm

Until now, no one on the team gives anything. Terrible.

remontti · Tue Feb 19, 2019 7:04 pm

Unfortunately the team has not yet deployed the Delegated-IPv6-Prefix.

It is by these and others that people have been abandoning mikrotik.

I hope you're ashamed in the face.

We have been expecting this since 2014.
5 years waiting.
it's ridiculous!

DuhBatista · Tue Feb 19, 2019 10:44 pm

Good afternoon

Inevitably stay that way, a matter of extreme complexity, and mikrotik has not done anything yet so we can move forward.

Wrong

saaremaa · Tue Feb 26, 2019 10:26 pm

viewtopic.php?f=21&t=145793&p=717609#p717609

marlow · Wed Feb 27, 2019 12:15 am

Unfortunately the team has not yet deployed the Delegated-IPv6-Prefix.

It is by these and others that people have been abandoning mikrotik.

I hope you're ashamed in the face.

We have been expecting this since 2014.
5 years waiting.
it's ridiculous!

Hang on. .. 2014 ?

What sort of dreamland do you live in ? I have been asking for these kind of features, when 2.9 was stable.. and that is a long time before that.

Anyhow ...since before 2008 anyhow ..

I have tickets to prove it. Yet ignored.

/M

ft897d · Wed Feb 27, 2019 1:00 pm

Dear support, please tell me when the company MikroTik plans to implement the support of "Delegated-IPv6-Prefix" radius attribute for PPP services?

ft897d · Thu Feb 28, 2019 1:15 pm

Dear support, please tell me when the company MikroTik plans to implement the support of "Delegated-IPv6-Prefix" radius attribute for PPP services?

Hello,

It is in our plans to implement such functioality, however, I can not provide any ETA.

Best regards,
Martins S.

(((((

omidkosari · Sun Mar 03, 2019 12:23 pm

viewtopic.php?f=21&t=145793&p=717609#p717667

saaremaa - What is the question here actually? Delegated-IPv6-Prefix is already working for DHCP service (RADIUS). Such parameter is not available yet for PPP service. If you make PPPoE server which then distributes addresses by using DHCP service, then this will not work since users are authenticated by using PPP service, not DHCP;

saaremaa · Sun Mar 03, 2019 12:27 pm

viewtopic.php?f=21&t=145793&p=717609#p717900

saaremaa - Sorry about that. I mixed both services together. We do support Delegated-IPv6-Prefix for DHCP service but not for PPP yet. It is in our plans to add support for this in the future;

littlecake · Sun Mar 03, 2019 12:28 pm

But nobody knows how far is the "future"

remontti · Wed Mar 20, 2019 9:56 pm

viewtopic.php?f=21&t=145793&p=717609#p717667

saaremaa - What is the question here actually? Delegated-IPv6-Prefix is already working for DHCP service (RADIUS). Such parameter is not available yet for PPP service. If you make PPPoE server which then distributes addresses by using DHCP service, then this will not work since users are authenticated by using PPP service, not DHCP;

Everyone coming out of RouterOS exactly because they have not yet deployed Delegated-IPv6-Prefix with PPPoE. This update of you is useless to the vast majority.
We have been clamoring for this functionality for years. It is a disregard for users.
Hope to see this working on an update.

All other companies competing with mikrotik are already compatible with Delegated-IPv6-Prefix + PPPoE.
is being charged to do
IPv6 is being charged to be implanted.
When a large company (example google) deactivate their IPv4, is Mikrotik will lose many customers
Sorry for my English.

DuhBatista · Sun Mar 24, 2019 8:21 pm

inadmissible

marekm · Thu Mar 28, 2019 10:30 pm

On a positive side, lack of this feature may have kept many people safe from this soon to be disclosed vulnerability:
viewtopic.php?f=2&t=147048
viewtopic.php?f=2&p=723809

Stop IPv6 deployment, or move from MT to something else (Cisco, Linux + BIRD + accel-ppp, ...) so you can deploy IPv6 anyway = not vulnerable

Since it was known internally for about a year, perhaps it was the real reason support was not telling anyone why it takes so long to implement Delegated-IPv6-Prefix.

marlow · Mon Apr 01, 2019 12:39 pm

Nah. Requests for Delegated-IPv6-Prefix on PPPoE go back to ROS 3.x

And thats a decade ago.

It is just disregard of Mikrotiks customers.

/M

fredyz · Mon Apr 08, 2019 6:56 pm

That's a cultural thing within Mikrotik it seems. Looks like the development and the organization of the priorities is messed up and the same person (or similar people) are in charge for a long time and refuses even to acknowledge there are serious issues regarding organization.They probably feel better believing that keeping the same way of doing things and dismissing everything else they may not like to hear is the right way to go.

Nah. Requests for Delegated-IPv6-Prefix on PPPoE go back to ROS 3.x

And thats a decade ago.

It is just disregard of Mikrotiks customers.

/M

petrb · Thu Apr 11, 2019 12:14 pm

I want to deploy a combination of the VPLS+PPPoE+Delegated-IPv6-Prefix. Most of the cheap devices cannot do this at the once

. Basic linux distribution have poor implementation of the VPLS. MK please implement "Delegated-IPv6-Prefix" attribute for PPPoE. Thanks

CoMMyz · Mon Apr 22, 2019 3:01 am

We need this please done - the need for IPv6 over Radios with PPPoE is a use case for most ISP's out there.

ntmanxp · Sat Apr 27, 2019 5:03 pm

+1
Testing Latest ROS 6.44.3, same situation!

marekm · Mon Apr 29, 2019 1:09 pm

For anyone looking for alternatives (on x86 hardware), VyOS now includes accel-ppp which supports Delegated-IPv6-Prefix.

saaremaa · Mon Apr 29, 2019 1:22 pm

We gradually abandon Mikrotik as BRAS and migrate to VAS Experts DPI BRAS There are many more MPLS from Mikrotik in the network, but because of the absence of FRR, I also want to leave

petrb · Mon Apr 29, 2019 2:23 pm

For anyone looking for alternatives (on x86 hardware), VyOS now includes accel-ppp which supports Delegated-IPv6-Prefix.

vyos not support VPLS

.... or documentation is poor

marlow · Mon May 06, 2019 9:51 pm

For anyone looking for alternatives (on x86 hardware), VyOS now includes accel-ppp which supports Delegated-IPv6-Prefix.

Jup. I'm already testing accel-ppp on Edgerouter Infinity and also looking at cross-compiling the package for Edgerouter X. Mikrotik seem to have no interest in the need of their customers.

/M

petrb · Sat Jun 29, 2019 7:45 pm

I gave up the idea of implementing PPPoE delegated-ipv6-prefix and use DHCP and 802.1x for network configuration.

How it works:
1. I have a freeradius with 802.1x authentification, store Calling-Station-Id after successful EAP.
2. DHCPv4 and DHCPv6 server at the MK is connected to the radius.
3. At the freeradius rewrite policy to pair DHCP"username" attribute and "Calling-Station-Id" to find EAP"username".
4. Freeradius send correct framed-ip-address, framed-route, delegated-ipv6-prefix, Mikrotik-Rate-Limit, Mikrotik-address-list

Results:
- Works perfect for IPv4.
- IPv6 not work for MK CPE (DHCP username attribute for IPv4 and IPv6 are different - mac vs duid ......... long story)
- IPv6 works perfect for UBNT CPE (same username attribute for IPv4 and IPv6 DHCP client)

Until DHCP option 79 will be implemented, you can use Kea as dhcp server instead Mikrotik.

Next sollution for the future will be DHCPv6 op 79 - Client Link-Layer Address Option
viewtopic.php?f=2&t=149399

Until DHCP option 79 will be implemented, you can use Kea as dhcp server instead Mikrotik.

ricardobrock · Tue Jul 16, 2019 9:21 am

+1
Any update about this from Mikrotik??? We have multiple CCR1072-1G-8S+ running only for PPPoE and my customers would like to use IPv6.
@Mikrotik, this post is from 2014, should I start buying other routers for PPPoE? If there would be any information about this FR, just to give people (network engineers) headsup when they can expect something?

interprime · Tue Jul 16, 2019 10:18 pm

+1 since 2014

ntmanxp · Wed Jul 17, 2019 6:47 pm

+1 again!
But what about latest version?
"dhcpv6-server - override prefix pool and/or DNS server settings by values received from RADIUS;"
Could it be related?

ricardobrock · Thu Aug 29, 2019 9:40 pm

@Mikrotik Amy response?

Ripe says IPv4 is done by then end of this year.

tdamas · Wed Sep 04, 2019 9:39 pm

WORKING since 6.45.1:
*) dhcpv6-server - added additional RADIUS parameters for Prefix delegation, "rate-limit" and "life-time";

For now, it need to activate the "dhcp" option under RADIUS configuration to log accounting packets.

petrb · Wed Sep 11, 2019 10:41 am

dhcpv6 PD is not PPPoE PD

dibatech · Thu Sep 19, 2019 5:07 pm

@Mikrotik: This must be really difficult to impliment....

pietroscherer · Thu Sep 19, 2019 5:45 pm

Anyone tested on 6.45.x ?

edurosso · Tue Sep 24, 2019 3:50 am

Anyone tested on 6.45.x ?

Hi Pietro, glad to see you.
I just tested on 6.45.6. For PPPoE, sending "Delegated-IPv6-Prefix" attribute did not work. I found that enabling "dhcp" option in RADIUS Client resulted on RouterOS sending "Delegated-IPv6-Prefix" to RADIUS Server, but not for PPPoE connections, only for DHCPv6.
So, until MikroTik releases full support for "Delegated-IPv6-Prefix" for PPPoE, I am using "Mikrotik-Delegated-IPv6-Pool" instead. But this is not a solution, it is a workaround because this way I need to create the pools, and therefore, RADIUS Server don't receive PD information from RouterOS via accounting or access/accept requests. RADIUS receives back only the "Framed-IPv6-Prefix" (WAN).

jindranix · Wed Oct 02, 2019 12:51 pm

Yes, it is really annoying. this small thing is missing to full dual-stack support on PPPoE.

danunjaya123 · Fri Oct 04, 2019 12:56 pm

I have configured PPPoE on IPv6 for my customers on different Vlan's, Now i have got issue in this when i did PPPoE Dail at customer end getting IPv6 IP and showing IPv6 for my PC but not able to get browsing on IPv6 traffic, For this i have found that it was IPv6 DNS issue.

When i dail On PPPoE getting IP only not getting DNS of IPv6.

Let us we know how DNS will reach the customer when dailup.

Is IPv6 Support Hotspot?, I need to give for some of my customers on DHCP mode so they are getting IP but not able to redirect to Radius.

I have CCR-1036