From 899623cd9e004ac252b58453f3138eb9c4f7860d Mon Sep 17 00:00:00 2001 From: teastep Date: Mon, 19 May 2003 13:55:56 +0000 Subject: [PATCH] Remove obsolete files git-svn-id: https://shorewall.svn.sourceforge.net/svnroot/shorewall/trunk@558 fbd18981-670d-0410-9b5c-8dc0c1a9a2bb --- Shorewall-docs/hosts_file.htm | 21 ---- Shorewall-docs/mailing_list_problems.htm | 49 -------- Shorewall-docs/netfilter_overview.htm | 140 ----------------------- Shorewall-docs/spam_filters.htm | 69 ----------- 4 files changed, 279 deletions(-) delete mode 100644 Shorewall-docs/hosts_file.htm delete mode 100644 Shorewall-docs/mailing_list_problems.htm delete mode 100644 Shorewall-docs/netfilter_overview.htm delete mode 100644 Shorewall-docs/spam_filters.htm diff --git a/Shorewall-docs/hosts_file.htm b/Shorewall-docs/hosts_file.htm deleted file mode 100644 index c06d22058..000000000 --- a/Shorewall-docs/hosts_file.htm +++ /dev/null @@ -1,21 +0,0 @@ - - - - - - - -The Hosts File - - - - - -

The Hosts File

-

Since there seems to be a lot of confusion regarding the -/etc/shorewall/hosts file, I have created this page to try to clear the fog.

-

 

- - - - diff --git a/Shorewall-docs/mailing_list_problems.htm b/Shorewall-docs/mailing_list_problems.htm deleted file mode 100644 index 5d91d695d..000000000 --- a/Shorewall-docs/mailing_list_problems.htm +++ /dev/null @@ -1,49 +0,0 @@ - - - - - - - - - - - - Mailing List Problems - - - - - - - - - - -
- -

Mailing List Problems

-
- -

Shorewall.net is currently experiencing mail delivery problems - to at least one address in each of the following domains:

- -
-
- 
2020ca - delivery to this domain has been disabled (cause unknown)
arosy.de - delivery to this domain has been disabled (Relay access denied)
arundel.homelinux.org - delivery to this domain has been disabled (connection timed out, connection refused)
asurfer.com - (Mailbox full)
bol.com.br - delivery to this domain has been disabled (Mailbox Full)
cuscominc.com - delivery to this domain has been disabled (bouncing mail from all sources with "Mail rejected because the server you are sending to is misconfigured").
cvnet.psi.br - (DNS configuration error -- MX is cvn-srv1.cvnet.psi.br.cvnet.psi.br)
datakota.com - (DNS Timeouts)
excite.com - delivery to this domain has been disabled (cause unknown)
epacificglobal.com - delivery to this domain has been disabled (no MX record for domain)
freefish.dyndns.org - delivery to this domain has been disabled (Name Server Problem -- Host not found)
gmx.net - delivery to this domain has been disabled (cause unknown)
hotmail.com - delivery to this domain has been disabled (Mailbox over quota)
intercom.net - delivery to this domain has been disabled (cause unknown)
nitialcs.com - delivery to this domain has been disabled (cause unknown)
intelligents.2y.net - delivery to this domain has been disabled (Name Service Problem -- Host not Found).
khp-inc.com - delivery to this domain has been disabled (anti-virus problems)
kieninger.de - delivery to this domain has been disabled (relaying to <xxxxx@kieninger.de> prohibited by administrator)
lariera.com - delivery to this domain has been disabled (Unknown User)
mfocus.com.my - delivery to this domain has been disabled (MTA at mailx.mfocus.com.my not delivering and not giving a reason)
navair.navy.mil - delivery to this domain has been disabled (A restriction in the system prevented delivery of the message)
opermail.net - delivery to this domain has been disabled (cause unknown)
penquindevelopment.com - delivery to this domain has been disabled (connection timed out)
scip-online.de - delivery to this domain has been disabled (cause unknown)
spctnet.com - connection timed out - delivery to this domain has been disabled
telusplanet.net - delivery to this domain has been disabled (cause unknown)
the-techy.com - delivery to this domain has been disabled  (clueless administrator - continuous DNS problems) 
yahoo.com - delivery to this domain has been disabled (Mailbox over quota)
-
-
- -

