All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aleksandar Milivojevic <amilivojevic@pbl.ca>
To: netfilter@lists.netfilter.org
Subject: Re: Virtual interfaces
Date: Wed, 07 Jul 2004 08:50:19 -0500	[thread overview]
Message-ID: <40EBFF9B.4060603@pbl.ca> (raw)
In-Reply-To: <200407051642.19090.francesco.chicchiricco@eposse.it>

Dott. Francesco Chicchiriccò wrote:
> With physical interfaces only, all works well. When a try to filter traffic 
> between 2 LANs attached to the same physical interface but with 2 different 
> virtual IPs, it starts messing. Nothing works, I can't even log packets.

Netfilter does not know about virtual interfaces.  Use physical 
interface names in combination with source and/or destination addresses 
(for example "-i eth0 -s 192.168.0.0/24").

 From security side, you are not gaining anything by filtering between 
two virutal interfaces on the same wire -- stations on those two 
networks can talk to each other directly anyhow.  If you haven't 
disabled ICMP redirects, you'll see that Linux kernel is sending out 
ICMP redirects telling 192.168.0.1 that 192.168.1.1 is on the same wire 
and to talk to it directly.


  parent reply	other threads:[~2004-07-07 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 14:42 Virtual interfaces Dott. Francesco Chicchiriccò
2004-07-07  9:27 ` Askar Ali Khan
2004-07-07 13:50 ` Aleksandar Milivojevic [this message]
     [not found] <a0f69e5040704225918359fec@mail.gmail.com>
2004-07-05  6:27 ` virtual interfaces ip tables
2004-07-05  6:49   ` Ming-Ching Tiew
  -- strict thread matches above, loose matches on Subject: below --
2004-07-05  4:54 ip tables

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=40EBFF9B.4060603@pbl.ca \
    --to=amilivojevic@pbl.ca \
    --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.