Re: Extension Script or systemd for Shorewall dependencies?

Tom Eastep
Thu, 05 Dec 2013 14:46:46 -0000

On 12/4/2013 10:50 AM, jen142@promessage.com wrote:
>
>
>> You can simply use the ''shorewall reload <remote
system>'' on the admin
>> system, or you must export then ''systemctl restart''
on the remote
>> firewall.
>
> thanks

Note that, after export, you may also ''shorewall-lite restart''
on the
remote system.

>
>>> Can the remote executable be changed?  For example, to use
>>> /etc/systemd/system/my-shorewall-script.service, instead?
>>
>> Instead of what?
>
> instead of whatever the answer to my prior question:

You seem to be fixated on systemd. What exactly are you trying to
accomplish?

Please refer to http://www.shorewall.org/Install.htm#id1169649892315. It
describes all of the configuration options available for relocating
Shorewall files.

>
> '' ... is the remote''s Shorewall-lite instance
reloaded/restarted by
> using "systemctl restart ...",
> or by directly invoking the shorewall script? ...''
>
> is.
>
> a local ''shorewall reload'' executes WHAT on the remote
system?
> "systemctl shorewall-lite"?

No -- it executes "${SBINDIR}/shorewall-lite restart" where SBINDIR is
set in shorewallrc. See above.

Note That the ''shorewall-lite'' program uses shorewallrc to
determine
where the compiled script resides, but the name of the compiled script
is always assumed to be ''firewall''.