cs427: Zebra Introduction
href="http://wiki.cs.uiuc.edu/cs427/EDIT/Zebra+Introduction">Edit
href="http://wiki.cs.uiuc.edu/cs427/RENAME/Zebra+Introduction">Rename
href="http://wiki.cs.uiuc.edu/cs427/DIFF/12/11/Zebra+Introduction">Changes
href="http://wiki.cs.uiuc.edu/cs427/HISTORY/Zebra+Introduction">History
href="http://wiki.cs.uiuc.edu/cs427/UPLOAD">Upload
href="http://wiki.cs.uiuc.edu/cs427/DOWNLOAD/">Download
Back to
Top
href="http://wiki.cs.uiuc.edu/cs427/SEARCH/Zebra+Introduction">Zebra
Introduction
--------
[NEXT > http://wiki.cs.uiuc.edu/cs427/Zebra+Generic+Router] [HOME > http://wiki.cs.uiuc.edu/cs427/Software+Architecture+of+Zebra]
---------
Introduction
Zebra is a multi-server routing software that provides TCP/IP based routing protocols. It is a free routing system designed for UNIX operating systems, including Linux, BSD, and Solaris. It is intended to be used as a route server and a route reflector as well as a normal router. The Zebra project began in 1996. Today, it is near completion and version 1.0 will be released soon.
One of the attractive features of Zebra is that it does not require dedicated hardware, such as a router, to run on. Zebra runs on several platforms, mainly PC-based platforms, such as Linux, FreeBSD, NetBSD and OpenBSD as well as SUN Solaris. A multihome computer (a host with multiple interfaces) can easily be configured as a router that runs multiple routing protocols with Zebra.
Zebra is unique in its design because it has a process for each protocol that runs on a multi-threaded UNIX kernel. Zebra software offers true modularity because each protocol module can be upgraded or configured independently of the others.
Some of the features of Zebra include:
* Common routing protocols such as RIP, OSPF, BGP supported.
* IPv6 routing protocols such as RIPng and BGP-4+ supported.
* User can dynamically change configuration from terminal interface.
* User can use command line completion and history in terminal interface.
* IP address based filtering, AS path based filtering, attribute modification
by route map are supported.
We intend finding answers to the following questions
* What is the architecture of zebra?
* How, and in what respects, does Zebra抯 architecture differ from the generic router architecture?
* What was the motivation and objective of designing Zebra the way it is designed?
* How does Zebra achieves those objectives?
* What are the true benefits of designing Zebra that way?
---------
[NEXT > http://wiki.cs.uiuc.edu/cs427/Zebra+Generic+Router] [HOME > http://wiki.cs.uiuc.edu/cs427/Software+Architecture+of+Zebra]
//-- unformatted page contents -->
href="http://wiki.cs.uiuc.edu/cs427/Zebra+Generic+Router">NEXT
HOME
Introduction
Zebra is a multi-server routing software that provides TCP/IP based routing
protocols. It is a free routing system designed for UNIX operating systems,
including Linux, BSD, and Solaris. It is intended to be used as a route server
and a route reflector as well as a normal router. The Zebra project began in
1996. Today, it is near completion and version 1.0 will be released soon.
One of the attractive features of Zebra is that it does not require dedicated
hardware, such as a router, to run on. Zebra runs on several platforms, mainly
PC-based platforms, such as Linux, FreeBSD, NetBSD and OpenBSD as well as SUN
Solaris. A multihome computer (a host with multiple interfaces) can easily be
configured as a router that runs multiple routing protocols with Zebra.
Zebra is unique in its design because it has a process for each protocol that
runs on a multi-threaded UNIX kernel. Zebra software offers true modularity
because each protocol module can be upgraded or configured independently of the
others.
Some of the features of Zebra include:
Common routing protocols such as RIP, OSPF, BGP supported.
IPv6 routing protocols such as RIPng and BGP-4+ supported.
User can dynamically change configuration from terminal interface.
User can use command line completion and history in terminal interface.
IP address based filtering, AS path based filtering, attribute
modification by route map are supported.
We intend finding answers to the following questions
What is the architecture of zebra?
How, and in what respects, does Zebra抯 architecture differ from the
generic router architecture?
What was the motivation and objective of designing Zebra the way it is
designed?
How does Zebra achieves those objectives?
What are the true benefits of designing Zebra that way?
href="http://wiki.cs.uiuc.edu/cs427/Zebra+Generic+Router">NEXT
HOME
name=COMMAND> name=SEARCHPATTERN>
href="http://wiki.cs.uiuc.edu/cs427/EDIT/Zebra+Introduction">Edit
href="http://wiki.cs.uiuc.edu/cs427/RENAME/Zebra+Introduction">Rename
href="http://wiki.cs.uiuc.edu/cs427/DIFF/12/11/Zebra+Introduction">Changes
href="http://wiki.cs.uiuc.edu/cs427/HISTORY/Zebra+Introduction">History
href="http://wiki.cs.uiuc.edu/cs427/UPLOAD">Upload
href="http://wiki.cs.uiuc.edu/cs427/DOWNLOAD/">Download
Back to
Top
