[rbak-nsp] Source based routing on SE100

[Giga Eth0]

I agree that a much cleaner solution is to map a subscriber to a context
directly. But for other cases (assuming non subscriber traffic), PBR is
possible. Here is a snippet for source based routing..

 policy access-list Source_based_routing
  seq 10 permit ip 192.168.1.0 0.0.255.255 any class ClassA
  seq 20 permit ip 192.168.2.0 0.0.255.255 any class ClassB
  seq 30 permit ip 192.168.3.0 0.0.255.255 any class ClassC

forward policy Source_based_redirect
 access-group Source_based_routing
  class ClassA
   redirect destination next-hop  10.0.0.1
class ClassB
   redirect destination next-hop 10.0.1.1
  class ClassC
   redirect destination next-hop 10.0.2.1

//cheers


On Thu, May 19, 2011 at 3:22 AM, Pawel Jarosz <pj at hostersi.pl> wrote:

> 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
>
> _______________________________________________
> 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/20110519/90af3aae/attachment.html>