I have used Alien Bobs script generator to finally get the firewall on my laptop going. I KMyFirewall wouldn't work at all, it threw out all kinds of errors. GuardDog wouldn't let me get on the internet at all, a little too well guarded for my tastes. Anyhow, I used the script here and I am now up and running. My question is, since I am using a laptop I switch between a wired connection (eth0) and a wireless (wlan0), how do I put them both in the script? When I ran the generator I used eth0 in the Internet Interface field just to get it going. Can I even use the generator for more than one interface or do I have to edit the resulting script manually?

Thanks in advance,
Eric

I could be wrong about this BUT, i am almost positive that any iptables you add are permanent. Not sure how the script inputs them but they should always stay there, even if you run the script once. So you could create another script to just add wlan0 to those rules aswell. might just be easy enough to replace eth0 with wlan0

You will most likely need to edit the script if you plan on using two different interfaces. But, if you plan on using the same rules for both interfaces you could remove the interface specification all together. This would then apply the rule to any interface I think.

Good idea, sparker, about interface.

Quick idea here only and my knowledge on iptables script is rather limited to say the least.

So do not use this until/unless you have already tried ways recommended by others.

If you do not get it working without both interface names in there:

(a possibility?): make another iptables script for your wlan0 interface.

Have the two (the eth0 and the wlan0) generated scripts saved as filename1 and filename2 on your hard drive.

Then diff those two (man diff; diff in bash; is it "kdiff" in KDE which is graphical)

copy/paste (combine) the two files based on the differences so that the result includes both what's common between the two and what's different (non repeat the common but include the common stuff once) *and* add in the difference from one file, add it to the other file.

But if one interface is not always active, at such time it is not active then (if you do my idea) errors might show during bootup when the firewall is activated (or thereabouts, I might have it slightly out of order since firewall likely is first then activate interface for use).
--
Alan.

Thank you all, I haven't been home long enough in the last few days to give the wireless a try. Hopefully today I'll get a little while to play.

OK I have tried the following and so far no wireless:

Comment out INET_IFACE="eth0" with the theory that it will apply to all connections -> no such luck.

Uncomment INET_IFACE="eth0" and add INET_IFACE="wlan0" -> also no luck

Comment out INET_IFACE="eth0" but leave INET_IFACE="wlan0" -> I though for sure that this would disable the wired connection and enable wireless. No wireless, didn't test wired.

I'm going to do some serious reading on IPTables today and see if I can find an answer.

I did a quick scan through the script. Commenting out INET_IFACE="eth0" will only serve to leave a bunch of "-i" parameters without an argument which will give you an error.

Find the commands with "-i INET_IFACE" and remove that portion from the command and it should apply to all interfaces.

But, if it didn't work on the wireless interface by adding INET_IFACE="wlan0", my guess is that it probably won't solve your problem.

Also once edit rc.firewall

After edit, you need to then get the actual (live) firewall itself re-implemented

To do so, as root

root # /etc/rc.d/rc.firewall stop

then

root # /etc/rc.d/rc.firewall start

or there may be option of restart that would do the job all in one step instead of using/doing two steps via the use of stop and then start

--
Alan.

I restarted the computer to be sure the script was run after each time I changed it. I think tonight I am going to try turning off the firewall completely and see what happens. I just want to be sure I am actually attacking the problem or is there something else causing the trouble. There is a section of the script that removes the firewall completely each time it is run, I'm going to copy out that section and put it into it's own script to hopefully return the computer to normal. From there I'll put stuff back and see where it breaks.