All of lore.kernel.org
 help / color / mirror / Atom feed
From: Damion de Soto <damion@snapgear.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Aliases and Multipath
Date: Mon, 08 Dec 2003 00:37:21 +0000	[thread overview]
Message-ID: <marc-lartc-107084406011453@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107055227804578@msgid-missing>



Hi Guillermo,

> iptables just does not likes eth0:1 neither eth0:2, is this the right
> behaviour of iptables or what? i read something about NAT in advance
> routing engine but never used before and i'm little confuse on how it
> works. Will it crash with iptables NAT engine?
As far as I know, the ethX:X terminology is just for ifconfig usage.
Inside the kernel, eth0:1 is exactly the same as eth0.
So for iptables rules, you just use the eth0:1 IP address with eth0.
this is the same way the 'ip' tool works too.


Regards,
Damion.


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Damion de Soto - Software Engineer  email:     damion@snapgear.com
SnapGear - A CyberGuard Company ---    ph:         +61 7 3435 2809
  | Custom Embedded Solutions          fax:         +61 7 3891 3630
  | and Security Appliances            web: http://www.snapgear.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  ---  Free Embedded Linux Distro at   http://www.snapgear.org  ---

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

  parent reply	other threads:[~2003-12-08  0:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 15:06 [LARTC] Aliases and Multipath Guillermo Gomez
2003-12-05 14:03 ` Guillermo Gomez
2003-12-08  0:37 ` Damion de Soto [this message]
2003-12-08 11:34 ` Guillermo Gomez
2003-12-08 12:35 ` Jose Luis Domingo Lopez
2003-12-10  4:12 ` Damion de Soto

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-107084406011453@msgid-missing \
    --to=damion@snapgear.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.