Problem: I can’t write to the fwbuilder list directly, because I used another account to start there. Anyway, I’m using it successful with dd-wrt. Where is your advantage of sveasoft over dd-wrt? If you need instruction, please mail me directly, as I don’t follow all discussions in the list (to much spam today, and to much other work.) But definitely, fwbuilder + linksys works like a charm (at least with 2.0)


Best regards


Robert Kahl



Robert Kahl

Sales Department

EMI-tec GmbH

Motzener Str. 17

12277 Berlin

Tel:    +49 30 723 949 - 20

FAX: +49 30 723 949 - 19



From: Vadim Kurland _ []
Sent: Thursday, August 31, 2006 3:19 AM
To: Paul
Cc: Chris Martin; fwbuilder-discussion; Robert Kahl
Subject: Re: [Fwbuilder-discussion] Help! FirewallBuilderv2.0.12"Segmantation Fault" after upgrade to Sveasoft Talisman 1.2



On Aug 30, 2006, at 5:59 PM, Paul wrote:

Hello Vadm,

On 8/30/06, Vadim Kurland ✈ <> wrote:



actually, you can just change platform in the firewall settings from Sveasoft to Linux24. You do not have to recreate firewall object from scratch.

Tom had actually instructed me in that in a private conversation. Thank  you though.

One question that still remains, however.

When I *do* make the change to Linux24, I note that there a number of  'additional' options available in the Linxux24/26 dialog(s), as opposed to the presumed/default settings that have been made for the Sveasoft/Linksys settings.

Is there some guideline as to how to set all those options to ensure working correctly with the Sveasoft?


there is no written document on that, but I can answer specific questions. I am sure others, who run fwbuilder in this mode, can help too.


Again, the goal here is to get FWB to write its firewall to the Sveasoft R/W Partition rather than to the apparently problematic NVRAM var -- and properly set up the whole thing, of course, to boot properly from the R/W-saved firewall.


I really do not know much about this as I do not it myself.