[Xorp-hackers] OLSR seems to be mostly working, but no subnet routes
Bruce Simpson
bms at incunabulum.net
Wed Jul 8 07:54:21 PDT 2009
Ben Greear wrote:
> I'm doing some testing with OLSR (plus my hacks to make it work with
> multiple router tables and multiple instances of xorp).
>
> I thought it was working previously, but I wasn't paying close enough
> attention. It is adding routes to individual interfaces, but no subnet routes,
> so traffic won't actually flow across my network.
>
Off the top of my head, this would be by design -- OLSR doesn't add
subnet routes for interfaces, as it's a peer-to-peer protocol -- unless
you explicitly configured an HNA advertisement somewhere. It doesn't do
any kind of auto summaries or anything like that. It's been a while
since I wrote that code, though.
Are you sure the regression tests continue to run OK with your changes?
Some of them are quite detailed and incomplete (it can be difficult to
make sure the timings are right, and the OLSR tests would often fail on
slow or old machines due to timer aliasing). But HNA should get tested
in there.
The only thing that multiple interfaces would turn on in the protocol is
MID. Subnet routes never appear in OLSR unless explicitly advertised in
HNA messages.
cheers
BMS
> A diagram of my network is at:
> http://www.candelatech.com/oss/olsr_diag.pdf
>
> The routes for router 3 are:
>
> 10.2.2.2 via 10.2.3.2 dev 2.3.3 proto xorp metric 5 notify
> 10.1.2.2 via 10.2.3.2 dev 2.3.3 proto xorp metric 5 notify
> 10.1.2.1 via 10.1.3.1 dev 1.3.3 proto xorp metric 5 notify
> 10.2.3.2 via 10.2.3.2 dev 2.3.3 proto xorp metric 5 notify
> 10.1.3.1 via 10.1.3.1 dev 1.3.3 proto xorp metric 5 notify
> 10.1.1.1 via 10.1.3.1 dev 1.3.3 proto xorp metric 5 notify
> 10.2.3.0/24 dev 2.3.3 scope link
> 10.1.3.0/24 dev 1.3.3 scope link
> 10.3.3.0/24 dev br3 scope link
> unreachable default proto xorp metric 1 notify
> fe80::/64 dev 2.3.3 metric 1024 mtu 1500 advmss 1440 hoplimit 4294967295
> unreachable default dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
>
>
> I was assuming that OLSR would be sharing subnet routes for the subnets directly connected
> to remote OLSR routers, and not just the interface IP routes.
>
>
> My config for router 3 is below. Others are similar:
>
> root at nehalem# show
> protocols {
> olsr4 {
> main-address: 10.3.3.3
> interface br3 {
> vif br3 {
> address 10.3.3.3 {
> }
> }
> }
> interface "1.3.3" {
> vif "1.3.3" {
> address 10.1.3.3 {
> interface-cost: 2
> }
> }
> }
> interface "2.3.3" {
> vif "2.3.3" {
> address 10.2.3.3 {
> interface-cost: 2
> }
> }
> }
> }
> static {
> interface-route 0.0.0.0/0 {
> next-hop-interface: "my_discard"
> next-hop-vif: "my_discard"
> }
> }
> }
> fea {
> unicast-forwarding4 {
> table-id: 10003
> }
> }
> interfaces {
> interface "my_discard" {
> unreachable: true
> vif "my_discard" {
> }
> }
> interface br3 {
> vif br3 {
> address 10.3.3.3 {
> prefix-length: 24
> }
> }
> }
> interface "1.3.3" {
> vif "1.3.3" {
> address 10.1.3.3 {
> prefix-length: 24
> }
> }
> }
> interface "2.3.3" {
> vif "2.3.3" {
> address 10.2.3.3 {
> prefix-length: 24
> }
> }
> }
> }
>
> Thanks,
> Ben
>
>
More information about the Xorp-hackers
mailing list