Last updated 12/17/2002 02:51 GMT - Tom Eastep

- -

Copyright © 2002 Thomas M. Eastep.

- -

 

-
- - diff --git a/Shorewall-docs/netfilter_overview.htm b/Shorewall-docs/netfilter_overview.htm deleted file mode 100644 index 76d8a3e87..000000000 --- a/Shorewall-docs/netfilter_overview.htm +++ /dev/null @@ -1,140 +0,0 @@ - - - - - - - -Netfilter Overview - - - - - -

Netfilter Overview

-
-

 

-

1.0 Tables

- -

Chains of rules are organized into Tables. -Netfilter currently has three tables.

- -
    -
  1. -

    Mangle Table - This allows the contents of the packet to be -changed. Shorewall uses rules in this table to mark packets for traffic -shaping/control (/etc/shorewall/tcrules file) and for setting the Type of -Service (TOS) for the packet (/etc/shorewall/tos).

    - -
    2. -
  2. -

    NAT Table - Allows modification of the source and destination IP -and port.

    - -
    3. -
  3. -

    Filter Table - This is where most ACCEPT/DROP/REJECT decisions -are made in Shorewall.

    - -
    4. -
-

Each table has a number of pre-defined chains as shown in -the table that follows. Packets flow through the chains in the order of that -table.

- -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
OrdinalTableChainShorewall UsageComments
1ManglePREROUTING -
    -
  1. RFC 1918 Destination Rejections
    2. -
  2. Marking Packets for Traffic Control
    3. -
  3. TOS
    4. -
- 		 
2NATPREROUTING -
    -
  1. DNAT Rules
    2. -
  2. Static NAT DNAT mapping
    3. -
- 		Only connection requests go here -- packets that are part of or - related to an established connection use information from the connection - tracking table.
3FilterINPUT<zone>2fw filtering 
3FilterFORWARD<zone>2<zone> filtering 
3FilterOUTPUTfw2<zone> filtering 
4ManglePOSTROUTINGTOS 
5NATOUTPUTDNAT rules where the source zone is fwOnly connection requests go here -- packets that are part of or - related to an established connection use information from the connection - tracking table.
5NATPOSTROUTING -
    -
  1. Masquerading (/etc/shoreawll/masq)
    2. -
  2. SNAT (/etc/shorewall/masq)
    3. -
  3. Static NAT SNAT Mapping
    4. -
- 		Only connection requests go here -- packets that are part of or - related to an established connection use information from the connection - tracking table.
-
-

The connection tracking table can be displayed using the -"shorewall show connections" command.

- - - - diff --git a/Shorewall-docs/spam_filters.htm b/Shorewall-docs/spam_filters.htm deleted file mode 100644 index 41f9cd513..000000000 --- a/Shorewall-docs/spam_filters.htm +++ /dev/null @@ -1,69 +0,0 @@ - - - - - - - - - - - - SPAM Filters - - - - - - - - - - -
-

SPAM Filters

-
- -


- (SpamAssassin Logo) - -

- -

Like all of you, I'm concerned about the increasing volume of Unsolicited - Commercial Email (UCE or SPAM). I am therefore sympathetic with those of -you who are installing SPAM filters on your mail servers. A couple of recent -incidents involving mis-configured filters have prompted me to establish this -page to spell out what I will do when these filters bounce list postings.

- -

When your SPAM filter bounces/rejects list mail and I can identify -who you are, I will:

- -
    -
  1. immediately turn off delivery to you from all Shorewall lists to -which you subscribe.
    2. -
  2. try to send you an email from a source other than shorewall.net
    3. - -
- -

When you have corrected the problem, please let me know and I will re-enable - delivery (or you can reenable delivery yourself).
-

-

Note that many brain-dead spam filters inform the sender that a post was -rejected as spam but fail to provide any clue about the original addressee!!! -If I don't know who you are, I can't tell you about the problem...
-

- -

Last Updated 1/29/2003 - Tom Eastep

- -

Copyright - © 2001, 2002, 2003 Thomas M. Eastep.

-
-
- -