From: "Christopher Davis" <cldavis@speakeasy.net>
To: netfilter@lists.netfilter.org
Subject: RE: Firewall Script Help
Date: Mon, 8 Mar 2004 14:19:14 -0500 [thread overview]
Message-ID: <JKELJHHMDHPOLKFBOEGHMECLFDAA.cldavis@speakeasy.net> (raw)
In-Reply-To: <200403081849.49587.lists@edeca.net>
David:
> -----Original Message-----
> From: netfilter-admin@lists.netfilter.org
> [mailto:netfilter-admin@lists.netfilter.org]On
> Behalf Of David Cannings
> Sent: Monday, March 08, 2004 1:50 PM
> To: netfilter@lists.netfilter.org
> Subject: Re: Firewall Script Help
>
> Just a quick point, it is (in my opinion at
> least) far easier to read your
> firewall rules if they're output from iptables
> itself. Following through
> the script is harder.
>
> # iptables -L -v
>
> David
Here it is! If it is easier to read, I can forward indivual
txt docs with the same information -- I didn't want to
attach anything being sent to the list.
Thanks again!
Christopher Davis
Chain INPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 DROP all -- any any anywhere
anywhere state INVALID
0 0 ACCEPT all -- any any anywhere
anywhere state RELATED,ESTABLISHED
0 0 ACCEPT all -- lo any anywhere
anywhere
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:FIN,ACK/FIN
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:PSH,ACK/PSH
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:ACK,URG/URG
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:FIN,RST/FIN,RST
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:FIN,SYN/FIN,SYN
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:SYN,RST/SYN,RST
0 0 DROP tcp -- any any anywhere
anywhere tcp
flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,PSH,ACK,URG
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:FIN,SYN,RST,PSH,ACK,URG/NONE
0 0 DROP tcp -- any any anywhere
anywhere tcp
flags:FIN,SYN,RST,PSH,ACK,URG/FIN,PSH,URG
0 0 DROP tcp -- any any anywhere
anywhere tcp
flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,PSH,URG
0 0 DROP tcp -- any any anywhere
anywhere tcp
flags:FIN,SYN,RST,PSH,ACK,URG/FIN,SYN,RST,ACK,URG
0 0 ACCEPT tcp -- any any anywhere
anywhere tcp dpt:www
0 0 ACCEPT tcp -- any any anywhere
anywhere tcp dpt:ssh
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:SYN/SYN
0 0 DROP tcp -- any any anywhere
anywhere tcp flags:SYN,RST,ACK/SYN
0 0 ACCEPT icmp -- any any anywhere
anywhere icmp destination-unreachable
0 0 ACCEPT icmp -- any any anywhere
anywhere icmp source-quench
0 0 ACCEPT icmp -- any any anywhere
anywhere icmp time-exceeded
0 0 ACCEPT icmp -- any any anywhere
anywhere icmp parameter-problem
Chain FORWARD (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
Chain OUTPUT (policy DROP 0 packets, 0 bytes)
pkts bytes target prot opt in out source
destination
0 0 ACCEPT tcp -- any any
www01.colligatedtechnologies.com anywhere tcp
spt:www
0 0 ACCEPT tcp -- any any
www01.colligatedtechnologies.com anywhere tcp
spt:ssh
1 66 ACCEPT all -- any any
www01.colligatedtechnologies.com anywhere
Chain BADIP (0 references)
pkts bytes target prot opt in out source
destination
0 0 LBADIP all -- any any 0.0.0.0/8
anywhere
0 0 LBADIP all -- any any anywhere
0.0.0.0/8
0 0 LBADIP all -- any any 10.0.0.0/8
anywhere
0 0 LBADIP all -- any any anywhere
10.0.0.0/8
0 0 LBADIP all -- any any 127.0.0.0/8
anywhere
0 0 LBADIP all -- any any anywhere
127.0.0.0/8
0 0 LBADIP all -- any any
169.254.0.0/16 anywhere
0 0 LBADIP all -- any any anywhere
169.254.0.0/16
0 0 LBADIP all -- any any 172.16.0.0/12
anywhere
0 0 LBADIP all -- any any anywhere
172.16.0.0/12
0 0 LBADIP all -- any any 192.0.0.0/24
anywhere
0 0 LBADIP all -- any any anywhere
192.0.0.0/24
0 0 LBADIP all -- any any
192.168.0.0/16 anywhere
0 0 LBADIP all -- any any anywhere
192.168.0.0/16
0 0 LBADIP all -- any any 192.0.34.0/24
anywhere
0 0 LBADIP all -- any any anywhere
192.0.34.0/24
0 0 LBADIP all -- any any
BASE-ADDRESS.MCAST.NET/4 anywhere
0 0 LBADIP all -- any any anywhere
BASE-ADDRESS.MCAST.NET/4
0 0 LBADIP all -- any any 240.0.0.0/5
anywhere
0 0 LBADIP all -- any any anywhere
240.0.0.0/5
0 0 LBADIP all -- any any
255.255.255.255 anywhere
0 0 LBADIP all -- any any anywhere
255.255.255.255
Chain LBADIP (22 references)
pkts bytes target prot opt in out source
destination
0 0 DROP tcp -- any any anywhere
anywhere tcp dpts:netbios-ns:netbios-ssn
0 0 DROP udp -- any any anywhere
anywhere udp dpts:netbios-ns:netbios-ssn
0 0 DROP all -- any any anywhere
anywhere
Chain LDROP (0 references)
pkts bytes target prot opt in out source
destination
0 0 DROP all -- any any anywhere
anywhere
Chain LSHUN (0 references)
pkts bytes target prot opt in out source
destination
0 0 DROP all -- any any anywhere
anywhere
Chain SHUN (0 references)
pkts bytes target prot opt in out source
destination
next prev parent reply other threads:[~2004-03-08 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 18:47 Firewall Script Help Christopher Davis
2004-03-08 18:49 ` David Cannings
2004-03-08 19:19 ` Christopher Davis [this message]
2004-03-08 20:12 ` David Cannings
2004-03-08 20:32 ` Antony Stone
2004-03-09 4:34 ` Mark E. Donaldson
2004-03-08 18:51 ` Aldo S. Lagana
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 21:14 cldavis
2004-03-08 22:06 ` Antony Stone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=JKELJHHMDHPOLKFBOEGHMECLFDAA.cldavis@speakeasy.net \
--to=cldavis@speakeasy.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox