rc.firewall to iptables

ic_torres · 03-11-2006, 05:21 PM

i would just like to ask, i have a new rc.firewall, i want it to be applied to iptables, how will i do it?

win32sux · 03-11-2006, 08:07 PM

Quote:

Originally Posted by ic_torres

i would just like to ask, i have a new rc.firewall, i want it to be applied to iptables, how will i do it?

basically, just execute the file...

/bin/bash · 03-12-2006, 01:32 AM

Put rc.firewall in /etc/rc.d directory and make it executable then it will start every time you boot up.

ic_torres · 03-12-2006, 02:14 AM

sir how will i make it executable? do i just need to copy it at rc.d ?

win32sux · 03-12-2006, 02:25 AM

to copy the script into /etc/rc.d:

Code:

cp rc.firewall /etc/rc.d/

to set the permissions (make it executable by root, etc):

Code:

chown root:root /etc/rc.d/rc.firewall

chmod 750 /etc/rc.d/rc.firewall

to give regular users permission to see the contents of the file, use a 754 instead:

Code:

chmod 754 /etc/rc.d/rc.firewall

either way, to execute it you could do a:

Code:

/etc/rc.d/rc.firewall

or also a:

Code:

cd /etc/rc.d/

./rc.firewall

but as has been said, slackware is pre-configured to automatically execute any file called /etc/rc.d/rc.firewall at startup...

just my

...

ic_torres · 03-12-2006, 07:15 PM

sir isnt that chmod +x etc/rc.d/rc.firewall can be used?

thanks for the help..

win32sux · 03-12-2006, 07:33 PM

Quote:

Originally Posted by ic_torres

sir isnt that chmod +x etc/rc.d/rc.firewall can be used?

that would make the file executable by any user, which isn't really kosher... yes, i know the iptables/sysctl (assuming that's all you have in there) commands within the script won't work for non-roots, but still - the file is meant to be executed by root - so that's what you should set... to specify that you only want to set executable permission for root (the user that owns the file) do it like:

Code:

chown root:root /etc/rc.d/rc.firewall

chmod u+x /etc/rc.d/rc.firewall

but by using something like (for example):

Code:

chmod 744 /etc/rc.d/rc.firewall

you make sure everything else is fine too (non-root users can only read the file)... either way, you can always check your permissions with a:

Code:

ls -l /etc/rc.d/rc.firewall

Bruce Hill · 03-12-2006, 11:33 PM

I don't know where you got your rc.firewall script,
but the most popular one on the internet will NOT
work with Slackware until you make a modification.
Make sure you have the correct path to iptables
(/usr/sbin/iptables) or it won't run at all.

rayan · 03-13-2006, 02:38 AM

hi every body

im rayan and this is my first time to joint to this forum,my question is wich disto is best for blocking open port? thanks and good bless

win32sux · 03-13-2006, 03:08 AM

Quote:

Originally Posted by rayan

hi every body

im rayan and this is my first time to joint to this forum,my question is wich disto is best for blocking open port? thanks and good bless

welcome to LQ...

port blocking is not a distro thing... it's a firewall thing, and all distros come with the same firewall system - netfilter...

please don't jump into ongoing threads to ask your questions unless they are completely related to the thread's original post (this is definitely not a "which distro" thread)... you should open your own thread instead... a good place to open your thread would be here...

good luck!!

ic_torres · 03-13-2006, 05:58 AM

Quote:

Originally Posted by Chinaman

I don't know where you got your rc.firewall script,
but the most popular one on the internet will NOT
work with Slackware until you make a modification.
Make sure you have the correct path to iptables
(/usr/sbin/iptables) or it won't run at all.

so meaning i have to STILL LINK rc.firewall to iptables before it can function? ?

win32sux · 03-13-2006, 06:09 AM

Quote:

Originally Posted by ic_torres

so meaning i have to STILL LINK rc.firewall to iptables before it can function? ?

no... it means you open your iptables script (rc.firewall) with a text editor and change anything that says "/sbin/iptables" to "/usr/sbin/iptables"... the reason the "/usr" isn't usually put is because most scripts assume the person using them will be runnig a redhat based distro or something like that... for example, if you spot something like this:

Code:

IPT="/sbin/iptables"

you'd wanna change it to

Code:

IPT="/usr/sbin/iptables"

why don't you just post your script??

ic_torres · 03-13-2006, 05:26 PM

ok..il be updating you soon.. i have just reinstalled my slack the other day, coz before, rc.firewall is linked to my iptables.. but now, i was told that rc.firewall could just be copied and executed (so i also posted a thread in this forum to verify) il be posting my rc.firewall asap.. thanks