Hi, I need help with my firewall settings, and I prospected using the script option.





#!/bin/bash
#
# This script is executed whenever your appliance boots. Here you can add
# commands to be executed before the system enters the first runlevel. This
# could include loading kernel modules, starting daemons that aren't managed
# by init files, asking questions at the console, etc.
#
# The 'kiwi_type' variable will contain the format of the appliance (oem =
# disk image, vmx = VMware, iso = CD/DVD, xen = Xen).
#

# read in some variables
. /studio/profile

if [ -f /etc/init.d/suse_studio_firstboot ]
then

echo "Running SUSE Studio first boot script..."
iptables -I INPUT -p tcp --dport 113 -j DROP
iptables -I INPUT -p icmp -j DROP
fi





As you can see I need to use the terminal commands of "iptables -I INPUT -p tcp --dport 113 -j DROP" and "iptables -I INPUT -p icmp -j DROP." Is there anything wrong with my script or should I even be using script in the first place?

I'm by no means a SUSE studio expert, but

That's a bit difficult to read: using code tags helps

is rather easier.

I never really like using -I for iptables; it would only take a change to what went on previously for the end result to be rather different. However, having said that, have you tried listing your iptables ruleset to check that the end result is what you expected? Presumably, you did check that /etc/init.d/suse_studio_firstboot exists?

Terminal commands? bash commands, really (there are shells other than bash). I can't see what other options there are other than a script, but maybe there is some other way of setting stuff up in Studio - there is in plain openSUSE (Yast), but I'm not sure about Studio.

By the way, in earlier versions of Suse, 'going behind Yast's back' was a recipe for confusion, as Yast had a habit of thinking that it knew best, and overwriting your changes. Oh, and Suse starts up its firewall in two stages, and if you make your changes while 'early' (whatever the first part is called) is in place, they'll get overwritten when 'final' is put in place.

I guess I might just try something else then. Anyways, thanks for making a contribution.

Nice, I got the predicament fixed. I could not have done it without you Salasi.

Good news! Please mark the thread as solved.

You might also want to add a quick note on what the problem actually was, to help others who come across the thread from, eg, a network search.