From: BURKE, PETER peter.burke@connexim.ca
To: lartc@vger.kernel.org
Subject: [LARTC] subinterfaces
Date: Thu, 01 Feb 2001 19:08:25 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416937@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416895@msgid-missing>
<PRE>Both subinterfaces and secondairy interfaces are configurable on a Cisco router. A
secondary interface is usualy used we you use up all you ip addresses in an
assigned subnet and you ned more addresses. On the other had subinterfaces are used
to create logical interfaces, are usualy used to get around the split horizin
problem and frame relay or atm networks. Basicaly secondairy address meens one
interface with multible addresses, and subinterfaces meen multiple ilogical
interfaces.
Guy Van Den Bergh wrote:
><i> "subinterfaces" is no cisco speak for aliases.
</I>><i> The Cisco speak for aliases is "secondary"
</I>><i> In Cisco terms you can add an alias to an interface by typing:
</I>><i> ip address <address> <mask> secondary.
</I>><i> Even a third address can be added with this statement.
</I>><i>
</I>><i> The subinterface concept is mainly used for running IP over frame relay
</I>><i> networks.
</I>><i> You can have an interface to a frame relay network, with multiple
</I>><i> subinterfaces for connecting to multiple hosts on the same frame relay
</I>><i> network.
</I>><i> This has to do with the NBMA (non-broadcast multiple access) nature of
</I>><i> frame relay. This basically means that basic ARP does not work on frame
</I>><i> relay. And this is the reason why subinterfaces are really useful on
</I>><i> these networks.
</I>><i>
</I>><i> But I do not fully know this matter in Cisco, nor in Linux speak.
</I>><i>
</I>><i> More information on the Cisco concept of subinterfaces can be found at:
</I>><i> <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>><i>
</I>><i> I guess John wants to know the capabilities of Linux concerning frame
</I>><i> relay, but I don't know anyone with experience on this is on the list.
</I>><i>
</I>><i> The linux equivalent for subinterfaces depends on what you want to do
</I>><i> with it, I guess.
</I>><i>
</I>><i> bert hubert wrote:
</I>><i>
</I>><i> > On Wed, Jan 17, 2001 at 09:32:01PM -0500, John Russo wrote:
</I>><i> >
</I>><i> >> Does Linux support the concept of subinterfaces? If so can anyone point
</I>><i> >> me in the right direction for docs?
</I>><i> >
</I>><i> >
</I>><i> > I think 'subinterfaces' are Cisco speak for IP aliases - if so, yes, try
</I>><i> > this:
</I>><i> >
</I>><i> > ip addr add your.ip.address.here dev eth0
</I>><i>
</I>><i> _______________________________________________
</I>><i> LARTC mailing list / <A HREF="mailto:LARTC@mailman.ds9a.nl">LARTC@mailman.ds9a.nl</A>
</I>><i> <A HREF="http://mailman.ds9a.nl/mailman/listinfo/lartc">http://mailman.ds9a.nl/mailman/listinfo/lartc</A> HOWTO: <A HREF="http://ds9a.nl/2.4Routing/">http://ds9a.nl/2.4Routing/</A>
</I>
</PRE>
next prev parent reply other threads:[~2001-02-01 19:08 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 [this message]
2001-02-01 20:40 ` Guy
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-98373940416937@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.