RE: iptables/linux - filtered ports?

[Jay Christopherson]

>Actually, I believe this is the way this works, as I know if you run an nmap against my firewalls, you get stealth as the answer.    That's very strange as I get the exact opposite....   no iptables: Starting nmap V. 2.12 by Fyodor ([EMAIL PROTECTED], www.insecure.org/nmap/) Interesting ports on  (10.1.6.100): Port    State       Protocol  Service 22      open        tcp        ssh             25      open        tcp        smtp            80      open        tcp        http            111     open        tcp        sunrpc          515     open        tcp        printer           iptables w/ following rule: iptables -A INPUT -p tcp --dport 25 -j DROP   Starting nmap V. 2.12 by Fyodor ([EMAIL PROTECTED], www.insecure.org/nmap/) Interesting ports on  (10.1.6.100): Port    State       Protocol  Service 22      open        tcp        ssh             25      filtered    tcp        smtp            80      open        tcp        http            111     open        tcp        sunrpc          515     open        tcp        printer           Nmap run completed -- 1 IP address (1 host up) scanned in 1 second   iptables w/ following rule (REJECT): iptables -A INPUT -p tcp --dport 25 -j REJECT --reject-with tcp-reset   Starting nmap V. 2.12 by Fyodor ([EMAIL PROTECTED], www.insecure.org/nmap/) Interesting ports on  (10.1.6.100): Port    State       Protocol  Service 22      open        tcp        ssh             80      open        tcp        http            111     open        tcp        sunrpc          515     open        tcp        printer