Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Iptables rules comparation |
|---|---|
| Date: | Tue, 26 Oct 2004 09:40:14 -0400 |
Hi! Thnks for your answser!
you could run both rule sets, then redirect the details to files, then diff them... # fw1.sh # iptables -L -n -v > fw1.txt # fw2.sh # iptables -L -n -v > fw2.txt # diff fw1.txt fw2.txt Just make sure you flush the rules at the beginning of your scripts.
But, what if I have rulesets like this one? (just a sample) # script 1 *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] ... -A INPUT -i eth0 -p tcp -m tcp --dport 80 --syn -j ACCEPT ... COMMIT # script 2 *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT DROP [0:0] :IN_CHAIN - [0:0] ... -A INPUT -i eth0 -j IN_CHAIN -A IN_CHAIN -p tcp -m tcp --dport 80 --syn -j ACCEPT ... COMMIT When I run diff, the port 80 related lines are printed twice. :( ByE! Barreras
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: PIX Load balancing?, Jerome Tytgat |
|---|---|
| Next by Date: | RE: Unique POLICY NAT requirement, steve ruben |
| Previous by Thread: | Re: Iptables rules comparation, Phil Dyer |
| Next by Thread: | Re: Iptables rules comparation, Phil Dyer |
| Indexes: | [Date] [Thread] [Top] [All Lists] |