[Xorp-users] Q: Configuring static routes in OSPF

Knowles, Thomas thomas.knowles at advatechpacific.com
Wed Dec 16 12:25:40 PST 2009


I have not been able to get a static route to show up in LSAs
Several variations of the configuration below have been tried.

interfaces {
    interface eth1 {
        default-system-config
    }
    interface eth0 {
        default-system-config
    }
    interface tun1 {
        default-system-config
    }
    interface tun2 {
        default-system-config
    }
}

policy {
    policy-statement connected {
        term export {
            from {
                protocol: "connected"
            }
        }
    }
}

policy {
    policy-statement static {
        term export {
            from {
                protocol: "static"
            }
        }
    }
}

fea {
    unicast-forwarding4 {
        disable: false
    }
}
protocols {
   static {
        mrib-route 192.168.51.0/26 {
            next-hop: 192.168.51.4
        }
    }

    fib2mrib {
    }

    ospf4 {
        export: "static"
/*        export: "connected" */
        router-id: 192.168.37.2
        traceoptions {
            flag {
                all {
                    disable: true
                }
            }
        }
        area 0.0.0.0 {
            interface eth0 {
                vif eth0 {
                    address 192.168.51.4 {
                        priority: 0
                    }
                }
            }
            interface eth1 {
                vif eth1 {
                    address 192.168.37.2 {
                    }
                }
            }
           interface tun1 {
                vif tun1 {
                    address 10.1.0.1 {
                    }
                }
            }
            interface tun2 {
                vif tun2 {
                    address 10.1.1.1 {
                    }
                }
            }
        }
    }
}

Background:
The topology can NOT be changed.
IP forwarding is enabled and rp_filtering is disabled
There will not be any routers connected to this router eth0
I know that the static route is defined as mirb, so fib2mirb is not required
Xorpsh shows version 1.6

The tunnels and the eth1 ip addresses are seen with:
Show route table ipv4 multicast final
10.1.0.0/26     [connected(0)/0]
                > via tun1/tun1
10.1.1.0/26     [connected(0)/0]
                > via tun2/tun2
10.1.2.0/26     [fib2mrib(254)/2]
                > to 10.1.0.2 via tun1/tun1
192.168.37.0/26 [connected(0)/0]
                > via eth1/eth1
192.168.37.64/26        [fib2mrib(254)/65535]
                > to 192.168.37.1 via eth1/eth1
192.168.37.128/26       [fib2mrib(254)/65535]
                > to 192.168.37.1 via eth1/eth1
192.168.37.2/32 [connected(0)/0]
                > via eth1/eth1
192.168.37.66/32        [connected(0)/0]
                > via tun1/tun1
192.168.37.130/32       [connected(0)/0]
                > via tun2/tun2

The physical connections are as follows:
This router(A) has 2 phys: eth0 & eth1
Two other routers(B & C) are attached via two other linksys routers into a network switch
A third linksys router is attached to this router eth1 and then to the switch
So each of the Xorp routers are exchanging information via tunnels (tun1 & tun2)
The static route is configured for this routers eth0

192.168.51.0/26 <->[192.168.51.4 (eth0 routerA eth1) 192.168.37.2/26 ] <----------------------> [.37.1 linksys routerA] <-> { switch }
xxx.xxx.xx.x/26 <->[xxx.xxx.xx.x (eth0 routerB eth1) 192.168.37.64/26]  <- tun1 10.1.0.0/26 --> [.xx.x linksys routerB] <-------^
xxx.xxx.xx.x/26 <->[xxx.xxx.xx.x (eth0 routerC eth1) 192.168.37.128/26] <- tun2 10.1.1.0/26 --> [.xx.x linksys routerC] <---------^

Thank you in advance for the help!  mGby!
Tom Knowles


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20091216/d7d081dc/attachment-0001.html 


More information about the Xorp-users mailing list