Results 1 to 1 of 1
I don't understand why the firewall would be starting at boot time if all the S##Firewall links are removed from the /etc/rc.d/rc5.d directory. Is there some other process that would ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 11-28-2006 #1
Why don't firewall boot configuations work?
I'm running VectorLinux 5.8 (based on Slackware). Using the system config tool (VASM) to disable the firewall at boot time, that's what it does; it removes the links in the rc2-5.d directories. So it technically shouldn't be starting right?
Also, I've configured it to open http and a few other ports. At least that's what VASM and the /etc/sysconfig/firewall and /etc/rc.d/rc.firewall scripts show. But at boot, when the firewall starts (like it's not supposed to), http (port 80) is apparently closed. And I'm not sure how to open it, because the config says it's open.
Thanks for your thoughts.HP Pavilion dv6000t
Intel Centrino Duo 2.0GHz
nVidia GeForce Go 7400
The real question is what time is it and why the hell am I still screwing around with my computer?