Hi. I've made a mistake. And I guessed a wrong conclusion.
I was running 'shorewall compile' from the directory I wanted to include
and not from /etc/shorewall. I thought that shorewall used config directory
as a base for complete relative paths but uses current directory instead.
Thank you.
El may 6, 2014 8:42 PM, <[email protected]>
escribió:
>
> Send Shorewall-users mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Shorewall-users digest..."
>
> Today's Topics:
>
> 1. Re: ERROR: Startup is disabled (Mike Andrewjeski)
> 2. INCLUDE directive on Rules file (Emiliano Marino)
> 3. Re: INCLUDE directive on Rules file (Tom Eastep)
> 4. Re: ERROR: Startup is disabled (Tom Eastep)
> 5. Re: ERROR: Startup is disabled (Tom Eastep)
> 6. Re: ERROR: Startup is disabled (Tom Eastep)
>
>
> ---------- Mensaje reenviado ----------
> From: Mike Andrewjeski <[email protected]>
> To: Shorewall Users <[email protected]>
> Cc:
> Date: Tue, 06 May 2014 07:51:24 -0700
> Subject: Re: [Shorewall-users] ERROR: Startup is disabled
> 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?
>>
>> Regards,
>>
>> -Roberto
>
>
> Unfortunately it doesn't. That was what prompted me to copy the zones
file from /var/lib/shorewall
>
> -mike
>>
>>
>>
>>
>>
------------------------------------------------------------------------------
>> 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
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>
>
>
>
> ________________________________
>
> This email is free from viruses and malware because avast! Antivirus
protection is active.
>
>
>
>
> ---------- Mensaje reenviado ----------
> From: Emiliano Marino <[email protected]>
> To: [email protected]
> Cc:
> Date: Tue, 6 May 2014 17:43:00 -0300
> Subject: [Shorewall-users] INCLUDE directive on Rules file
> Hi! I'm becoming a fan of shorewall. I'm using it for some things and i'm
love the easy way it has to configure everything.
> At work we use CISCO ASA Firewall and the more I learn of the
capabilities of Linux firewall (and routing, brigding, vpn, vlan etc) more
I don't want to use cisco :D
>
> Ok, here is the issue:
>
> I'm starting a firewall setup in where I'm defining some rules in
separated files that are included using the INCLUDE directive.
>
> It works fine, but when you make a mistake in some of the included files,
the compiler hides you the problem saying:
>
> Compiling /etc/shorewall/rules...
> ERROR: INCLUDE file rules.d/out not found /etc/shorewall/rules
(line 19)
>
> Is false that the compiler can't find the file. If you copy the contents
of the included file inside "rules", and remove the INCLUDE directive for
that file; the compiler reveals the true error.
>
> When you fix your mistake it compiles ok (using the INCLUDE directive)
>
> I think this could be a low level bug. Or i'm making things wrong. If
it's a bug, How can I report it?
>
> Thanks
>
>
>
>
> ---------- Mensaje reenviado ----------
> From: Tom Eastep <[email protected]>
> To: [email protected]
> Cc:
> Date: Tue, 06 May 2014 14:22:26 -0700
> Subject: Re: [Shorewall-users] INCLUDE directive on Rules file
> On 5/6/2014 1:43 PM, Emiliano Marino wrote:
> > Hi! I'm becoming a fan of shorewall. I'm using it for some things and
> > i'm love the easy way it has to configure everything.
> > At work we use CISCO ASA Firewall and the more I learn of the
> > capabilities of Linux firewall (and routing, brigding, vpn, vlan etc)
> > more I don't want to use cisco :D
> >
> > Ok, here is the issue:
> >
> > I'm starting a firewall setup in where I'm defining some rules in
> > separated files that are included using the INCLUDE directive.
> >
> > It works fine, but when you make a mistake in some of the included
> > files, the compiler hides you the problem saying:
> >
> > Compiling /etc/shorewall/rules...
> > ERROR: INCLUDE file rules.d/out not found /etc/shorewall/rules
> > (line 19)
> >
> > Is false that the compiler can't find the file. If you copy the contents
> > of the included file inside "rules", and remove the INCLUDE directive
> > for that file; the compiler reveals the true error.
> >
> > When you fix your mistake it compiles ok (using the INCLUDE directive)
> >
> > I think this could be a low level bug. Or i'm making things wrong. If
> > it's a bug, How can I report it?
>
> Please post a simple example that demonstrates the problem.
>
> Thanks,
> -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 \________________________________________________
>
>
>
> ---------- Mensaje reenviado ----------
> From: Tom Eastep <[email protected]>
> To: Shorewall Users <[email protected]>
> Cc:
> Date: Tue, 06 May 2014 14:24:09 -0700
> Subject: Re: [Shorewall-users] ERROR: Startup is disabled
> 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?
> >>
> >> Regards,
> >>
> >> -Roberto
> >
> > Unfortunately it doesn't. That was what prompted me to copy the zones
> > file from /var/lib/shorewall
> >
>
> Please:
>
> shorewall trace check > trace 2>&1
>
> and send Roberto and me the 'trace' file.
>
> Thanks,
> -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 \________________________________________________
>
>
>
> ---------- Mensaje reenviado ----------
> From: Tom Eastep <[email protected]>
> To: [email protected]
> Cc:
> Date: Tue, 06 May 2014 16:08:59 -0700
> Subject: Re: [Shorewall-users] ERROR: Startup is disabled
> 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.
>
> -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 \________________________________________________
>
>
>
> ---------- Mensaje reenviado ----------
> From: Tom Eastep <[email protected]>
> To: [email protected]
> Cc:
> Date: Tue, 06 May 2014 16:42:32 -0700
> Subject: Re: [Shorewall-users] ERROR: Startup is disabled
> 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
>
> And send us the trace1 file. That will allow us to see why you are
> getting the 'Startup is disabled' error.
>
> Thanks,
> -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 \________________________________________________
>
>
>
------------------------------------------------------------------------------
> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/shorewall-users
>
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users
