Re: [j-nsp] merging IPv6 and IPv4 route in same policy

2008-12-29 Thread a. rahman isnaini rst / netsoft
lhady [mailto:ahmad.alh...@yahoo.com] Sent: Sunday, December 28, 2008 10:23 PM To: Masood Ahmad Shah; juniper-nsp@puck.nether.net Subject: Re: [j-nsp] merging IPv6 and IPv4 route in same policy but in 2 different terms !!! not in same term !? I was asking about same term ?! Thanks _

Re: [j-nsp] merging IPv6 and IPv4 route in same policy

2008-12-28 Thread Ahmad Alhady
@puck.nether.net Subject: [j-nsp] merging IPv6 and IPv4 route in same policy can we merge matching IPv6 and IPv4 routes in same config ??? for example policy-statement O-R { term 1 { from { protocol ospf; route-filter 10.0.6.0/24 orlonger; route-filter fec0:0

Re: [j-nsp] merging IPv6 and IPv4 route in same policy

2008-12-28 Thread Tommy Perniciaro
Multiple terms is fine, you get the result you want, right? - Original Message - From: juniper-nsp-boun...@puck.nether.net To: 'Ahmad Alhady' ; juniper-nsp@puck.nether.net Sent: Sun Dec 28 10:27:50 2008 Subject: Re: [j-nsp] merging IPv6 and IPv4 route in same policy What&

Re: [j-nsp] merging IPv6 and IPv4 route in same policy

2008-12-28 Thread Masood Ahmad Shah
What's wrong in using two terms J Regards, Masood From: Ahmad Alhady [mailto:ahmad.alh...@yahoo.com] Sent: Sunday, December 28, 2008 10:23 PM To: Masood Ahmad Shah; juniper-nsp@puck.nether.net Subject: Re: [j-nsp] merging IPv6 and IPv4 route in same policy but in 2 different

Re: [j-nsp] merging IPv6 and IPv4 route in same policy

2008-12-28 Thread Masood Ahmad Shah
Subject: [j-nsp] merging IPv6 and IPv4 route in same policy can we merge matching IPv6 and IPv4 routes in same config ??? for example policy-statement O-R { term 1 { from { protocol ospf; route-filter 10.0.6.0/24 orlonger; route-filter fec0:0:0:4

[j-nsp] merging IPv6 and IPv4 route in same policy

2008-12-28 Thread Ahmad Alhady
can we merge matching IPv6 and IPv4 routes in same config ??? for example policy-statement O-R { term 1 { from { protocol ospf; route-filter 10.0.6.0/24 orlonger; route-filter fec0:0:0:4::/64 orlonger; } then accept; }