[Xorp-users] Fwd: Route redistribution issue

[Igor Maravić]

I really didn't have time to boot up your configuration with Quagga.
Could you apply patch that I've attached in email to n3 i n8 machines.
After you do that, turn on the network and send me in email what do you see
when you enter

show route table ipv4 unicast final

in xorpsh on n3 and n8. I'm interested in TAG field, which I added via
patch that I've attached.
BR
Igor

2012/7/17 Phil Wiggins <phil.wiggins at gmail.com>

> Igor,
>
> Thanks for looking into this issue.  I've also attached a CORE4.3 imn
> file, if that helps.  Once the network converges, the subnet at
> 10.0.6.0/24 isn't visible to nodes n1 and n2.  Similarly, the subnet at
> 10.0.2.0/24 isn't visible to nodes n9 and n10.
>
> Here are the config.boots for n3 and n8, slightly cleaned up from the
> previous post:
>
> n3:config.boot
> ==============
> interfaces {
>      interface eth0 {
> vif eth0 {
>     address 10.0.1.2 {
>  prefix-length: 24
>     }
>     }
> }
>     interface eth1 {
> vif eth1 {
>      address 10.0.2.2 {
>  prefix-length: 24
>      }
>  }
>     }
> }
>
> fea {
>     unicast-forwarding4 {
> disable:false
>     }
> }
>
> protocols {
>     rip {
>        export: "connected-to-rip,ospf4-to-rip"
>        interface eth0 {
>     vif eth0 {
> address 10.0.1.2 {
>  disable: false
>   }
>     }
> }
>     }
>     ospf4 {
>         export: "connected-to-ospf4,rip-to-ospf4"
>         router-id: 10.0.2.2
>         area 0.0.0.0 {
>             interface eth1 {
>                 vif eth1 {
>                     address 10.0.2.2 {
>                     }
>                 }
>             }
>         }
>     }
> }
>
> policy {
>     policy-statement connected-to-rip {
>         term 100 {
>             from {
>                 protocol: "connected"
>             }
>      then {
>  metric: 1
> accept
>      }
>         }
>     }
>     policy-statement connected-to-ospf4 {
>         term 200 {
>             from {
>                 protocol: "connected"
>             }
>     then {
> accept
>  }
>         }
>     }
>     policy-statement rip-to-ospf4 {
>         term 300 {
>             from {
>                 protocol: "rip"
>             }
>             then {
>  metric add 0
> accept
>             }
>         }
>     }
>     policy-statement ospf4-to-rip {
>         term 400 {
>             from {
>                 protocol: "ospf4"
>             }
>             then {
> metric add 0
>                 accept
>             }
>         }
>     }
> }
> n8:config.boot
> ==============
> interfaces {
>     interface eth0 {
> vif eth0 {
>     address 10.0.6.1 {
>  prefix-length: 24
>     }
> }
>     }
>     interface eth1 {
> vif eth1 {
>     address 10.0.7.1 {
>  prefix-length: 24
>     }
> }
>     }
> }
>
> fea {
>     unicast-forwarding4 {
> disable:false
>     }
> }
>
> protocols {
>     ospf4 {
>         export: "connected-to-ospf4,rip-to-ospf4"
> router-id: 10.0.6.1
> area 0.0.0.0 {
>     interface eth0 {
> vif eth0 {
>     address 10.0.6.1 {
>     disable: false
>     }
> }
>     }
> }
>     }
>     rip {
>         export: "connected-to-rip,ospf4-to-rip"
>  interface eth1 {
>     vif eth1 {
> address 10.0.7.1 {
>     disable: false
> }
>     }
>  }
>     }
> }
>
> policy {
>     policy-statement connected-to-rip {
>         term 100 {
>             from {
>                 protocol: "connected"
>             }
>      then {
>  metric: 1
> accept
>      }
>         }
>     }
>     policy-statement connected-to-ospf4 {
>         term 200 {
>             from {
>                 protocol: "connected"
>             }
>     then {
> accept
> }
>         }
>     }
>     policy-statement rip-to-ospf4 {
>         term 300 {
>             from {
>                 protocol: "rip"
>             }
>             then {
> metric add 0
> accept
>             }
>         }
>     }
>     policy-statement ospf4-to-rip {
>         term 400 {
>             from {
>                 protocol: "ospf4"
>             }
>             then {
>  metric add 0
>                 accept
>             }
>         }
>     }
> }
>
> Phil
>
>
> On Tue, Jul 17, 2012 at 6:39 PM, Igor Maravić <igorm at etf.rs> wrote:
>
>> Phil,
>> Could You send whole configuration file for n3 and n8. If I understood
>> correctly, problem is that connected route 10.0.2.0/24 and 10.0.6.0/24aren't redistributed in RIP.
>> I'll try it to look at the problem as soon as I find some time.
>> BR
>> Igor
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120720/da201914/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-DEBUG-REDISTRIBUTION.patch
Type: application/octet-stream
Size: 10136 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20120720/da201914/attachment-0001.obj