[rbak-nsp] Source based routing on SE100

Pawel Jarosz pj at hostersi.pl
Wed May 18 13:22:06 EDT 2011


On Wed, 18 May 2011, Ian Calderbank wrote:

> Pawel,
Ian,

> Its not clear to me what you are asking / trying to do, the explanation
> seems a little confused?
>
> If you are asking, whats the equivalent of cisco PBR (make forwarding
> decision based on source IP or other arbitrary criteria), its "forwarding
> policy" applied to circuit, which it seems you are already trying using.
Exactly.

> You can apply forwarding policy by radius attribute per-subscriber, if
> that's more scalable for you.
Static is for now, I try to get it work.

> Most scalable design is to bind the subscriber to the right context in the
> first place. Why are you binding all subs to context OSPF? Why not bind him
> to context A in the first place, then he automatically routes through
> context A?
topology is:
customer(subscriber)- (port) --OSPF --- (port) - ISP A (bgp)
                                     |-- (port) - ISP B (BGP)

> The subscriber static route that you see is expected behaviour given that
> you have defined that static subscriber and it is bound.
Maybe I get it wrong, and clips is not for
routed subscribers, only direct attached?
If so, the route is created as expected.

Pawel



More information about the redback-nsp mailing list