On 5/6/2014 4:42 PM, Tom Eastep wrote: > On 5/6/2014 4:08 PM, Tom Eastep wrote: >> On 5/6/2014 7:51 AM, Mike Andrewjeski wrote: >>> On 5/6/2014 7:34 AM, Roberto C. Sánchez wrote: >>>> On Tue, May 06, 2014 at 07:16:14AM -0700, Mike Andrewjeski wrote: >>>>> Oh, Sorry Tom, after running shorewall check, in desperation I >>>>> copied >>>>> the /var/lib/shorewall/zones to /etc/shorewall/zones to see if it would >>>>> help. I have a back up of the original /etc/shorewall/zones file. >>>>> >>>>> It looks like this: >>>>> #zone display comment >>>>> fw firewall >>>>> loc ipv4 >>>>> net ipv4 >>>>> >>>> If you replace the bogus zones file with the backup of the original >>>> zones file, then does it work? >>>> >> >> If I replace the bogus file with the one above and adjust CONFIG_PATH to >> omit /etc/shorewall, the configuration compiles fine for me. So I hope >> that the trace file will show us what is wrong. > > And also please: > > sh -x /sbin/shorewall start > trace1 2>1 >
Make that:
sh -x /sbin/shorewall start > trace1 2>&1
-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: OpenPGP digital signature
------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce
_______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
