Hi Patrick
> I did this, but that IP still can access my site. Here's my config. > Options Indexes FollowSymLinks > Order Deny,Allow > Deny from 75.126.21.163 [...]/etc/sysconfig/SuSEfirewall2 FW_CUSTOMRULES="/etc/sysconfig/scripts/SuSEfirewall2-custom" /etc/sysconfig/scripts/SuSEfirewall2-custom fw_custom_after_antispoofing() { # could also be named /"before_port_splitting()" # these rules will be loaded after the anti-spoofing and icmp # handling # but before any IP protocol or TCP/UDP port allow/protection rules # will be set. # You can use this hook to allow/deny certain IP protocols or # TCP/UDP # ports before the SuSEfirewall2 generated rules are hit. iptables -I INPUT 1 -s 75.126.21.163 -j DROP
I add this in Susefirewall-custom, but still not working. When I type iptables -L, there's no chains indicated this IP. But when I add manually from console by typing iptables -I INPUT 1 -s 75.126.21.163 -j DROP , it worked. Is this susefirewall-custom actually work ? Or I just add this rule somewhere in /etc/init.d/boot.local or /etc/init.d/custom.script so it start whenever I boot / want ? Will it break rules in susefirewall ? regards, -- Arie Reynaldi Zanahar reymanx at gmail.com http://www.reynaldi.or.id -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
