All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] additional routes?
Date: Fri, 29 Nov 2002 05:48:01 +0000	[thread overview]
Message-ID: <marc-lartc-103854898002622@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103849751630293@msgid-missing>


Tomas,

I'm glad to be of help.

 : if i want to allow hosts from network A to reach and talk to hosts on
 : network C, but _not_ hosts on network B, is this best controlled by
 : iptables? since i now probably need to specify the route to network B
 : in that very table, i cannot deny network A hosts to talk to network B
 : with ip, or can i?

I'd suggest you use iptables and a prohibit route:

  http://plorf.net/linux-ip/html/tools-ip-route.htm#EX-TOOLS-IP-ROUTE-ADD-FROM

Here's an example:

# ip route add prohibit x.x.x.x/24 from y.y.y.y/24

I would be inclined to block packets at the packet filter as well.

# iptables -t filter -A FORWARD -d x.x.x.x/24 -s y.y.y.y/24 -j REJECT

Good luck,

-Martin

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-11-29  5:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-28 15:30 [LARTC] additional routes? Tomas Bonnedahl
2002-11-28 22:32 ` Martin A. Brown
2002-11-28 23:35 ` Tomas Bonnedahl
2002-11-29  5:48 ` Martin A. Brown [this message]
2002-11-29  7:39 ` Tomas Bonnedahl

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=marc-lartc-103854898002622@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --cc=lartc@vger.kernel.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.