From: Andrew Beverley <andy@andybev.com>
To: Aadith Koshy <ak699f@att.com>
Cc: "netfilter@vger.kernel.org" <netfilter@vger.kernel.org>
Subject: Re: Details on iif in ip rule
Date: Wed, 21 Dec 2011 09:01:12 +0000 [thread overview]
Message-ID: <1324458072.4269.37.camel@steve-pc> (raw)
In-Reply-To: <alpine.LNX.2.01.1112210318020.5980@frira.zrqbmnf.qr>
On Wed, 2011-12-21 at 03:20 +0100, Jan Engelhardt wrote:
> On Wednesday 2011-12-21 01:08, Aadith Koshy wrote:
>
> >Hi Team,
> >
> >I am having some trouble understanding 'iif' on the ip rules. Let me
> >explain what I am trying out. I have 3 virtual interfaces on a single
> >interface.
>
> stop using net-tools. Use iproute2.
Aadith: Jan is right. You need to use iproute2. As a starter for 10, you
need to do something like:
ip address add 192.168.5.0/24 dev eth0
rather than whatever ifconfig rule you are using.
Andy
prev parent reply other threads:[~2011-12-21 9:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 0:08 Details on iif in ip rule Aadith Koshy
2011-12-21 2:20 ` Jan Engelhardt
2011-12-21 9:01 ` Andrew Beverley [this message]
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=1324458072.4269.37.camel@steve-pc \
--to=andy@andybev.com \
--cc=ak699f@att.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).