Tom
At 18:31 10.04.2004, Tom Eastep wrote:
Tom Eastep wrote:
Stijn Jonker wrote:
It works fine here after a small modification in firewall on line 5757:
Loading /usr/share/shorewall/functions...
Processing /etc/shorewall/params ...
Processing /etc/shorewall/shorewall.conf...
Erich Titl wrote:
As I suggested some time ago could this be solved by falling back to the
default shorewall.conf file if the file pointed to by CONFIG_PATH did
not exist?
Let say that for LEAF, the CONFIG_PATH is:
/etc/shorewalluser:/etc/shorewall:/usr/share/shorewall
Shorewall continues
Tom Eastep wrote:
Erich Titl wrote:
As I suggested some time ago could this be solved by falling back to the
default shorewall.conf file if the file pointed to by CONFIG_PATH did
not exist?
Let say that for LEAF, the CONFIG_PATH is:
/etc/shorewalluser:/etc/shorewall:/usr/share/shorewall
Erich Titl wrote:
Does it have to be populated?
I think so if the /var/lib/lrpkg/shorwall.conf file points to it.
If Shorewall has a fallback set up which
would be overridden by user configuration data then Shorewall would have
a default configuration initially unless there is a user
Tom Eastep wrote:
Erich Titl wrote:
Does it have to be populated?
I think so if the /var/lib/lrpkg/shorwall.conf file points to it.
If Shorewall has a fallback set up which
would be overridden by user configuration data then Shorewall would have
a default configuration initially unless there
Charles Steinkuehler wrote:
I think that Charles's suggestion about using two packages makes this
a bit more friendly. The main problem that I see with that approach is
that it doesn't allow any way for me to add a new config file in the
future and have it reflected in the Shorewall
Am Dienstag, 13. April 2004 13:09 schrieb Charles Steinkuehler:
Mike Noyes has been in a bicycle accident (see message below).
If I get any more details, I'll let everyone know.
Thx for info Charles - bad news.
Best wishes to Mike - I hope he'll be back soon and healthy again.
kp
