Quote (ke4nt1 @ Dec. 05 2004,03:57) | ||
Oh, you MUST share. !!! Pray Tell !!! 73 ke4nt |
Quote |
######################################## # -- Advanced Configuration Options -- # ######################################## # ** DO NOT ** modify anything below unless you know what you are doing!! # See online documentation at: http://projectfiles.com/firewall/config.html DENY_OUTBOUND="" ALLOW_INBOUND="" BLACKLIST="" STATIC_INSIDE_OUTSIDE="" PORT_FORWARDS="" PORT_FWD_ALL="yes" PORT_FWD_ROUTED_NETWORKS="yes" ADDITIONAL_ROUTED_NETWORKS="" TRUST_ROUTED_NETWORKS="yes" SHARED_INTERNAL="yes" FIREWALL_IP="" TRUST_LOCAL_EXTERNAL_NETWORKS="no" DMZ_INTERFACES="" NAT_EXTERNAL="yes" ADDITIONAL_NAT_INTERFACES="" IGNORE_INTERFACES="" LOGGING="no" REQUIRE_EXTERNAL_CONFIG="no" |
Quote (Guest @ Dec. 05 2004,18:39) |
rcfirewall sounds great but does it work on a machine with only 1 nic? I am only interested in blocking access to the machine, not in creating a new, protected subnet and using DSL as a NAT firewall. Again, something akin to what the "Windows Firewall" does should be sufficient to block all inbound TCP, UDP, and ICMP packets. I see no real reason for egress filtering either in this scenario as trojans/rootkits would not persist between restarts and this is a workstation, not a bastion server. Chip |