Filtering traffic based on associated forwarding equivalence classes

• US 7,889,711 B1
• Filed: 07/29/2005
• Issued: 02/15/2011
• Est. Priority Date: 07/29/2005
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Washburn, James, Aggarwal, Shivani, Minei, Ina
• Primary Examiner(s): Yao; Kwang B
• Assistant Examiner(s): LOO, JUVENA W
• Application Number:
  US11/192,747
• Time in Patent Office: 2,027 Days
• Field of Search: 370/351, 370354-356, 370380-390
• US Class Current: 370/351
• CPC Class Codes: H04L 45/30 Routing of multiclass traffic
• CPC Class Codes: H04L 45/38 Flow based routing
• CPC Class Codes: H04L 45/507 Label distribution

Abstract

Filters are selectively applied to packets depending on forwarding equivalence classes (FECs) of the packets. A FEC filter is defined within the network device and qualified by incoming interface information that identifies source sites of the packets. A label distribution protocol (LDP) FEC is configured such that packets of the given FEC are associated with the FEC filter. The FEC identifies a destination site of the packets received by the router and is automatically combined with incoming interface information. In this way, packet flows may be filtered based on FECs of the packets. FEC filters may be further refined to operate at forwarding class granularity. The techniques allow accurate billing of packets traveling between specific source and destination sites regardless of the number of interfaces of the network device the packets utilize. In addition, the filtering can be used to provide anti-spoofing capabilities.

Claims

1. A method comprising:

receiving, with a routing engine of a network device, configuration data defining a forwarding equivalence class (FEC) filter that associates a label distribution protocol (LDP) FEC with one or more actions, wherein the network device is positioned between an ingress network device and an egress network device for a label switched path (LSP);

installing, with the routing engine of the network device, the FEC filter within forwarding information of a packet forwarding engine of the network device so as to associate the FEC filter with a next hop of the forwarding information corresponding to the LDP FEC;

receiving, with the packet forwarding engine of the network device positioned between the ingress network device and the egress network device for the LSP, a multi-protocol label switching (MPLS) data packet having an MPLS label that corresponds to the LSP in accordance with a label distribution protocol (LDP);

examining, with the packet forwarding engine of the network device, the forwarding information to select a next hop for the packet based on the MPLS label of the received MPLS packet;

determining, with the packet forwarding engine, an MPLS label associated with the selected next hop to be used in place of the MPLS label of the received MPLS data packet when forwarding the MPLS packet to the selected next hop; and

selectively applying, with the packet forwarding engine of the network device, the FEC filter to the MPLS data packet when the selected next hop for the MPLS data packet is associated with the FEC filter by the forwarding information to perform the one or more actions of the FEC filter, wherein selectively applying the FEC filter includes applying the FEC filter before forwarding the MPLS data packet to the selected next hop.

2. The method of claim 1, wherein the configuration data further qualifies the FEC filter with incoming interface information that identifies a source interface,

wherein selectively applying a FEC filter comprises selectively applying the FEC filter to the data packet when an incoming interface on which the data packet is received matches the source interface identified in the FEC filter.

3. The method of claim 2, wherein the actions include at least one of updating customer account information, counting data packets, marking data packets, or discarding data packets.

4. The method of claim 2, wherein the configuration data qualifies the FEC filter by defining the FEC filter based on an interface identifier that allows configuration of one or more incoming interfaces as a match condition of the FEC filter.

5. The method of claim 1, further comprising configuring the LDP FEC to associate the FEC filter with data packets of the LDP FEC.

6. The method of claim 5, wherein the FEC filter is associated with transit traffic of the LDP FEC that transitions from the ingress network device though the network device to the egress network device.

7. The method of claim 1, further comprising mapping FEC filter names to FEC filter indices in a FEC filter table.

8. The method of claim 1, further comprising selecting the next hop for the received data packet according to the LDP FEC of the data packet.

9. The method of claim 1, wherein the network device comprises a router.

10. The method of claim 9, wherein installing the FEC filter comprises forwarding a next hop message from the routing engine to the packet forwarding engine to specify the next hop and an index of the FEC filter to install the FEC filter within the packet forwarding engine.

11. The method of claim 10, further comprising inserting the FEC filter and the next hop in a forwarding path of the packet forwarding engine.

12. The method of claim 1, wherein selectively applying the FEC filter comprises applying the FEC filter to the data packet when the data packet belongs to the LDP FEC and when the data packet is received from a source identified in the FEC filter.

13. The method of claim 12, wherein selectively applying the FEC filter further comprises applying the FEC filter to the data packet when the data packet matches one or more characteristics identified in the FEC filter.

