> On Redhat/Fedora, Shorewall-init installs the ifupdown script as
> /sbin/ifup-local and /sbin/ifdown-local.
>
I don't have any of this. I do have /sbin/ifup and /sbin/ifdown, but
that, again, seems to be a standard-issue scripts. Still, how are these
2 scripts called? Is it by the OS when an interface goes up/down?
>> Could you elaborate on this a bit more please? I ran grep -r "ifupdown"
>> /etc, but could not find any meaningful matches. Does shorewall-init
>> auto-generate these up/down scripts depending on my shorewall
>> configuration or does it use them to insert a callback to
>> /usr/libexec/ifupdown? If not, is this done in some other way?
>>
>
> ifupdown runs ${VARDIR}/firewall passing it either an 'up' or 'down'
> command. e.g., /var/lib/shorewall/firewall up eth0. The firewall
> script's up/down processing is taylored to your configuration.
>
What I need to understand is how are the /sbin/*-local scripts called
(see above). I also assume that /var/lib/shorewall/firewall needs to be
compiled, so I presume that "shorewall compile" is called at some stage
to create this file, is that the case?
> That's fine. The Shorewall document sources are maintained in Docbook
> XML, but the free WYSIWYG editor that I use (XXE from XMLMind) is no
> longer available for download.
>
If I create it in a plain text format would that be a bit too much
hassle for you?
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
