Dear FreeRadius users, I need to implement IP Pool into FreeRadius because I have multiple PPPoE Server. Reading about "_ippool/_sqlippool" I've found many issues (for example a bug that assign double IP). Are there same problem with the new version of FreeRadius (3.x) ? I've not enough IP to split my IP pools into multiple PPPoE server. (example 33% IPs of my ALL IPs into 3 PPPoE server) Regards, Man.
On May 28, 2015, at 8:33 AM, manman <mbaldov@gmail.com> wrote:
Reading about "_ippool/_sqlippool" I've found many issues (for example a bug that assign double IP).
No. The "assign double IP" problem happens because FreeRADIUS assumes that the NAS works properly. If the NAS doesn't work properly, then duplicate IPs can be assigned. i.e. FreeRADIUS sends a Session-Timeout of 3600 to the NAS. The NAS is SUPPOSED to kick the user off after an hour. So after an hour, FreeRADIUS assumes that the user is kicked off. If the NAS is broken, it may let the user stay on the network after the hour is up. The only solution to this problem is to buy a NAS that works.
Are there same problem with the new version of FreeRadius (3.x) ?
Buggy NASes exist. No amount of poking FreeRADIUS can fix a buggy NAS. Alan DeKok.
Hello Alan, thanks for your reply. My idea is to build a "full failover" infrastructure with: - 2 PPPoE Server - 2 Radius Server with MySQL (MySQL in cluster active/active) Is it possible? As PPPoE server I'm thinking about Mikrotik devices (good CPU/Ethernet with good price/preformance). They also support bandwidht profiles Have you other suggestions for do this and which PPPoE server I need (other vendors) ? Thanks again Man 2015-05-28 15:12 GMT+02:00 Alan DeKok <aland@deployingradius.com>:
On May 28, 2015, at 8:33 AM, manman <mbaldov@gmail.com> wrote:
Reading about "_ippool/_sqlippool" I've found many issues (for example a bug that assign double IP).
No. The "assign double IP" problem happens because FreeRADIUS assumes that the NAS works properly. If the NAS doesn't work properly, then duplicate IPs can be assigned.
i.e. FreeRADIUS sends a Session-Timeout of 3600 to the NAS. The NAS is SUPPOSED to kick the user off after an hour. So after an hour, FreeRADIUS assumes that the user is kicked off.
If the NAS is broken, it may let the user stay on the network after the hour is up. The only solution to this problem is to buy a NAS that works.
Are there same problem with the new version of FreeRadius (3.x) ?
Buggy NASes exist. No amount of poking FreeRADIUS can fix a buggy NAS.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On May 28, 2015, at 9:22 AM, manman <mbaldov@gmail.com> wrote:
My idea is to build a "full failover" infrastructure with:
- 2 PPPoE Server - 2 Radius Server with MySQL (MySQL in cluster active/active)
That should work.
As PPPoE server I'm thinking about Mikrotik devices (good CPU/Ethernet with good price/preformance). They also support bandwidht profiles
Have you other suggestions for do this and which PPPoE server I need (other vendors) ?
No idea, sorry. There are dozens of vendors, each of whom has dozens of products. I don't keep up with all of them. Alan DeKok.
participants (2)
-
Alan DeKok -
manman