+1
tks
+100500
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?
+1
Awaiting a solution…
Yes, it is terrible solution, but is very easy to prepare it.
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.
IMHO no sense, but +1
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.
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?
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.
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)
+1 for the glorious feature. Can’t fully implement dynamic IPv6 for customers without RADIUS being able to record delegated prefixes.
+1 for this feature
Scripting all pppoe hubs with all prefix list is being a hustle.
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
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
IPv6 Delegated prefix +1
IPv6 accounting +1
+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
+1 !!!
+1 !!