Hello, I see the following when using 4.5.2 beta version. The config files are in the current directory. # shorewall check . /sbin/shorewall: 47: -: not found Checking... # shorewall start . /sbin/shorewall: 47: -: not found Compiling... Apart from that, normal compilation occurs OK. Thanks. ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
On Apr 9, 2012, at 2:03 PM, Fred Maillou <frederriffic@yahoo.ca> wrote:> Hello, > > I see the following when using 4.5.2 beta version. The config files are in the current directory. > > # shorewall check . > /sbin/shorewall: 47: -: not found > Checking... > > # shorewall start . > /sbin/shorewall: 47: -: not found > Compiling... > > Apart from that, normal compilation occurs OK. >Which version exactly? There have been five betas and two RCs. Tom ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2
>> I see the following when using 4.5.2 beta version. The config >> files are in the current directory.>> # shorewall check . >> /sbin/shorewall: 47: -: not found >> Checking...>> # shorewall start . >> /sbin/shorewall: 47: -: not found >> Compiling... >> Apart from that, normal compilation occurs OK.> Which version exactly? There have been five betas and two RCs.Sorry, that is version 4.5.2 beta4. There is also the following: [...] Generating Rule Matrix... Creating iptables-restore input... Shorewall configuration compiled to /var/lib/.start /var/lib/.start: 2460: -: not found /var/lib/.start: 2460: -: not found Starting Shorewall.... [...] And although the firewall is installed after a ''start .'' command, TC rules are not. Eg. ''tc -d -s class show dev eth4'' returns nothing. ''iptables -L'' returns a full configuration. The firewall is very basic: policy ACCEPT, all, all and no rules. One fw and one net zone, one interface. Here is the TC config. # cat tcdevices #INTERFACE IN-BANDWITH OUT-BANDWIDTH eth4 0 75mbit # cat tcclasses #INTERFACE MARK RATE CEIL PRIO OPTIONS eth4 1 full*5/10 full*9/10 1 eth4 2 full*1/10 full*7/10 1 default # cat tcrules #MARK SOURCE DEST PROTO DPORT SPORT USER TEST LENGTH TOS 1 172.30.159.102 0.0.0.0/0 all - - - - :455 - The doing a ''stop'' command yields: # shorewall stop /sbin/shorewall: 47: -: not found ERROR: Shorewall has never been started ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev
On 04/10/2012 05:11 AM, Fred Maillou wrote:>>> I see the following when using 4.5.2 beta version. The config >>> files are in the current directory. > >>> # shorewall check . >>> /sbin/shorewall: 47: -: not found >>> Checking... > >>> # shorewall start . >>> /sbin/shorewall: 47: -: not found >>> Compiling... >>> Apart from that, normal compilation occurs OK. > >> Which version exactly? There have been five betas and two RCs. > > Sorry, that is version 4.5.2 beta4. > > There is also the following: > > [...] > Generating Rule Matrix... > Creating iptables-restore input... > Shorewall configuration compiled to /var/lib/.start > /var/lib/.start: 2460: -: not found > /var/lib/.start: 2460: -: not found > Starting Shorewall.... > [...] > > And although the firewall is installed after a ''start .'' command, > TC rules are not. Eg. ''tc -d -s class show dev eth4'' returns > nothing. ''iptables -L'' returns a full configuration. > > The firewall is very basic: policy ACCEPT, all, all and no rules. > One fw and one net zone, one interface. > > Here is the TC config. > > # cat tcdevices > > #INTERFACE IN-BANDWITH OUT-BANDWIDTH > eth4 0 75mbit > > # cat tcclasses > > #INTERFACE MARK RATE CEIL PRIO OPTIONS > eth4 1 full*5/10 full*9/10 1 > eth4 2 full*1/10 full*7/10 1 default > > # cat tcrules > > #MARK SOURCE DEST PROTO DPORT SPORT USER TEST LENGTH TOS > 1 172.30.159.102 0.0.0.0/0 all - - - - :455 - > > The doing a ''stop'' command yields: > > # shorewall stop > /sbin/shorewall: 47: -: not found > ERROR: Shorewall has never been startedBeta 4 was pretty broken. These problems are not present in RC 2. -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 \________________________________________________ ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev
The ''- not found'' has to do with:
elif - -f ${SHOREAWLLRC_HOME}/.shorewallrc;
instead of:
elif [ -f ${SHOREAWLLRC_HOME}/.shorewallrc ];
The .start has also the same syntax.
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
> Beta 4 was pretty broken. These problems are not present in RC 2.OK! Thanks. ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev