All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michelle Konzack <linux4michelle@freenet.de>
To: netfilter@lists.netfilter.org
Subject: Routing problem...
Date: Tue, 27 Jul 2004 09:23:29 +0200	[thread overview]
Message-ID: <20040727072329.GV20473@freenet.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

*************************************************************************
* Do not Cc: me, because I am on THIS list, if I write here             *
* Keine Cc: am mich senden, bin auf DIESER Liste wenn ich hier schreibe *
*************************************************************************

Hello, 

I have 4 NICs in my Router and with two I have a problem:

eth0	-> public network with Servers
eth1    -> private network with Workstations.

I have following rules:

  ____ ( 'stdin' ) _____________________________________________________
 /
|  iptables -P INPUT ACCEPT
|  iptables -F INPUT 
|  iptables -P OUTPUT ACCEPT
|  iptables -F OUTPUT 
|  iptables -P FORWARD DROP
|  iptables -F FORWARD 
|  
|  iptables -A FORWARD -i eth1 -o eth0 -j ACCEPT

OK, I can SEND packages from my Workstations in eth1 
to the Servers in eth0

|  iptables -A FORWARD -i eth0 -o eth1 -m state --state ESTABLISHED,RELATED -j ACCEPT

Here comes the Packages from the Servers back and 
I allow to come into my private Network

 \______________________________________________________________________

But if I execute the script, I get: 

iptables: No chain/target/match by that name

Whats wrong ?
I have compiled Linux with ALL netfilter modules in.

Greetings
Michelle

-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/ 
Michelle Konzack   Apt. 917                  ICQ #328449886
                   50, rue de Soultz         MSM LinuxMichi
0033/3/88452356    67100 Strasbourg/France   IRC #Debian (irc.icq.com)

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2004-07-27  7:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  7:23 Michelle Konzack [this message]
2004-07-27  7:42 ` Routing problem Sven Schuster
2004-07-27  8:06   ` Michelle Konzack
2004-07-27 14:21     ` Sven Schuster
2004-07-28  8:32       ` Michelle Konzack
  -- strict thread matches above, loose matches on Subject: below --
2006-05-15 16:08 Yang, Steve
2006-05-15 19:39 ` Antonio Di Bacco
2006-05-12 20:53 Antonio Di Bacco
2004-02-13 15:39 Carlos Fernandez Sanz
2004-02-13 15:50 ` Antony Stone
2004-02-13 16:30   ` Carlos Fernandez Sanz
2004-02-13 17:12     ` Antony Stone
2004-02-14  8:41       ` Carlos Fernandez Sanz
2004-02-14  9:09         ` Antony Stone
2004-02-14 15:15           ` Carlos Fernandez Sanz
2004-02-14 15:19           ` Carlos Fernandez Sanz
2004-02-14 15:38             ` Antony Stone
2004-02-13 17:16     ` Scott MacKay
2004-02-14  8:47       ` Carlos Fernandez Sanz
2004-02-13 16:53 ` John A. Sullivan III
2003-08-13 18:26 GG Noris
2003-06-06 18:22 Editing File Associations in KDE Rex Dieter
2003-06-07  1:17 ` Routing Problem lance turner
2003-06-07  2:27   ` terry white
2003-06-07  3:46   ` Joakim Ryden
2003-06-07  3:46   ` Joakim Ryden
2002-09-20 14:29 Tom Fischer

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=20040727072329.GV20473@freenet.de \
    --to=linux4michelle@freenet.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.