INSERT INTO web_count (name, counter) VALUES (‘test.htm’, 1) ON duplicate KEY UPDATE counter = counter + 1

service iptables status

Start iptables if the service is not running.  You should also set iptables to load on boot as well.  This can be achieved using the following command:

chkconfig -level 345 iptables on

Now that you know iptables is running, you can begin adding the new rules for allowing only specific ip addresses to connect to your mySQL database.
Note: If you do not want any external connections to your mySQL database, you can also edit the my.conf file located by default under /etc/my.cnf.  Simply add bind_address = 127.0.0.1 under [mysqld], and restart the mysql service.  mySQL will now deny all external connections.

For this example, I’m going to allow access from 3 servers, and deny every other address.  Execute the following commands in order, and replace IP address 1, 2, and 3 with the addresses of your servers.

iptables -A INPUT -p tcp -s IPaddress1/32 --dport 3306 -j ACCEPT
iptables -A INPUT -p tcp -s IPaddress2/32 --dport 3306 -j ACCEPT
iptables -A INPUT -p tcp -s IPaddress3/32 --dport 3306 -j ACCEPT
iptables -A INPUT -p tcp --dport 3306 -j DROP

When configuring iptables, order is important.  The effects of each command are immediate, but you must save your iptables settings or you’ll lose them on your next restart.  Do this by issuing the following command:

service iptables save

You iptable settings are now saved, and will be used next time iptables is restarted.  By default in Red Hat, and centOS, the settings are stored here: /etc/sysconfig/iptables viagra

The issue with adding custom 404 error pages to your WordPress site is due to WordPress using Apache’s rewrite on your entire site.  In order to prevent this from happening on your subdirectory, you need to add a .htaccess file with the following code:

<IfModule mod_rewrite.c>
RewriteEngine Off
</IfModule>

ErrorDocument 404 /subdirectory/404.html

This code prevents URL rewrites on your subdirectory, and specifies your custom 404 error page.  The 404 error page should link to the custom file you want to display to your visitors.

Here’s a link to some stylish 404 error pages.
http://dzineblog.com/2008/11/custom-error-404-pages.html

If you’re still having trouble with getting your custom error page to display, make sure that your subdirectoy has the AllowOverride permission set in your Apache configuration.  In your Apache configuration, you can set AllowOverride on that directory with this code:

<Directory “/path/to/your/wordpress/subdirectory”>
AllowOverride All
</Directory>

Step 2: Configuration
Stunnel needs to be configured to create a connection from the port which will allow remote connections (ie: 14333) to the Microsoft SQL Server port (1433). All connections to port 14333 on the server will be encrypted. On your server, set port 14333 to accept remote TCP connections, and make sure to block all remote connections to port 1433 from the Internet. Configuration may vary depending on your network structure, but only the secure port should be accessible from outside your network. You can even restrict access to the secure port further by only accepting connections from specific IP addresses.

Now, lets modify the Stunnel configuration file.  You can access the configuration file from the start menu in the stunnel program folder, there is an icon that says “Edit stunnel.conf”.

Paste the following into the stunnel configuration:

cert = stunnel.pem
debug = 7
output = stunnel.log

[mssql]
accept = EXTERNAL_IP:14333
connect = 127.0.0.1:1433

Replace EXTERNAL_IP with the IP address of your server. This configuration tells stunnel to use stunnel.pem for the security certificate – by default located under c:\program files\stunnel.pem. All debug output is logged to the stunnel.log file.
Make sure your MSSQL server accepts connections on 127.0.0.1 and port 1433, otherwise you may need to change this information, or modify your SQL configuration.

Step 3: Security Certificate
You will need a security certificate for the encryption to work.  Here’s a site reference for creating the .pem certificate http://panoptic.com/wiki/aolserver/How_to_generate_self-signed_SSL_certificates.

Step 4: Start the service
For testing, you don’t have to start the program as a service, just run “Run stunnel” under the stunnel program folder in the start menu. This should add an icon to your task bar. You can see debug information in the console output if you double click that icon. If everything is configured properly, remote clients should be able to connect to that port, and have all data sent over the Internet encrypted.