14. The method of claim 1, wherein selectively applying the FEC filter comprises forwarding the data packet directly to a next hop without application of the FEC filter when the next hop selected for the data packet is not associated with the FEC filter or when the data packet belongs to the LDP FEC and is received from a source that is not identified in the FEC filter.

15. The method of claim 1, further comprising receiving statistics from the FEC filter.

16. The method of claim 15, wherein the statistics includes at least one of data packet counts, data byte counts, marked data packet counts, or dropped data packet counts.

17. The method of claim 1, wherein the data packet travels across a multi-protocol label switching (MPLS) path.

18. The method of claim 1, wherein the data packet travels across a virtual private LAN service (VPLS) path.

19. The method of claim 1,

wherein the network device is a router;

and

wherein selectively applying the FEC filter comprises taking the one or more actions with respect to the packet within a forwarding path of the packet forwarding engine of the router.

20. The method of claim 19, wherein taking an action comprises one or more of:

dropping the packet,

counting the packet in order to maintain traffic statistics,

marking the packet with a loss or gain in priority,

updating billing or account information, or

changing the forwarding class of the packet.

40. The method of claim 1, further comprising identifying a destination of the data packet, wherein the destination is the same as the LDP FEC, and

wherein examining the forwarding information comprises examining the forwarding information based on the identified destination to select the next hop for the packet.

21. A network device comprising:

a packet forwarding engine that includes forwarding information defining a next hop for a label distribution protocol (LDP) forwarding equivalence class (FEC); and

a routing engine that receives configuration data defining a FEC filter that associates the LDP FEC with one or more actions and installs the FEC filter within the forwarding information so as to associate the FEC filter with the next hop of the forwarding information corresponding to the LDP FEC,

wherein the network device is positioned between an ingress network device and an egress network device for a label switched path (LSP), and

wherein the packet forwarding engine further receives a multi-protocol label switching (MPLS) data packet having an MPLS label that corresponds to the LSP in accordance with a label distribution protocol (LDP), examines the forwarding information to select a next hop for the data packet based on the MPLS label of the received MPLS packet, determines an MPLS label associated with the selected next hop to be used in place of the MPLS label of the received MPLS data packet when forwarding the MPLS packet to the selected next hop, and selectively applies the FEC filter to the MPLS data packet when the selected next hop for the MPLS data packet is associated with the FEC filter by the forwarding information to perform the one or more actions of the FEC filter,

wherein the packet forwarding engine applies the FEC filter before forwarding the MPLS data packet to the selected next hop.

22. The network device of claim 21,

wherein the packet forwarding engine further identifies a destination of the data packet,

wherein the destination is the same as the LDP FEC, and

wherein the packet forwarding engine further examines the forwarding information based on the identified destination to select the next hop.

23. The network device of claim 21,

wherein the configuration data further qualifies the FEC filter with incoming interface information that identifies a source interface, and

wherein the packet forwarding engine selectively applies the FEC filter when an incoming interface on which the data packet is received matches the source interface identified in the FEC filter.

24. The network device of claim 21, wherein the LDP FEC is configured to associate the FEC filter with data packets of the LDP FEC.

25. The network device of claim 21, further comprising routing information that correlates the FEC filter with a next hop of the LDP FEC.

26. The network device of claim 21, further comprising a FEC filter table that maps FEC filter names to FEC filter indices.

27. The network device of claim 21, wherein the packet forwarding engine receives a next hop message from the routing engine to specify the next hop and an index of the FEC filter to install the FEC filter within the packet forwarding engine.

28. The network device of claim 27, wherein the packet forwarding engine inserts the FEC filter and the next hop in a forwarding path of the packet forwarding engine.

29. The network device of claim 21, wherein the packet forwarding engine generates statistics in response to selectively applying the FEC filter.

30. The network device of claim 29, wherein the statistics includes at least one of data packet counts, data byte counts, marked data packet counts, or dropped data packet counts.

31. The network device of claim 21, wherein the data packet travels across a multi-protocol label switching (MPLS) path.

32. The network device of claim 21, wherein the data packet travels across a virtual private LAN service (VPLS) path.

33. A non-transitory computer-readable medium comprising instructions that cause a programmable processor to:

receive, with a routing engine of a network device, configuration data defining forwarding equivalence class (FEC) filter that associates a label distribution protocol (LDP) FEC with one or more actions, wherein the network device is positioned between an ingress network device and an egress network device for a label switched path (LSP);

install, with the routing engine of the network device, the FEC filter within forwarding information of a packet forwarding engine of the network device so as to associate the FEC filter with a next hop of the forwarding information corresponding to the LDP FEC;

receive, with the packet forwarding engine of the network device positioned between the ingress network device and the egress network device for the LSP, a multi-protocol label switching (MPLS) data packet having an MPLS label that corresponds to the LSP in accordance with a label distribution protocol (LDP);

