Re: [j-nsp] L3VPNs and on-prem DDoS scrubbing architecture
Saku Ytti via juniper-nsp <[email protected]> Wed, 3 Apr 2024 09:45:54 +0300
| Newsgroups | gmane.network.nsp.juniper |
|---|---|
| Message-ID | <CAAeewD9MVhiajb+AHfGQFfvKmH7rNU9BCuHZ+RP+rCmWUbKkug@mail.gmail.com> |
On Wed, 3 Apr 2024 at 09:37, Mark Tinka via juniper-nsp <[email protected]> wrote: > At old job, we managed to do this with a virtual-router VRF that carried > traffic between the scrubbing PE and the egress PE via MPLS, to avoid > the IP loop. Actually I think I'm confused. I think it will just work. Because even as the EgressPE does IP lookup due to table-label, the IP lookup still points to egressMAC, instead looping back, because it's doing it in the CleanVRF. So I think it just works. So OP just needs to copy the direct route as-is, not as host/32 into cleanVRF, with something like this: routing-options { interface-routes { rib-groups { cleanVRF { import-rib [ inet.0 cleanVRF.inet.0 ]; import-policy cleanVRF:EXPORT; }}}} Now cleanVRF.inet.0 has the connected TableLabel, and as lookup is done in the cleanVRF, without the Scrubber/32 route, it'll be sent to the correct egress CE, despite doing egress IP lookup. -- ++ytti _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp