Re: [Fwbuilder-discussion] Help! FirewallBuilderv2.0.12"Segmantation Fault" after upgrade to Sveasoft Talisman 1.2

[Chris M. <ch...@ma...>]

When you stared configuring your firewall in Fwbuilder you selected the
sveasoft template.

 

This is what causes the installer to place the script in NVRAM.

 

If you configure your firewall using a std linux 2.4 / iptables template you
will be able to install to the JFFS filesystem.

 

Don't delete the firewall you configured in Fwbuilder,  just create a second
firewall based on a linux template

 

 

I started out using talisman, but found it too restrictive, and I was not
able to do everything I wanted with it

I moved to openWrt, and haven't looked back,  but if you are NOT familiar
with linux I wouldn't recommend it

 

 

---------------------------------------------------------------------------

Chris Martin

m: 0419 812 371

e: ch...@ma...

---------------------------------------------------------------------------

  _____  

From: fwb...@li...
[mailto:fwb...@li...] On Behalf Of
Paul
Sent: Thursday, 31 August 2006 4:29 AM
To: fwbuilder-discussion
Cc: R....@em...
Subject: Re: [Fwbuilder-discussion] Help!
FirewallBuilderv2.0.12"Segmantation Fault" after upgrade to Sveasoft
Talisman 1.2

 

Hello Again.

While exploring your suggestions, I've learned that the FWB installer, when
targeted at an Sveasoft firmware-based router, correctly configs to place
the firewall in a nvram variable.

Per your point, above. 

I've discovered an option in FWB in the firewall's seeting -> Installer
dialog:

"Directory on the firewall where script should be installed"

which looked promising to place the firewall in the R/W partition (or JFFS,
I believe) on the 
router.

BUT, it is greyed-out/inactive.

Is this a FWB lmitation, feature or bug?  In other words, can I "Make it
work" using FWB?

Thanks.

Paul