[j-nsp] ACX control plane filter

[Saku Ytti]

You probably don't want to protect customer LANs same way as you want
to protect your control-plane.

On 22 March 2017 at 20:12, Eduardo Schoedler <listas at esds.com.br> wrote:
> Better example:
>
> {master}[edit]
> jnpr at R1-RE0# *show policy-options prefix-list router-ipv4*
> apply-path "interfaces <*> unit <*> family inet address <*>";
>
> {master}[edit]
> jnpr at R1-RE0# *show policy-options prefix-list router-ipv4 | display inheritance*
> ##
> ## apply-path was expanded to:
> ##     192.168.0.0/30;
> ##     10.8.0.0/31;
> ##     192.0.2.0/26;
> ##     192.0.2.64/26;
> ##     10.3.255.1/32;
> ##     172.19.90.0/23;
> ##
> apply-path "interfaces <*> unit <*> family inet address <*>";
>
>
>
>
> Em qua, 22 de mar de 2017 às 15:00, Eduardo Schoedler <listas at esds.com.br>
> escreveu:
>
>> have you tried to do a prefix-list like this?
>>
>>
>> {master}[edit]
>> regress at R1-RE0# *show policy-options | no-more*
>> prefix-list router-ipv4 {
>>     apply-path "interfaces <*> unit <*> family inet address <*>";
>> }
>>
>>
>> --
>> Eduardo Schoedler
>>
>>
>> Em seg, 20 de mar de 2017 às 06:24, Johan Borch <johan.borch at gmail.com>
>> escreveu:
>>
>> Hi
>>
>> Do anyone have a control plane filter for ACX they can share? :) they don't
>> seem to support using standard loopback filters.
>>
>> Johan
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>> --
>> Eduardo Schoedler
>>
> --
> Eduardo Schoedler
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp



-- 
  ++ytti