[Xorp-users] Fwd: Route redistribution issue

[Phil Wiggins]

Igor,

The tag issue seems significant for a generalized fix. One of our team
members has a workaround using an import policy for ospf4:
...
protocols {

rip {
            export: "connected-to-rip,ospf4-to-rip"
 ...
    }

    ospf4 {
    export: "connected-to-ospf4,rip-to-ospf4"
    import: "convert-metric"
router-id: 10.0.2.2
 area 0.0.0.0 {
    interface eth0 {
 vif eth0 {
    address 10.0.2.2 {
 interface-cost: 1
    }
 }
    }
 }
    }
}

policy {
    policy-statement connected-to-rip {
...
    }
    policy-statement connected-to-ospf4 {
...
    }
    policy-statement rip-to-ospf4 {
...
    }
    policy-statement ospf4-to-rip {
...
    }
    policy-statement convert-metric {
term 100 {
 from {
metric > 13
 }
then {
 metric sub 9
accept
 }
}
 }
}

Phil

On Fri, Jul 20, 2012 at 12:57 PM, Phil Wiggins <phil.wiggins at gmail.com>wrote:

> n2 output
> =========
> root at n2> show route table ipv4 unicast final
> 10.0.0.0/24     [connected(0)/0]
>                 > via eth0/eth0 TAGS 0
> 10.0.1.0/24     [connected(0)/0]
>                 > via eth1/eth1 TAGS 0
> 10.0.2.0/24     [rip(120)/2]
>                 > to 10.0.1.2 via eth1/eth1 TAGS
> 10.0.3.0/24     [rip(120)/12]
>                 > to 10.0.1.2 via eth1/eth1 TAGS
> 10.0.7.0/24     [rip(120)/2]
>                 > to 10.0.1.2 via eth1/eth1 TAGS
> 10.0.8.0/24     [rip(120)/2]
>                 > to 10.0.1.2 via eth1/eth1 TAGS
> root at n2>
> /snip/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120721/21818d7c/attachment.html