Default-free zone: Difference between revisions
Jump to navigation
Jump to search
imported>Howard C. Berkowitz (New page: A router in the '''default zone (DFZ)''' has only explicit routes in its routing information base; it gets all routing information from local configuration and dynamic [[routing pr...) |
imported>Howard C. Berkowitz No edit summary |
||
| Line 1: | Line 1: | ||
{{subpages}} | |||
A [[router]] in the '''default zone (DFZ)''' has only explicit routes in its [[routing information base]]; it gets all routing information from local configuration and dynamic [[routing protocol]]s. Its tables contain no default routes. | A [[router]] in the '''default zone (DFZ)''' has only explicit routes in its [[routing information base]]; it gets all routing information from local configuration and dynamic [[routing protocol]]s. Its tables contain no default routes. | ||
[[Internet Service Provider]] (ISP) interprovider routers are normally in the DFZ. Large enterprise edge routers that connect to multiple ISPs may be in the DFZ. Any production DFZ router will run the [[Border Gateway Protocol]] as its major means of acquiring routing information. | [[Internet Service Provider]] (ISP) interprovider routers are normally in the DFZ. Large enterprise edge routers that connect to multiple ISPs may be in the DFZ. Any production DFZ router will run the [[Border Gateway Protocol]] as its major means of acquiring routing information. | ||
Revision as of 00:51, 27 July 2008
A router in the default zone (DFZ) has only explicit routes in its routing information base; it gets all routing information from local configuration and dynamic routing protocols. Its tables contain no default routes.
Internet Service Provider (ISP) interprovider routers are normally in the DFZ. Large enterprise edge routers that connect to multiple ISPs may be in the DFZ. Any production DFZ router will run the Border Gateway Protocol as its major means of acquiring routing information.