#!/bin/sh -e
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
/etc/rc.d/rc.Firewall start

Now... make the module and add it to your Porteus loadout.
(the location of the final module is moot... place it in "base" or "modules" if you prefer)

When you start Porteus your firewall will default to "block all".

I'm sure other defaults (and methods) are possible... but you have to start somewhere right?

More to come...

Last edited by n0ctilucient on 13 Mar 2018, 04:13, edited 19 times in total.

I do NOT have the "right" to tell anyone what they should do...
but I reserve the "right" to tell them what they should "consider".

!/bin/sh -e
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
/etc/rc.d/rc.Firewall start

This post was made with the above noted rc.local @ login.
On login the firewall was defaulted to "block all".

I will have to hunt down the faq site (so bear with me).
I'm multitasking today... usually I'm not this sloppy.

I will also try it with the shebang default (#).
Perhaps the firewall will still default to "block all".

More to follow...

Last edited by n0ctilucient on 07 Mar 2018, 02:42, edited 2 times in total.

I do NOT have the "right" to tell anyone what they should do...
but I reserve the "right" to tell them what they should "consider".

#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
chmod +x /etc/rc.d/rc.FireWall
/etc/rc.d/rc.FireWall start

When you start Porteus your firewall will default to "block all".

I doubt that the firewall will use the "block all" settings
without further adjustments in rc.FireWall > allowed ports
I think the firewall will use the default = normal setting

You can compare the "block all" and "normal" firewall settings
as root with iptables -L -v

FYI. once /etc/rc.d/rc.FireWall is made executable, it will start at boot without needing /etc/rc.d/rc.FireWall start in rc.local(or anywhere else)
whatever is executable in /etc/rc.d/ will be executed at boot.
when set with psc, a module containing /etc/rc.d/rc.FireWall(executable) is made (when not using /changes)