#1  
Old 15th August 2006, 01:57
punto punto is offline
Member
 
Join Date: Jul 2006
Posts: 84
Thanks: 12
Thanked 2 Times in 1 Post
Default Firewall ACLs

Hi I have installed ISPconfig and must say think it is a fantastic application , thankyou so much to the developers.

I was wondering if it is possible to configure the ISPconfig firewall so that you can limit ssh access to certain IP addresses?

With my other linux server I have an explicit REJECT in /etc/sysconfig/iptables for port 22 and then just add an ACCEPT in for the source IP addresses I want to accept and it works well.

-A RH-Firewall-1-INPUT -p tcp -m tcp -s 172.16.8.35 --dport 22 --syn -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 22 --syn -j REJECT


Where is the script or config file for the ISPconfig firewall? Can I manually edit the script without breaking anything? I dont like having ssh access open to anyone.

Thanks in advance

Matt.
Reply With Quote
Sponsored Links
  #2  
Old 15th August 2006, 09:37
till till is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 36,733
Thanks: 840
Thanked 5,596 Times in 4,407 Posts
Default

The script is:

/etc/Bastille/bastille-firewall.cfg

You will have to change the master file too:

/root/ispconfig/isp/conf/bastille-firewall.cfg.master

Then run:

/etc/init.d/bastille-firewall restart
__________________
Till Brehm
--
Get ISPConfig support and the ISPConfig 3 manual from ispconfig.org.
Reply With Quote
  #3  
Old 15th August 2006, 13:14
punto punto is offline
Member
 
Join Date: Jul 2006
Posts: 84
Thanks: 12
Thanked 2 Times in 1 Post
Default

Great, thanks Till.

Regards

Matt
Reply With Quote
  #4  
Old 22nd August 2006, 15:26
punto punto is offline
Member
 
Join Date: Jul 2006
Posts: 84
Thanks: 12
Thanked 2 Times in 1 Post
Default

Quote:
Originally Posted by till
The script is:

/etc/Bastille/bastille-firewall.cfg

You will have to change the master file too:

/root/ispconfig/isp/conf/bastille-firewall.cfg.master

Then run:

/etc/init.d/bastille-firewall restart
I found that I wasnt able to add ACLs directly to the bastille-firewall.cfg script.

After doing some reading, here is my how-to and hopefully others will find it useful:

In this case I want to restrict ssh access to only one IP address (you can configure it for any number depending on your needs)

I order to restrict access to certain source IPs for certain protocols, using the Bastille-firewall setup you need to firstly create a new directory under /etc/Bastille. This directory needs to be called firewall.d

#cd /etc/Bastille
#mkdir firewall.d


You then need to create a new file within the newly created directory called post-rule-setup.sh

#cd firewall.d
#vi post-rule-setup.sh


This is the file where any IPTABLES rules can be entered. When you restart bastille.cfg the script is read and the rules applied. A knowledge of IPTABLES is required but once you get the hang of it, it is easy enough.
So in my case I want to allow ssh access to only 123.34.56.789 and deny it to ALL other IP addresses, so my post-rule-setup.sh file will look like this:

/sbin/iptables -I INPUT -p tcp -m tcp -s 123.34.56.789 --dport 22 --syn -j ACCEPT
/sbin/iptables -I INPUT -p tcp -m tcp --dport 22 --syn -j REJECT


The first line accepts ssh (tcp port 22) connections only from 123.34.56.789 and the second line denies ALL other source IP addresses. If there is no match in this case 123.34.56.789 then all traffic bound for port 22 will be denied.

Ok now we have our rule we need to restart bastille.cfg

#/etc/init.d/bastille-firewall restart

A successfully read script will yield the following

Setting up IP spoofing protection... done.
Allowing traffic from trusted interfaces... done.
Setting up chains for public/internal interface traffic... done.
Setting up general rules... done.
Setting up outbound rules... done


The last line is the one we are interested in. If your IPTABLES rules are not understood or written incorrectly then you will get the following output when you restart bastille.cfg

