>> 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? >> > > > How did you install shorewall-init? > Compiled from sources to build rpm (using rpmbuild) and then made/installed as a Live image, which is then copied to the target machine (plenty of RAM, very limited amount of "disk" space). The target system has 9 interfaces. I see that the rpm you are distributing (shorewall-init-4.5.14-0base.noarch.rpm) doesn't have these files either.
> /sbin/ifup-local is invoked by /etc/sysconf/network-scripts/ifup-post. > /sbin/ifdown-local is invoked by /etc/sysconf/network-scripts/ifdown-post. > Yep, grep agrees, thanks! >> 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? >> > > A successful start or restart will populate that file (as will compile). > In this case, I am assuming that "shorewall" (the service) needs to start prior to "shorewall-lite". I do remember having to alter the "shorewall-init" start up script to execute "shorewall compile" first (and I vaguely remember that you added a few alterations to shorewall(-init), as per my request, to accommodate this) as there was a chicken-and-egg scenario developing. > Not at all; I can copy/paste the text into the editor. > No problem for me then, thanks. ------------------------------------------------------------------------------ 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
