You are not logged in.
Dear Forums users,
I've recently installed Arch along with Shorewall but I can't seem to get it to start on boot. According to the docs, shorewall isn't a daemon and should start itself after the first execution. Yet I can't seem to bring it up automatically. Anybody who can assist?
Regards,
Alex
Solution:
put the startup command in /etc/rc.local
Last edited by alexkarro (2012-01-03 17:15:10)
Offline
Adding the executable line to /etc/rc.local should do the trick.
"Cleverness is not wisdom." ~Euripides
Offline
Adding the executable line to /etc/rc.local should do the trick.
Thank you, that worked. Is it normal for it compile everytime it starts?
Offline
Compile from source? Most likely not. What line did you add to /etc/rc.local?
"Cleverness is not wisdom." ~Euripides
Offline
Compile from source? Most likely not. What line did you add to /etc/rc.local?
Not source (sorry I'm not very familiar with the proper terms). Most daemons that boot up usually just have 1 line appear (STARTING DAEMON X ) during boot while Shorewall pretty much has a huge list of stuff like reading /etc/shorewall/rules etc.
The startup line I use is
shorewall start
and the output is:
Compiling...
Processing /etc/shorewall/params ...
Processing /etc/shorewall/shorewall.conf...
Loading Modules...
Compiling /etc/shorewall/zones...
Compiling /etc/shorewall/interfaces...
Determining Hosts in Zones...
Locating Action Files...
Compiling /usr/share/shorewall/action.Drop for chain Drop...
Compiling /usr/share/shorewall/action.Broadcast for chain Broadcast...
Compiling /usr/share/shorewall/action.Invalid for chain Invalid...
Compiling /usr/share/shorewall/action.NotSyn for chain NotSyn...
Compiling /usr/share/shorewall/action.Reject for chain Reject...
Compiling /etc/shorewall/policy...
Compiling /etc/shorewall/notrack...
Running /etc/shorewall/initdone...
Adding rules for DHCP
Compiling Kernel Route Filtering...
Compiling Martian Logging...
Compiling MAC Filtration -- Phase 1...
Compiling /etc/shorewall/rules...
Compiling MAC Filtration -- Phase 2...
Applying Policies...
Generating Rule Matrix...
Creating iptables-restore input...
Shorewall configuration compiled to /var/lib/shorewall/.start
Starting Shorewall....
Initializing...
Processing /etc/shorewall/init ...
Processing /etc/shorewall/tcclear ...
Setting up Route Filtering...
Setting up Martian Logging...
Setting up Proxy ARP...
Setting up Traffic Control...
Preparing iptables-restore input...
Running /usr/sbin/iptables-restore...
IPv4 Forwarding Enabled
Processing /etc/shorewall/start ...
Processing /etc/shorewall/started ...
done.
Might as well mark this as solved.
Last edited by alexkarro (2012-01-03 17:14:07)
Offline
Yeah, it seems like shorewall is parsing configuration files or doing some sort of regular run-time compilation. You may be able to silence these messages by searching for a 'quiet' option in 'man shorewall' or 'shorewall --help'.
"Cleverness is not wisdom." ~Euripides
Offline
Yeah, it seems like shorewall is parsing configuration files or doing some sort of regular run-time compilation. You may be able to silence these messages by searching for a 'quiet' option in 'man shorewall' or 'shorewall --help'.
Sadly there doesn't seem to be a quiet option. The output isn't annoying or anything I was just wondering if that was regular behaviour for it.
EDIT:
Apparently there is an init script within Archlinux for shorewall. Simply add shorewall to the daemons array in /etc/rc.conf. This way you will have a clean boot screen and it will start just as normal
Last edited by alexkarro (2012-01-07 20:01:53)
Offline