Can someone explain, in plain English, the difference between type 1 and
type 2 calculations? Mikortik only explains it is white box vs something
else.  Cisco says A type 1 route has a metric that is the
sum of the internal OSPF cost and the external redistributed cost. A type 2
route has a metric equal only to the redistributed cost.

 Justin
-- 
Justin Wilson <j...@mtin.net>
Aol & Yahoo IM: j2sw
http://www.mtin.net/blog ­ xISP News
http://www.twitter.com/j2sw ­ Follow me on Twitter
Wisp Consulting ­ Tower Climbing ­ Network Support




On 3/5/11 10:49 AM, "can...@believewireless.net"
<p...@believewireless.net> wrote:

>Basically, what is the fastest link in your network?  Let's say you
>have a GigE link.  You'll set that cost to 1.  Let's say you have a
>backup link that is a licensed 18GHz link that runs 350 Mbps.  You
>would make that cost a 3.  Then, you have a half-duplex Ubiquiti link.
> Normally you would count it as 100 Mbps but since it's half duplex,
>you might want to divied it by two.  So, instead of setting it to 10,
>you'd set it to 20.
>
>If you have equal cost link but want one favored over the other,
>adjust the priority.
>
>Then, make sure you are using the correct type 1/type 2 calculations
>for your network typology.
>
>
>--------------------------------------------------------------------------
>------
>WISPA Wants You! Join today!
>http://signup.wispa.org/
>--------------------------------------------------------------------------
>------
> 
>WISPA Wireless List: wireless@wispa.org
>
>Subscribe/Unsubscribe:
>http://lists.wispa.org/mailman/listinfo/wireless
>
>Archives: http://lists.wispa.org/pipermail/wireless/
>




--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Reply via email to