Koozali.org: home of the SME Server

Obsolete Releases => SME Server 7.x => Topic started by: brit-dub on May 29, 2006, 09:54:47 AM

Title: mysql from wan
Post by: brit-dub on May 29, 2006, 09:54:47 AM
Hi

I’m running a radius server for hotspots and would like to know if I can get it to use the mysql on the sme server from the wan side ? it would save me having to build another pc just to do that.

Or could this open up to many possible holes to the outside world ?

Regards

Brit
Title: Re: mysql from wan
Post by: cactus on May 29, 2006, 10:32:19 AM
Quote from: "brit-dub"
Hi

I’m running a radius server for hotspots and would like to know if I can get it to use the mysql on the sme server from the wan side ? it would save me having to build another pc just to do that.
Yes you can.
Code: [Select]

config setprop mysqld LocalNetworkingOnly no
config set mysqld service access public status enabled TCPPort 3306
signal-event remoteaccess-update
signal-event reboot


You might have to create a port forward rule from your servers WAN ip to the localhost for the mysql port to get everything working. This can be done using the server-manager.

Quote from: "brit-dub"
Or could this open up to many possible holes to the outside world ?

Regards

Brit
This opens up the 3306 port to the outside world so there is a security issue of course. Maybe you can configure the port to only allow hosts from the radius ipsubnet combination as I guess the radius device has a fixed IP. Ofcourse you also need to keep in mind the security of your radius access point and the mysql security rights and password strength.
Title: Re: mysql from wan
Post by: CharlieBrady on May 29, 2006, 05:41:45 PM
Quote from: "cactus"

Code: [Select]

config setprop mysqld LocalNetworkingOnly no
config set mysqld service access public status enabled TCPPort 3306
signal-event remoteaccess-update
signal-event reboot


You might have to create a port forward rule from your servers WAN ip to the localhost for the mysql port to get everything working.


You shouldn't need to. "access public TCPPort 3306" should be sufficient. You should report   a bug if it's not.