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.
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 .
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
Hey, Mikrotik guys!? Answer something about “Delegated-IPv6-Prefix” attribute for PPPoE and IPv6-Accounting? Should we wait or look for another vendor?
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.
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
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
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)
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 