Thread: [Firestarter-user] Using firestarter on Debian -- suggested improvements
Brought to you by:
majix
From: rob s. <flo...@gm...> - 2012-03-10 16:43:01
|
Hello, Debian version:- Linux roblaptop 3.2.0-1-amd64 #1 SMP Fri Feb 17 05:17:36 UTC 2012 x86_64 GNU/Linux Firestarter version 1.0.3 Installing firestarter via synaptic puts the shell script in the rcS.d path and is run prior to any network being available and subsequently killed by network-manager. It should be in rc2.d, etc. paths and start AFTER all other network services. My suggestion would be to run it in two stages. In rcS.d run a script that sets up the kernel variables and loads iptables, and then after networking has been established, start the gui. Also, it is the isc-dhcp-client packages that provide DHCP and consequently the documentation needs updating. Where can I find documentation about the scripts and configuration files held in /etc/firestarter??? I can see that some things are updateable via the preferences tab, but how do you use user-post and user-pre scripts?? The current version of iptables supports the ulog daemon. I suggest that you use this instead of flooding syslog. That way dropped packets are all in the one log. My logs were being flooded with firestarter dropped packages at the rate of one per minute, so I cobbled together my own rules for iptables, using the ulog daemon, and now firestarter just reports the odd packet with a condition not being trapped by "my" rules. This is NOT ideal. Is it O.K. if I modify your scripts to use the ulog daemon??? Regards, Rob |
From: Bret B. <bre...@gm...> - 2012-03-11 09:00:18
|
On 11/03/2012, rob stone <flo...@gm...> wrote: > Hello, > > Debian version:- > Linux roblaptop 3.2.0-1-amd64 #1 SMP Fri Feb 17 05:17:36 UTC 2012 x86_64 > GNU/Linux > > Firestarter version 1.0.3 > > Installing firestarter via synaptic puts the shell script in the rcS.d > path and is run prior to any network being available and subsequently > killed by network-manager. It should be in rc2.d, etc. paths and start > AFTER all other network services. > > My suggestion would be to run it in two stages. In rcS.d run a script > that sets up the kernel variables and loads iptables, and then after > networking has been established, start the gui. > > Also, it is the isc-dhcp-client packages that provide DHCP and > consequently the documentation needs updating. > > Where can I find documentation about the scripts and configuration files > held in /etc/firestarter??? I can see that some things are updateable > via the preferences tab, but how do you use user-post and user-pre > scripts?? > > The current version of iptables supports the ulog daemon. I suggest that > you use this instead of flooding syslog. That way dropped packets are > all in the one log. > > My logs were being flooded with firestarter dropped packages at the rate > of one per minute, so I cobbled together my own rules for iptables, > using the ulog daemon, and now firestarter just reports the odd packet > with a condition not being trapped by "my" rules. This is NOT ideal. Is > it O.K. if I modify your scripts to use the ulog daemon??? > > Regards, > Rob > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Firestarter-user mailing list > To unsubscribe, visit > https://lists.sourceforge.net/lists/listinfo/firestarter-user > Hello. In response to a query that I posted a while ago, it was posted on this list that Firestarter has been abandoned. Refusing to accept that, I sent messages to both the developer of Firestarter, and, to the Debian package maintainer for Firestarter, querying the status of Firestarter. I have not received even an acknowledgment from either of those people, so Firestarter appears to be" dead in the water" - abandoned by the people held to be responsible for the development and maintenance of it. So, your posting of suggestions for improvements of Firestarter, would appear to be as likely to have an effect, as dropping a bottle with a message asking for a rescue, down an abandoned well. It is unfortunate, and I regret posting this message, but I believe that it needs to be said. -- Bret Busby Armadale West Australia .............. "So once you do know what the question actually is, you'll know what the answer means." - Deep Thought, Chapter 28 of Book 1 of "The Hitchhiker's Guide to the Galaxy: A Trilogy In Four Parts", written by Douglas Adams, published by Pan Books, 1992 .................................................... |
From: Fuzzy T. <fuz...@gm...> - 2012-03-11 23:20:02
|
Gentlemen I been using firestarter for years on the gateway and been subscribed to this list since 2005 and kept an eye on the status of the project and always was interrested in it. It's a great little peice of software that was written and abandoned. Im not a programmer ,but im a linux user for 11 years . I still hope a programmer will have one day the time and interrest in picking this project back up. It cannot be a one man project. There is support , this list , bug reports , decisions on what direction to take Firestarter and a bunch of people on IRC that need help with a product like this. It is a worthy endeavour. That firewall kept me safe since 2005 and i haven't had a case of anyone behind my firewall ever being intruded upon , though i been inder several attacks from the outside. It is a robust protection . There is interrest in the product and an update to it would be welcomed. Question is .. will a programmer show interrest ? Is there a programmer in the house willing to help ? There's a bunch of willing people to back your efforts on this list. Sincerely Richard Hebert On 03/11/2012 05:00 AM, Bret Busby wrote: > On 11/03/2012, rob stone<flo...@gm...> wrote: >> Hello, >> >> Debian version:- >> Linux roblaptop 3.2.0-1-amd64 #1 SMP Fri Feb 17 05:17:36 UTC 2012 x86_64 >> GNU/Linux >> >> Firestarter version 1.0.3 >> >> Installing firestarter via synaptic puts the shell script in the rcS.d >> path and is run prior to any network being available and subsequently >> killed by network-manager. It should be in rc2.d, etc. paths and start >> AFTER all other network services. >> >> My suggestion would be to run it in two stages. In rcS.d run a script >> that sets up the kernel variables and loads iptables, and then after >> networking has been established, start the gui. >> >> Also, it is the isc-dhcp-client packages that provide DHCP and >> consequently the documentation needs updating. >> >> Where can I find documentation about the scripts and configuration files >> held in /etc/firestarter??? I can see that some things are updateable >> via the preferences tab, but how do you use user-post and user-pre >> scripts?? >> >> The current version of iptables supports the ulog daemon. I suggest that >> you use this instead of flooding syslog. That way dropped packets are >> all in the one log. >> >> My logs were being flooded with firestarter dropped packages at the rate >> of one per minute, so I cobbled together my own rules for iptables, >> using the ulog daemon, and now firestarter just reports the odd packet >> with a condition not being trapped by "my" rules. This is NOT ideal. Is >> it O.K. if I modify your scripts to use the ulog daemon??? >> >> Regards, >> Rob >> >> >> ------------------------------------------------------------------------------ >> Virtualization& Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> _______________________________________________ >> Firestarter-user mailing list >> To unsubscribe, visit >> https://lists.sourceforge.net/lists/listinfo/firestarter-user >> > > Hello. > > In response to a query that I posted a while ago, it was posted on > this list that Firestarter has been abandoned. > > Refusing to accept that, I sent messages to both the developer of > Firestarter, and, to the Debian package maintainer for Firestarter, > querying the status of Firestarter. > > I have not received even an acknowledgment from either of those > people, so Firestarter appears to be" dead in the water" - abandoned > by the people held to be responsible for the development and > maintenance of it. > > So, your posting of suggestions for improvements of Firestarter, would > appear to be as likely to have an effect, as dropping a bottle with a > message asking for a rescue, down an abandoned well. > > It is unfortunate, and I regret posting this message, but I believe > that it needs to be said. > |
From: Spud <spu...@gm...> - 2012-03-12 04:09:58
|
A few years back a few people tried to do what your suggesting and it went nowhere, no one seemed interested. I do however hope you have more luck then they did. On 12 March 2012 09:09, Fuzzy TheBear <fuz...@gm...> wrote: > Gentlemen > > I been using firestarter for years on the gateway and been subscribed to > this list > since 2005 and kept an eye on the status of the project and always was > interrested in it. > It's a great little peice of software that was written and abandoned. > > Im not a programmer ,but im a linux user for 11 years . > > I still hope a programmer will have one day the time and interrest in > picking this project back up. > > It cannot be a one man project. > There is support , this list , bug reports , decisions on what direction > to take Firestarter and > a bunch of people on IRC that need help with a product like this. > > It is a worthy endeavour. That firewall kept me safe since 2005 and i > haven't had a case of > anyone behind my firewall ever being intruded upon , though i been inder > several attacks from the outside. > > It is a robust protection . There is interrest in the product and an > update to it would be welcomed. > Question is .. will a programmer show interrest ? > > Is there a programmer in the house willing to help ? > > There's a bunch of willing people to back your efforts on this list. > > > Sincerely > > Richard Hebert > > > > > On 03/11/2012 05:00 AM, Bret Busby wrote: > > On 11/03/2012, rob stone<flo...@gm...> wrote: > >> Hello, > >> > >> Debian version:- > >> Linux roblaptop 3.2.0-1-amd64 #1 SMP Fri Feb 17 05:17:36 UTC 2012 x86_64 > >> GNU/Linux > >> > >> Firestarter version 1.0.3 > >> > >> Installing firestarter via synaptic puts the shell script in the rcS.d > >> path and is run prior to any network being available and subsequently > >> killed by network-manager. It should be in rc2.d, etc. paths and start > >> AFTER all other network services. > >> > >> My suggestion would be to run it in two stages. In rcS.d run a script > >> that sets up the kernel variables and loads iptables, and then after > >> networking has been established, start the gui. > >> > >> Also, it is the isc-dhcp-client packages that provide DHCP and > >> consequently the documentation needs updating. > >> > >> Where can I find documentation about the scripts and configuration files > >> held in /etc/firestarter??? I can see that some things are updateable > >> via the preferences tab, but how do you use user-post and user-pre > >> scripts?? > >> > >> The current version of iptables supports the ulog daemon. I suggest that > >> you use this instead of flooding syslog. That way dropped packets are > >> all in the one log. > >> > >> My logs were being flooded with firestarter dropped packages at the rate > >> of one per minute, so I cobbled together my own rules for iptables, > >> using the ulog daemon, and now firestarter just reports the odd packet > >> with a condition not being trapped by "my" rules. This is NOT ideal. Is > >> it O.K. if I modify your scripts to use the ulog daemon??? > >> > >> Regards, > >> Rob > >> > >> > >> > ------------------------------------------------------------------------------ > >> Virtualization& Cloud Management Using Capacity Planning > >> Cloud computing makes use of virtualization - but cloud computing > >> also focuses on allowing computing to be delivered as a service. > >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ > >> _______________________________________________ > >> Firestarter-user mailing list > >> To unsubscribe, visit > >> https://lists.sourceforge.net/lists/listinfo/firestarter-user > >> > > > > Hello. > > > > In response to a query that I posted a while ago, it was posted on > > this list that Firestarter has been abandoned. > > > > Refusing to accept that, I sent messages to both the developer of > > Firestarter, and, to the Debian package maintainer for Firestarter, > > querying the status of Firestarter. > > > > I have not received even an acknowledgment from either of those > > people, so Firestarter appears to be" dead in the water" - abandoned > > by the people held to be responsible for the development and > > maintenance of it. > > > > So, your posting of suggestions for improvements of Firestarter, would > > appear to be as likely to have an effect, as dropping a bottle with a > > message asking for a rescue, down an abandoned well. > > > > It is unfortunate, and I regret posting this message, but I believe > > that it needs to be said. > > > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Firestarter-user mailing list > To unsubscribe, visit > https://lists.sourceforge.net/lists/listinfo/firestarter-user > -- db It denos't mtater waht oredr the ltteers in a wrod are, it's olny iprmoatnt taht the frist and lsat ltteer be at the rghit pclae.The rset can be a total mses and you can sitll raed it wouthit porbelm.Tihs is bcuseae the huamn mnid deos not raed ervey lteter by istlef, but the wrod as a wlohe. |