search for: echo_notdone

...rewall /etc/rc0.d/K89shorewall /etc/rc6.d/K89shorewall /etc/rcS.d/S40shorewall The only entry on the log file seems to be the default one :- cat /var/log/shorewall-init.log LOGFILE (/var/log/messages) does not exist! ( /var/log/messages does in fact exist ) The Boot messages indicate that "echo_notdone" is being called and displaying the "check log" error message. It seems that "wait_for_ppd" is failing for some reason? Also, I am not clear on where the Variable "$wait_interface" gets initiated. After running shorewall start it appears to be an empty string...

Hey! No, actually shorewall works very well and starts and so on... Thanks for this! Problem is that it won''t start on boot it seems. At least it doesn''t enable forwarding. However, if I do /etc/init.d/shorewall restart it enables forwarding and the rest... But not if I do /etc/init.d/shorewall start ;) Seems weird... System is Debian Sid, Shorewall is prepackaged by Debian...

...rewall /etc/rc0.d/K89shorewall /etc/rc6.d/K89shorewall /etc/rcS.d/S40shorewall The only entry on the log file seems to be the default one :- cat /var/log/shorewall-init.log LOGFILE (/var/log/messages) does not exist! ( /var/log/messages does in fact exist ) The Boot messages indicate that "echo_notdone" is being called and displaying the "check log" error message. It seems that "wait_for_ppd" is failing for some reason? Also, I am not clear on where the Variable "$wait_interface" gets initiated. After running shorewall start it appears to be an empty string :-...

Hi, I have 2 Debian testing boxes running a very similar setup (both running the latest aptosid kernel); on one of them, since the iptables/libxtables10 packages have been upgraded from 1.4.19.1-1 to 1.4.20-2, shorewall-init can''t start shorewall anymore and for this reason ifupdown also fails triggering firewall up. Shorewall can be successfully started later on, and ifupdown starts