On Sat, 26 Dec 2009 10:43:03 -0600 Brad <[email protected]> wrote:
> > So my question is, what's the best way around this? Right now, I have > to manually stop the clients for long enough that their connection > tracking entries go away, then restart them. Should I start shorewall > twice: once when lo comes up then restart it when my other interfaces > have been configured? Has anyone else had to solve this? > The easiest solution is to install the conntrack utility program and arrange for /etc/init.d/shorewall to use the "-p" option to the start command. The other choice is to rearrange the order of startup so that Shorewall starts after networking. That usually requires so modification to the Shorewall configuration. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
