From: billy billy@ciudadglobal.com.ar
To: lartc@vger.kernel.org
Subject: [LARTC] IP Aliasing with "IP"?
Date: Tue, 30 Jan 2001 21:08:00 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416928@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416926@msgid-missing>
<PRE>On Tuesday 30 January 2001 17:51, you wrote:
><i> On Tue, Jan 30, 2001 at 05:50:01PM -0300, billy wrote:
</I>><i> > Can I do something like this?
</I>><i> >
</I>><i> > old way:
</I>><i> >
</I>><i> > ifconfig eth1 192.168.101.1 netmask 255.255.255.0 up
</I>><i> > route add -net 192.168.101.0 netmask 255.255.255.0 eth1
</I>><i> > ifconfig eth1:0 192.168.101.1 netmask 255.255.255.0 up
</I>><i> > route add -net 192.168.101.0 netmask 255.255.255.0 eth1:0
</I>><i>
</I>><i> ip addr add dev eth0 192.168.101.1 etc etc should work
</I>
OK, but what about eth0:0, the alias ? if I do something like:
# ip addr add dev eth0:0 192.168.101.1 etc etc
I get an error:
cannot find device "eth0:0"
but I can create eth0:0 with ifconfig, but "ip link show" does not show me
the interfaces, but with "ip route show" I see all of the eth0:x as only eth0.
# ip route show
200.51.164.128/29 dev eth0 proto kernel scope link src 200.51.164.131
192.168.101.0/24 dev eth0 proto kernel scope link src 192.168.101.1
192.168.102.0/24 dev eth0 proto kernel scope link src 192.168.102.1
127.0.0.0/8 dev lo scope link
default via 200.51.164.134 dev eth0
#
is this ok? I haev to create the "virtual" interfaces with ifconfig or do I
have a way with ip?
thanks billy
</PRE>
next prev parent reply other threads:[~2001-01-30 21:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 20:50 [LARTC] IP Aliasing with "IP"? billy
2001-01-30 20:51 ` bert
2001-01-30 21:08 ` billy [this message]
2001-01-30 21:26 ` bert
2001-01-30 22:59 ` Arkadiusz
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-98373940416928@msgid-missing \
--to=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.