This bug has been open for getting on for a year! I’m running 5.17 and still not fixed…I can overcome it using the workaround if I set the queue manually, but I’m looking for a way to do this using Radius queue creation.
i.e. Is there a Radius option to to set argument dst-address=::/0
If not, please can you escalate this? I can’t roll out IPv6 to my customers til this is fixed…
if i understood you correctly, then Hotpost is the only way how to work with RADIUS server and hotspot knows nothing about ipv6 therefore queues that are added via hotspot+radius does not know anything about ipv6 too.
However, if you want to limit ipv6 traffic you can add manually queues for ipv6 using PCQ queue type that can be configured to work with ipv6.
Hi
No, I think you’ve misunderstood me. I’m not using Hotspot at all. I have a separate Freeradius server, which sets a dynamicly generated Simple Queue with rate limit for each pppoe customer login.
IPv6 packets going through the pppoe interface are not being rate limited by the queue. IPv4 packets are.
The queue should be rate limiting both types of IP Packets, and it is not. This has to be a bug…
Please can you see if you can reproduce it, and advise of a likely fix?
I run a wget download through the queue from server A onto my laptop, B. using ipv4, the queue rate limits to 16 mbit. Using Ipv6, it does not rate limit.