Setting up IP spoofing protection... done.
Allowing traffic from trusted interfaces... done.
Setting up chains for public/internal interface traffic... done.
Setting up general rules... done.
Setting up outbound rules..../post-rule-setup.sh: line 5: -I: command not found
done


You will need to go back into your post-rule-setup.sh and modify it.

You can specify a subnet simply by using for example 192.168.0.0/24 notation in your rule set

Cheers

Matt
Reply With Quote
  #5  
Old 23rd August 2006, 16:19
falko falko is offline
Super Moderator
 
Join Date: Apr 2005
Location: Lüneburg, Germany
Posts: 41,701
Thanks: 1,900
Thanked 2,747 Times in 2,578 Posts
Thumbs up

That's a great solution.
__________________
Falko
--
Download the ISPConfig 3 Manual! | Check out the ISPConfig 3 Billing Module!

FB: http://www.facebook.com/howtoforge

nginx-Webhosting: Timme Hosting | Follow me on:
Reply With Quote
  #6  
Old 19th August 2014, 23:48
skycity skycity is offline
Junior Member
 
Join Date: Jul 2014
Posts: 5
Thanks: 2
Thanked 2 Times in 2 Posts
Default

I realize this thread is (really) old, but for those who arrive via searching for this solution- its important to note that if you use the commands given in the previous example, you will effectively block ssh completely. Using "-I" inserts the rule into the top of the chain by default, so the rule rejecting all ssh traffic ends up being the first rule in the chain.

Personally, I do something similar to this:

###############################################
##/etc/Bastille/firewall.d/post-rule-setup.sh
##Uncomment statements/rules per your requirements
##
#ip_address=<trusted_admin_IP>
#ssh_port=<22 or your_ssh_port>
#ispconfig_admin_port=<8080 or your_ispconfig_port>
#mysql_ip=<trusted_MySQL_IP>
#mysql_port=<3306 or your_MySQL_port>
#iptables=</sbin/iptables or path to your iptables>

##restrict access to the ISPConfig web interface to one or more specific IPs
#$iptables -I PUB_IN -p tcp -s $ip_address --dport $ispconfig_admin_port -j ACCEPT

##restrict ssh access to one or more specific IPs (make sure you have an
##alternate method of access in case your IP changes)
#$iptables -I PUB_IN -p tcp -s $ip_address --dport $ssh_port -j ACCEPT

##restrict MySQL access to one or more specific IPs
#$iptables -I PUB_IN -p tcp -s $ip_address --dport $mysql_port -j ACCEPT


##some of these may be unnecessary/redundant depending on your sysctl
##settings:

##null packets
#$iptables -I INPUT -p tcp --tcp-flags ALL NONE -j DROP

##SYN flood
#$iptables -I INPUT -p tcp ! --syn -m state --state NEW -j DROP

##XMAS packets
#$iptables -I INPUT -p tcp --tcp-flags ALL ALL -j DROP
#$iptables -I INPUT -p tcp --tcp-flags ALL FIN,PSH,URG -j DROP

##fragments
#$iptables -I INPUT -f -j DROP

###############################################

If you open ports using this method, be sure to leave them closed on the firewall configuration page in the ISPConfig web interface.

Always verify your configuration (iptables -L -n -V) after resetting Bastille.
Reply With Quote
The Following User Says Thank You to skycity For This Useful Post:
robertoshulze2257 (17th October 2014)
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
High Availability (Load Balancing) behind a firewall geek.de.nz Server Operation 7 4th January 2011 14:58
Firewall ACLs punto Tips/Tricks/Mods 37 10th June 2008 00:33
configuring IPTABLES firewall adityavpratap HOWTO-Related Questions 9 27th May 2006 22:42
Firewall script ColdDoT Server Operation 1 9th May 2006 00:50
I need a suitable firewall. agul Server Operation 4 23rd November 2005 01:12


All times are GMT +2. The time now is 15:45.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.