examine, with the packet forwarding engine of the network device, the forwarding information to select a next hop for the packet based on the MPLS label of the received MPLS packet;

determine, with the packet forwarding engine, an MPLS label associated with the selected next hop to be used in place of the MPLS label of the received MPLS data packet when forwarding the MPLS packet to the selected next hop; and

selectively apply, with the packet forwarding engine of the network device, the FEC filter to the MPLS data packet when the selected next hop for the MPLS data packet is associated with the FEC filter by the forwarding information to perform the one or more actions of the FEC filter, wherein, to selectively apply the FEC filter, the instructions cause the processor to apply the FEC filter before forwarding the MPLS data packet to the selected next hop.

34. The non-transitory computer-readable medium of claim 33, wherein the configuration data further qualifies the FEC filter with incoming interface information that identifies a source interface.

35. The non-transitory computer-readable medium of claim 33, further comprising instructions that cause the programmable processor to configure the LDP FEC to associate the FEC filter with data packets of the LDP FEC.

36. The non-transitory computer-readable medium of claim 33, wherein the instructions further cause the programmable processor to select a next hop for the received data packet according to a destination of the data packet.

37. The non-transitory computer-readable medium of claim 33, wherein the network device comprises a router.

38. The non-transitory computer-readable medium of claim 37, further comprising instructions that cause the programmable processor to forward a next hop message from the routing engine to the packet forwarding engine to specify the next hop and an index of the FEC filter to install the FEC filter within the packet forwarding engine.

39. The non-transitory computer-readable medium of claim 37, further comprising instructions that cause the programmable processor to insert the FEC filter and the next hop in a forwarding path of the packet forwarding engine.

41. A method comprising:

receiving, with a routing engine of a network device, configuration data defining a forwarding equivalence class (FEC) filter that associates a label distribution protocol (LDP) FEC with one or more actions, wherein the network device is positioned between an ingress network device and an egress network device for a label switched path (LSP) and wherein the one or more actions include at least one of updating customer account information, counting data packets, marking data packets, or discarding data packets;

installing, with the routing engine of the network device, the FEC filter within forwarding information of a packet forwarding engine of the network device so as to associate the FEC filter with a next hop of the forwarding information corresponding to the LDP FEC;

receiving, with the packet forwarding engine of the network device positioned between the ingress network device and the egress network device for the LSP, a multi-protocol label switching (MPLS) data packet having an MPLS label that corresponds to the LSP in accordance with a label distribution protocol (LDP);

examining, with the packet forwarding engine of the network device, the forwarding information to select a next hop for the MPLS data packet based on the MPLS label of the received MPLS data packet;

determining, with the packet forwarding engine, an MPLS label associated with the selected next hop to be used in place of the MPLS label of the received MPLS data packet when forwarding the MPLS packet to the selected next hop;

applying, with the packet forwarding engine of the network device, the FEC filter to the MPLS data packet when the selected next hop for the MPLS data packet is associated with the FEC filter to perform the one or more actions of the FEC filter; and

after applying the FEC filter to the MPLS data packet, forwarding the MPLS data packet to the selected next hop using the determined MPLS label.

42. A method comprising:

receiving, with a routing engine of a network device, configuration data defining a forwarding equivalence class (FEC) filter that associates a label distribution protocol (LDP) FEC with one or more actions, wherein the network device is positioned between an ingress network device and an egress network device for a label switched path (LSP), and wherein the one or more actions include at least one of updating customer account information, counting data packets, marking data packets, or discarding data packets;

installing, with the routing engine of the network device, the FEC filter into routing information of the routing engine in a manner that correlates the FEC filter with a next hop of the LSP associated with the FEC;

installing, with the routing engine of the network device, the FEC filter within forwarding information of a packet forwarding engine of the network device in a manner that associates the FEC filter with an MPLS label corresponding to the next hop of the LSP associated with the FEC;

receiving, with the packet forwarding engine of the network device positioned between the ingress network device and the egress network device for the LSP, a multi-protocol label switching (MPLS) data packet having an MPLS label that corresponds to the LSP in accordance with a label distribution protocol (LDP);

examining, with the packet forwarding engine of the network device, the forwarding information to select the label corresponding the next hop for the packet based on the MPLS label of the received MPLS packet, wherein the label is to be used by the packet forwarding engine in place of the MPLS label of the received MPLS data packet when forwarding the MPLS packet to the selected next hop; and

applying, with the packet forwarding engine of the network device, the FEC filter to the MPLS data packet when the selected next hop for the MPLS data packet is associated with the FEC filter by the forwarding information to perform the one or more actions of the FEC filter.