Re: Shorewall 4.5.2.2 startup question

2012-04-30 Thread Charles Kroeger
> That you can provide such detail and yet not use the tool yourself. > > Hugo > >> Do you run shorewall? > > > > Not at all. Hugo, despite being complex in appearance shorewall is 'easy' to set up for a strong firewall with example files provided with the installation. The installation can

Re: Shorewall 4.5.2.2 startup question

2012-04-30 Thread Camaleón
On Mon, 30 Apr 2012 11:13:10 -0500, hvw59601 wrote: > Camaleón wrote: Mmm, this is done from "/etc/default/shorewall" by editing the "startup" variable, that you have to set to "1" as it says. >>> Impresive. >> >> What's what you find "impressive"? >> >> > That you can prov

Re: Shorewall 4.5.2.2 startup question

2012-04-30 Thread Camaleón
On Mon, 30 Apr 2012 11:43:53 +0300, Andrei POPESCU wrote: > On Du, 29 apr 12, 18:53:11, Charles Kroeger wrote: >> >> In /doc/shorewall-core there's nothing about this In >> /doc/shorewall-doc/ there are subfolders of HTML and HTML/images and >> manpages in great abundance but no README. In /usr/s

Re: Shorewall 4.5.2.2 startup question

2012-04-30 Thread hvw59601
Camaleón wrote: On Sun, 29 Apr 2012 15:13:36 -0500, hvw59601 wrote: Camaleón wrote: On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: After the recent Shorewall upgrade that replaced the previous configuration files, Shorewall now only starts 'manually' at the command line: e.g. #sh

Re: Shorewall 4.5.2.2 startup question

2012-04-30 Thread Camaleón
On Sun, 29 Apr 2012 15:13:36 -0500, hvw59601 wrote: > Camaleón wrote: >> On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: >> >>> After the recent Shorewall upgrade that replaced the previous >>> configuration files, Shorewall now only starts 'manually' at the >>> command line: e.g. #sho

Re: Shorewall 4.5.2.2 startup question

2012-04-30 Thread Andrei POPESCU
On Du, 29 apr 12, 18:53:11, Charles Kroeger wrote: > > In /doc/shorewall-core there's nothing about this > In /doc/shorewall-doc/ there are subfolders of HTML and HTML/images and > manpages in great abundance but no README. > In /usr/share/shorewall there are subfolders of Shorewall and config fil

Re: Shorewall 4.5.2.2 startup question

2012-04-29 Thread Charles Kroeger
Brian pointed out: > Incidentally, shorewall has had 'startup=0' since Lenny at least. You > probably forgot that you must have altered the default sometime in the > past and didn't think the README in /usr/share/doc worth a glance. > Also, /etc/default/shorewall is a conffile so if indeed the upg

Re: Shorewall 4.5.2.2 startup question

2012-04-29 Thread Brian
On Sun 29 Apr 2012 at 15:30:28 -0500, Charles Kroeger wrote: > On Sun, 29 Apr 2012 22:20:02 +0200 > hvw59601 wrote: > > > Camaleón wrote: > > > On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: > > > > > >> After the recent Shorewall upgrade that replaced the previous > > >> configurat

Re: Shorewall 4.5.2.2 startup question

2012-04-29 Thread Charles Kroeger
On Sun, 29 Apr 2012 22:20:02 +0200 hvw59601 wrote: > Camaleón wrote: > > On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: > > > >> After the recent Shorewall upgrade that replaced the previous > >> configuration files, Shorewall now only starts 'manually' at the command > >> line: e.g.

Re: Shorewall 4.5.2.2 startup question

2012-04-29 Thread Charles Kroeger
On Sun, 29 Apr 2012 19:30:02 +0200 Camaleón wrote: > On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: > > > After the recent Shorewall upgrade that replaced the previous > > configuration files, Shorewall now only starts 'manually' at the command > > line: e.g. #shorewall start. > > >

Re: Shorewall 4.5.2.2 startup question

2012-04-29 Thread hvw59601
Camaleón wrote: On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: After the recent Shorewall upgrade that replaced the previous configuration files, Shorewall now only starts 'manually' at the command line: e.g. #shorewall start. I can't find where this problem can be corrected in the

Re: Shorewall 4.5.2.2 startup question

2012-04-29 Thread Camaleón
On Sun, 29 Apr 2012 11:48:58 -0500, Charles Kroeger wrote: > After the recent Shorewall upgrade that replaced the previous > configuration files, Shorewall now only starts 'manually' at the command > line: e.g. #shorewall start. > > I can't find where this problem can be corrected in the > etc/sh