All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guy Van Den Bergh guy.vandenbergh@pandora.be
To: lartc@vger.kernel.org
Subject: [LARTC] subinterfaces
Date: Thu, 01 Feb 2001 20:40:23 +0000	[thread overview]
Message-ID: <marc-lartc-98373940416934@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416895@msgid-missing>

<PRE>&quot;subinterfaces&quot; is no cisco speak for aliases.
The Cisco speak for aliases is &quot;secondary&quot;
In Cisco terms you can add an alias to an interface by typing:
ip address &lt;address&gt; &lt;mask&gt; secondary.
Even a third address can be added with this statement.

The subinterface concept is mainly used for running IP over frame relay 
networks.
You can have an interface to a frame relay network, with multiple 
subinterfaces for connecting to multiple hosts on the same frame relay 
network.
This has to do with the NBMA (non-broadcast multiple access) nature of 
frame relay. This basically means that basic ARP does not work on frame 
relay. And this is the reason why subinterfaces are really useful on 
these networks.

But I do not fully know this matter in Cisco, nor in Linux speak.

More information on the Cisco concept of subinterfaces can be found at:
<A HREF="http://www.cisco.com/warp/public/779/smbiz/service/knowledge/wan/subifs.htm">http://www.cisco.com/warp/public/779/smbiz/service/knowledge/wan/subifs.htm</A>

I guess John wants to know the capabilities of Linux concerning frame 
relay, but I don't know anyone with experience on this is on the list.

The linux equivalent for subinterfaces depends on what you want to do 
with it, I guess.


bert hubert wrote:

&gt;<i> On Wed, Jan 17, 2001 at 09:32:01PM -0500, John Russo wrote:
</I>&gt;<i> 
</I>&gt;&gt;<i> Does Linux support the concept of subinterfaces?  If so can anyone point
</I>&gt;&gt;<i> me in the right direction for docs?
</I>&gt;<i> 
</I>&gt;<i> 
</I>&gt;<i> I think 'subinterfaces' are Cisco speak for IP aliases - if so, yes, try
</I>&gt;<i> this:
</I>&gt;<i> 
</I>&gt;<i> ip addr add your.ip.address.here dev eth0
</I>



</PRE>

      parent reply	other threads:[~2001-02-01 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-18  2:32 [LARTC] subinterfaces John
2001-02-01  8:35 ` bert
2001-02-01 19:08 ` BURKE, PETER
2001-02-01 20:40 ` Guy [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=marc-lartc-98373940416934@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.