* [LARTC] subinterfaces
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
2 siblings, 0 replies; 4+ messages in thread
From: bert @ 2001-02-01 8:35 UTC (permalink / raw)
To: lartc
<PRE>On Wed, Jan 17, 2001 at 09:32:01PM -0500, John Russo wrote:
><i> Does Linux support the concept of subinterfaces? If so can anyone point
</I>><i> me in the right direction for docs?
</I>
I think 'subinterfaces' are Cisco speak for IP aliases - if so, yes, try
this:
ip addr add your.ip.address.here dev eth0
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LARTC] subinterfaces
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
2 siblings, 0 replies; 4+ messages in thread
From: BURKE, PETER @ 2001-02-01 19:08 UTC (permalink / raw)
To: lartc
<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>
^ permalink raw reply [flat|nested] 4+ messages in thread
* [LARTC] subinterfaces
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
2 siblings, 0 replies; 4+ messages in thread
From: Guy @ 2001-02-01 20:40 UTC (permalink / raw)
To: lartc
<PRE>"subinterfaces" is no cisco speak for aliases.
The Cisco speak for aliases is "secondary"
In Cisco terms you can add an alias to an interface by typing:
ip address <address> <mask> 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:
><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>
</PRE>
^ permalink raw reply [flat|nested] 4+ messages in thread