Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Marco Strullato" <batstru@email.it>
To: netfilter@lists.netfilter.org
Subject: Re: again problem with alias / virtual interface
Date: Mon, 19 Jul 2004 18:30:32 +0200	[thread overview]
Message-ID: <007d01c46dae$0a45f330$eb53623e@x> (raw)
In-Reply-To: 40FC2286.3070005@pbl.ca

> > -A INPUT -p tcp -m tcp -m state -i eth1:1 -d 82.186.92.91 --dport
25 --state
> > NEW -j ACCEPT
>
> And here is the error.
>
> As me (and I believe Antony, possibly others) already told you,
> Netfilter does not know about virtual interfaces.  Virtual interfaces
> are abstractions that exist in higher levels of kernel than Netfilter
> is.  Netfilter is concerned only on which *physical* interface the
> packet is.  Replace "-i eth1:1" with "-i eth1" in above rule (and same
> for all other virtual interfaces you have) and you'll be fine:
>
> -A INPUT -p tcp -m tcp -m state -i eth1 -d 82.186.92.91 --dport 25
> --state NEW -j ACCEPT

I've tried with just eth1 but the rule is not applied, or it seems not to be
applied

I've seen that using virtual interfaes is deprecated so I tryed to set
multilple ip with iproute.
If I set network interfaces only with iproute and not with ifconfig, network
configuration seems to be absent.
If I set network with ifconfig and not with iproute, network configuration
seems ok
So I can't to use iproute (to set interfaces) and iptables becacuse network
configuration is absent.

best regards

marco



 

 

 --

 Email.it, the professional e-mail, gratis per te: http://www.email.it/f

 

 Sponsor:

 Rinfresca la tua estate con i climatizzatori ed i ventilatori

* che trovi disponibili… Crios, Orieme, Hokkaido, Argo, Carrier, Vortice

 Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=2650&d=20-7


  reply	other threads:[~2004-07-19 16:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-19 18:55 again problem with alias / virtual interface Batstru
2004-07-19 19:10 ` George Alexandru Dragoi
2004-07-19 16:17   ` Marco Strullato
2004-07-19 19:14 ` Antony Stone
2004-07-19 19:35 ` Aleksandar Milivojevic
2004-07-19 16:30   ` Marco Strullato [this message]
2004-07-20 19:09     ` Antony Stone
2004-07-20 19:12     ` Aleksandar Milivojevic
2004-07-20 19:22       ` Aleksandar Milivojevic
2004-07-21 15:34     ` Marco Colombo
2004-07-21 16:48       ` Michael Sconzo
2004-07-21 17:13         ` Aleksandar Milivojevic
2004-07-22  2:27           ` Michael Sconzo
2004-07-22 16:58             ` Aleksandar Milivojevic
2004-07-22  8:53           ` Marco Colombo
2004-07-22 16:05             ` Michael Sconzo
2004-07-19 19:46 ` Jamie Pratt
2004-07-19 19:58   ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2004-07-21 10:31 Batstru
2004-07-21 17:09 ` Aleksandar Milivojevic

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='007d01c46dae$0a45f330$eb53623e@x' \
    --to=batstru@email.it \
    --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