:) May be simplicity of configuration is one of the purpose.
For me two terms are fine, it gives more flexibility in the future/soon
in case.
a. rahman isnaini rangkayo sutan.
Masood Ahmad Shah wrote:
What's wrong in using two terms J
Regards,
Masood
From: Ahmad Alhady [mailto:[email protected]]
Sent: Sunday, December 28, 2008 10:23 PM
To: Masood Ahmad Shah; [email protected]
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
_____
From: Masood Ahmad Shah <[email protected]>
To: Ahmad Alhady <[email protected]>; [email protected]
Sent: Sunday, December 28, 2008 8:14:11 PM
Subject: RE: [j-nsp] merging IPv6 and IPv4 route in same policy
The following configuration should work for IPv6/IPv4 in same policy.
policy-statement O-R {
term 1 {
from {
protocol ospf;
route-filter fec0:0:0:4::/64 orlonger;
}
then accept;
}
term 2 {
from {
protocol ospf;
route-filter 10.0.6.0/24 orlonger;
}
then accept;
}
Regards,
Masood
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Ahmad Alhady
Sent: Sunday, December 28, 2008 9:52 PM
To: [email protected]
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::/64 orlonger;
}
then accept;
}
he is giving me this message!!!!!
Policy: invalid prefix fec0:0:0:4::/64 for family inet
error: configuration check-out failed
Ahmad
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp