3

I have a scenario where i am capturing data where mutiple customers vrfs traverse

I am looking at my capture and ofcourse i see source & destination

However, these addresses could come from mutiple customers

e.g. 10.10.10.0/24 could belong to customer A or customer B

When capturing raw data from a link, is it even possible to find a vrf value, or a route-target ?

I know i can see route-targets / distingushers within BGP updates, but that not what i am looking for

Any ideas welcome

5

When capturing raw data from a link, is it even possible to find a vrf value, or a route-target ?

A VRF is meaningful only to a router, so once the data leaves the router the question becomes meaningless.

Route targets are attributes of routing information, not data. MPLS packets don’t contain that information.

You can capture the MPLS labels and determine which VPN the packet belongs to.

1
  • Thanks, agreed, the MPLS label was/is the only unique attribute that was within the capture that could be used to identify the VPN.
    – psniffer
    Oct 23 at 12:23

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.