On Thu, 12 Sep 2013 03:24:40 -0400 Thomas Harold <[email protected]> wrote:
> One pitfall that I found is that "status=1" is set to zero by default > in the stock /etc/lsm/lsm.conf file. That's not true. Default of status is 2 eg unknown. > The Shorewall scripts in the MultiISP document depend on LSM assuming > that the link is "up" when LSM starts. Since the stock config is > "status=0", LSM is assuming that links are "down" when LSM starts. You should really let lsm to control shorewall - not shorewall to control lsm, that's how lsm is designed to work. That's pretty simple on redhat based systems where you do something like this: Note, I only use lsm for ipv4 here. /etc/sysconfig/lsm: #!/bin/sh # # LSM to Shorewall Multi-ISP integration script # # Copyright © 2009-2013 Tuomo Soini <[email protected]> # DAEMON_COREFILE_LIMIT=unlimited VARDIR=$(/sbin/shorewall show vardir) if [ $1 = start -o $1 = restart ]; then # # Set all interfaces to up state on startup. # We will fail soon enough. # rm -f ${VARDIR:-/var/lib/shorewall}/*.status # umask=$(umask) umask 077 >/dev/null /sbin/shorewall -q restart >> /var/log/lsm 2>&1 /sbin/shorewall show routing >> /var/log/lsm umask ${umask} >/dev/null fi That's how I run lsm with shorewall on rhel6 based system. On connection it's important to have: eventscript=/usr/share/lsm/shorewall_script -- Tuomo Soini <[email protected]> Foobar Linux services +358 40 5240030 Foobar Oy <http://foobar.fi/> ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
