Re: [gentoo-user] What if the firewall doesn't start?

2007-02-27 Thread Alan McKinnon
On Tuesday 27 February 2007, Grant wrote: Anyway, a closed port remains closed whether a firewall is running, or not. I thought the firewall specified which ports to open/close. Not quite, but we might be running into terminology here. The app that is listening a port opens

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-27 Thread Grant
Anyway, a closed port remains closed whether a firewall is running, or not. I thought the firewall specified which ports to open/close. Not quite, but we might be running into terminology here. The app that is listening a port opens the port. This has nothing to do with

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-27 Thread Grant
Anyway, a closed port remains closed whether a firewall is running, or not. I thought the firewall specified which ports to open/close. Not quite, but we might be running into terminology here. The app that is listening a port opens the port. This has nothing to do with

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-27 Thread Dan Farrell
On Tue, 27 Feb 2007 09:11:33 -0800 Grant [EMAIL PROTECTED] wrote: Anyway, a closed port remains closed whether a firewall is running, or not. I thought the firewall specified which ports to open/close. Not quite, but we might be running into terminology here.

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-26 Thread Mick
On Monday 26 February 2007 00:28, Grant wrote: It occurred to me that if the shorewall firewall on my headless router doesn't start for whatever reason, I'll be totally exposed. Is there a way to protect against that? Well, you'll get an error during boot that iptables did not come

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-26 Thread Grant
Anyway, a closed port remains closed whether a firewall is running, or not. I thought the firewall specified which ports to open/close. Not quite, but we might be running into terminology here. The app that is listening a port opens the port. This has nothing to do with the firewall. The

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-26 Thread Mick
On Tuesday 27 February 2007 03:21, Grant wrote: Anyway, a closed port remains closed whether a firewall is running, or not. I thought the firewall specified which ports to open/close. Not quite, but we might be running into terminology here. The app that is listening a port

[gentoo-user] What if the firewall doesn't start?

2007-02-25 Thread Grant
It occurred to me that if the shorewall firewall on my headless router doesn't start for whatever reason, I'll be totally exposed. Is there a way to protect against that? - Grant -- gentoo-user@gentoo.org mailing list

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-25 Thread Mick
On Sunday 25 February 2007 19:58, Grant wrote: It occurred to me that if the shorewall firewall on my headless router doesn't start for whatever reason, I'll be totally exposed. Is there a way to protect against that? Well, you'll get an error during boot that iptables did not come up. I

Re: [gentoo-user] What if the firewall doesn't start?

2007-02-25 Thread Grant
It occurred to me that if the shorewall firewall on my headless router doesn't start for whatever reason, I'll be totally exposed. Is there a way to protect against that? Well, you'll get an error during boot that iptables did not come up. The machine is headless though. I assume that