On 10/27/2010 07:23 PM, Rob Owens wrote:
I'm inclined to call it a bug in firestarter, but to be sure, test it
out with Network Manager instead of wicd. See if you have the same
problem. I think you will, which will indicate the problem is with
firestarter (or possibly with the way you
On Tue, Oct 26, 2010 at 02:02:04PM -0400, Gilbert Sullivan wrote:
On 10/23/2010 12:15 PM, Rob Owens wrote:
If your firewall script references an IP address (which you don't have
when the network is down), I think it needs the network to be up in
order to run.
If the script only references
On 10/23/2010 12:15 PM, Rob Owens wrote:
If your firewall script references an IP address (which you don't have
when the network is down), I think it needs the network to be up in
order to run.
If the script only references the interface (eth0, for
example) it might run even if the network is
On 10/23/2010 02:38 PM, Gilbert Sullivan wrote:
...
I'm guessing I should try to run firestarter in the Pre-connection
Script field first, and then fall back to using the Post-connection
Script field if Pre-connection fails.
Now I just have to decide which of the firestarter scripts it makes
On Sun, Oct 24, 2010 at 12:20:59PM -0400, Gilbert Sullivan wrote:
This is a pretty sophisticated firewall front end, allowing for
connection sharing and allowing you to limit service connections to
specific IP addresses or IP address ranges, but it's not working
reliably for me. And the
On 10/24/2010 07:45 PM, Rob Owens wrote:
On Sun, Oct 24, 2010 at 12:20:59PM -0400, Gilbert Sullivan wrote:
This is a pretty sophisticated firewall front end, allowing for
connection sharing and allowing you to limit service connections to
specific IP addresses or IP address ranges, but it's
On Friday 22 October 2010 18:13:54 Gilbert Sullivan wrote:
On 10/22/2010 07:42 PM, Greg Madden wrote:
On Friday 22 October 2010 14:57:15 Gilbert Sullivan wrote:
On 10/22/2010 06:00 PM, Greg Madden wrote:
On Friday 22 October 2010 11:00:40 Gilbert Sullivan wrote:
Does this have something
On Fri, Oct 22, 2010 at 10:03:59PM -0400, Gilbert Sullivan wrote:
As root I ran
/etc/init.d/firestarter start
and I got
Starting the Firestarter firewall
I ran
iptables -L
and I could see that iptables is properly doing its thing. The rules
are in place!
So, for some reason,
On 10/23/2010 04:57 AM, Greg Madden wrote:
Runlevel 2 is the default runlevel.
Look for a link: '/etc/rc2.d/Sxxfirestarter - ../init.d/firestarter'
Hi, Greg.
Thanks to you and Rob I'm getting a bit of an education.
I found /etc/rc2.d/S19firestarter. It does not contain any apparent (to
On 10/23/2010 08:16 AM, Rob Owens wrote:
What if the network isn't up when firestarter is asked to start? Would
it start anyway? Would it fail to start and log an error? Or would it
fail silently?
I'm not sure of the answers to the above. Maybe you could try shutting
down your network
On Sat, Oct 23, 2010 at 11:53:33AM -0400, Gilbert Sullivan wrote:
Starting Network connection manager: wicd.
startpar: service(s) returned failure: firestarter ... failed!
Running scripts in rc2.d/ took xx seconds.
Ah, you're using wicd. For each network connection, click on the
scripts
On 10/23/2010 12:15 PM, Rob Owens wrote:
On Sat, Oct 23, 2010 at 11:53:33AM -0400, Gilbert Sullivan wrote:
Starting Network connection manager: wicd.
startpar: service(s) returned failure: firestarter ... failed!
Running scripts in rc2.d/ took xx seconds.
Ah, you're using wicd. For each
Post Script to Previous Message:
The failure of the Scripts button to bring up anything led me to
deliberately try entering the wrong password, and that got me a modal
dialog:
--8---
Failed to run
I'm running Firestarter 1.0.3 on Debian testing (both systems involved
in this message).
A number of months ago I was in a situation where I wanted to establish
an SSH connection from my notebook to a desktop system. Because the
network on which this desktop system resides is less well
On Fri, Oct 22, 2010 at 01:50:11PM -0400, Gilbert Sullivan wrote:
list's moderator hasn't got back to me. It appears that the rules I want
in iptables are not in effect at all until I actually bring up the
Firestarter user interface during a given session. Once I log off
(restart not
On 10/22/2010 01:56 PM, Rob Owens wrote:
On Fri, Oct 22, 2010 at 01:50:11PM -0400, Gilbert Sullivan wrote:
list's moderator hasn't got back to me. It appears that the rules I want
in iptables are not in effect at all until I actually bring up the
Firestarter user interface during a given
On Fri, Oct 22, 2010 at 03:00:40PM -0400, Gilbert Sullivan wrote:
On 10/22/2010 01:56 PM, Rob Owens wrote:
On Fri, Oct 22, 2010 at 01:50:11PM -0400, Gilbert Sullivan wrote:
list's moderator hasn't got back to me. It appears that the rules I want
in iptables are not in effect at all until I
On Friday 22 October 2010 11:00:40 Gilbert Sullivan wrote:
Does this have something to do with Firestarter being started (or not
started) at different run levels during startup? I briefly see something
about it scrolling by, but I never get a chance to read it.
You can use 'dmesg |grep
On 10/22/2010 04:29 PM, Rob Owens wrote:
On Fri, Oct 22, 2010 at 03:00:40PM -0400, Gilbert Sullivan wrote:
On 10/22/2010 01:56 PM, Rob Owens wrote:
On Fri, Oct 22, 2010 at 01:50:11PM -0400, Gilbert Sullivan wrote:
list's moderator hasn't got back to me. It appears that the rules I want
in
On 10/22/2010 06:00 PM, Greg Madden wrote:
On Friday 22 October 2010 11:00:40 Gilbert Sullivan wrote:
Does this have something to do with Firestarter being started (or not
started) at different run levels during startup? I briefly see something
about it scrolling by, but I never get a chance
On Friday 22 October 2010 14:57:15 Gilbert Sullivan wrote:
On 10/22/2010 06:00 PM, Greg Madden wrote:
On Friday 22 October 2010 11:00:40 Gilbert Sullivan wrote:
Does this have something to do with Firestarter being started (or not
started) at different run levels during startup? I briefly
On Fri, Oct 22, 2010 at 06:48:34PM -0400, Gilbert Sullivan wrote:
There is an /etc/init.d/firestarter file and an
/etc/firestarter/configuration file (that later one being present in its
directory with a whole bunch of other files.).
After a fresh reboot, with firestarter not running,
On 10/22/2010 08:18 PM, Rob Owens wrote:
On Fri, Oct 22, 2010 at 06:48:34PM -0400, Gilbert Sullivan wrote:
There is an /etc/init.d/firestarter file and an
/etc/firestarter/configuration file (that later one being present in its
directory with a whole bunch of other files.).
After a fresh
On 10/22/2010 07:42 PM, Greg Madden wrote:
On Friday 22 October 2010 14:57:15 Gilbert Sullivan wrote:
On 10/22/2010 06:00 PM, Greg Madden wrote:
On Friday 22 October 2010 11:00:40 Gilbert Sullivan wrote:
Does this have something to do with Firestarter being started (or not
started) at
24 matches
Mail list logo
