sqlippool and MySQL/InnoDB: Useable for production?
Hello FreeRadius Users. I have a question about sqlippool and I would be glad if you could share your opinions with me/the list: Is the module sqlippool useable for production if MySQL is used with InnoDB tables? I found the information, that transaction support of your SQL backend is important, but MySQL seems to support transactions with InnoDB. I'm asking because I was told, that there is still an issue if you use sqlippool with more one NAS: The same IP addresses could be given to different clients if you use MySQL - even with InnoDB. What is your experience? Would you advise to use a different SQL backend (PostgreSQL for example)? Would you advise, not to use sqlippool at all? How do you handle a pool of ip addresses if you have more than one NAS and it's not possible to handle the pool on each NAS? Thanks in advance! Sebastian
Sebastian Inacker wrote:
Is the module sqlippool useable for production if MySQL is used with InnoDB tables?
Yes.
I found the information, that transaction support of your SQL backend is important, but MySQL seems to support transactions with InnoDB. I'm asking because I was told, that there is still an issue if you use sqlippool with more one NAS: The same IP addresses could be given to different clients if you use MySQL - even with InnoDB.
That doesn't happen.
What is your experience? Would you advise to use a different SQL backend (PostgreSQL for example)? Would you advise, not to use sqlippool at all?
Use what you're familiar with. If you don't know either MySQL or PostgreSQL, choose Postgres. It's a real SQL database.
How do you handle a pool of ip addresses if you have more than one NAS and it's not possible to handle the pool on each NAS?
Use SQL IP Pools. Alan DeKok.
Hello Alan. On 13 February 2014 15:12, Alan DeKok <aland@deployingradius.com> wrote:
Is the module sqlippool useable for production if MySQL is used with InnoDB tables? Yes.
Good news. So the warning # WARNING: MySQL has certain limitations that means it can # hand out the same IP address to 2 different users. in raddb/sqlippool.conf is obsolete if you follow the advice to use MySQL with InnoDB, which can be found at the same place? # We suggest using an SQL DB with proper transaction # support, such as PostgreSQL, or using MySQL # with InnoDB. (Just for the record: raddb/sql/mysql/ippool.sql is useing "ENGINE=InnoDB".) Thanks, Sebastian
participants (2)
-
Alan DeKok -
Sebastian Inacker