[rbak-nsp] Inter context routing with OSPF?

[Frans Legdeur]

Hi Thomas,

As far as I know, this inter context routing is supported with IS-IS.
The interface between the contexts can be defined as p2p or as broadcast
segment, so /24 instead of /30, where each context would get it¹s own IP
address.
I would try to go with the broadcast option and define OSPF in broadcast
mode, however, this is pure theoretical.

So far I have seen working implementations based on IS-IS between the
contexts.

Kind regards,


Frans.




From: "Voigt, Thomas" <Thomas.Voigt at netkom.de>
Date: Fri, 26 Mar 2010 09:41:16 +0100
To: "redback-nsp at puck.nether.net" <redback-nsp at puck.nether.net>
Subject: [rbak-nsp] Inter context routing with OSPF?

Hi all,
 
I'm trying to configure some intercontext routing with OSPF having the
following config:
 
########################################
context local
 
 interface bla intercontext p2p 1
  ip address 10.0.0.1/30
 
 router ospf 6714
  fast-convergence
  router-id 10.0.0.1
  area 0.0.0.0
   interface bla
    neighbor 10.0.0.2
  redistribute static
 
 ip route 10.0.0.2/32 context test
 
 
context test
 
 interface bla intercontext p2p 1
  ip address 10.0.0.2/30
!
 router ospf 6714
  fast-convergence
  area 0.0.0.0
   interface bla
    neighbor 10.0.0.1
  redistribute static
!
 ip route 10.0.0.1/32 context local
########################################
 
I can ping each other interface bla from each context. In context test is
only this one ip address existing. So I think there's no need to configure
router-id there.
But the two OSPF processes don't exchange updates.
 
Am I missing something?
 
 
-- 
Kind regards
 
Thomas Voigt 
 
 


_______________________________________________
redback-nsp mailing list
redback-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20100326/4e3cb21e/attachment.html>