US 7,546,635 B1Grant
Stateful firewall protection for control plane traffic within a network device
Issue Date:2009-06-09
•49 Claims
•6 Drawing Sheets
Abstract
A network device receives control plane packets and data plane packets from a network. The network device includes a forwarding component that forwards the data plane packets in accordance with routing information maintained by a routing component. The forwarding component directs the control plane packets to a firewall component that processes the control plane packets to apply firewall services and detect network attacks. After processing, the firewall component loops the control plane packets back to the forwarding components for forwarding to the routing component. The firewall component may be a security service card.
Metadata
Assignee
- Juniper Networks, Inc.
Inventors
- Robert M. Krohn
- Sankar Ramamoorthi
- Michael Freed
- Keith Holleman
Application Information
Application Number:US 10/916,021
Filing Date:2004-08-11
Priority Date:2004-08-11
Art Unit:2439
Classifications
IPC:
G06F9/00
Patent Drawings (6 sheets)
Description
Technical Field
[0001] The invention relates to computer networks and, more particularly, to techniques for protecting devices within networks.
Background
[0002] A computer network is a collection of interconnected computing devices that exchange data and share resources. In a packet-based network, such as the Internet, the computing devices communicate data by dividing the data into small blocks called packets. The packets are individually routed across the network from a source device to a destination device. The destination device extracts the data from the packets and assembles the data into its original form. Dividing the data into packets enables the source device to resend only those individual packets that may be lost during transmission.
[0003] Certain devices, referred to as routers, maintain routing information that describes routes through the network. A “route” can generally be defined as a path between two locations on the network. Conventional routers often maintain the routing information in the form of one or more routing tables or other data structures. The form and content of the routing tables often depend on the particular routing algorithm implemented by the router.
[0004] Upon receiving incoming packets, the routers examine information within the packets, and forward the packets to other devices within the network in accordance with the routing information. In order to maintain an accurate representation of the network, routers exchange routing information in accordance with routing protocols, such as the Border Gateway Protocol (BGP), the Intermediate System to Intermediate System (ISIS) protocol, the Open Shortest Path First (OSPF) protocol, and the Routing Information Protocol (RIP).
[0005] When two routers initially connect, they typically exchange routing information. From then on, the routers send control messages to incrementally update the routing information when the network topology changes. For example, the routers may send update messages to advertise newly available routes, and to withdraw routes that are no longer available. The control messages communicated between network devices, such as routers, is often referred to “control plane” network traffic. In contrast, the network traffic received and forwarded by a router is often referred to as “data plane” network traffic.
[0006] A network device, such as a router, server, workstation, or other device, can be susceptible to a network attack. A denial of service (DoS) attack, for example, occurs when a malicious party directs a high volume of packets to the network device in an attempt to sabotage network operation. The high volume of traffic can overwhelm the network device, leaving it unable to process other packets. For example, in one type of DoS attack, a perpetrator sends a large number of “ping” requests to network broadcast addresses, which are special addresses used to broadcast messages to other devices on the network. When sending the requests, the perpetrator spoofs the source address of a network device targeted by the attack. In response to the requests, the other network devices reply to the targeted routing device, thereby inundating the targeted routing device with packets.
[0007] One technique for preventing or otherwise reducing the effects of attacks on devices within a network is to introduce a “firewall.” The firewall is often a dedicated device that provides stateful analysis (i.e., inter-packet analysis) of the network traffic, and is typically placed between the network and a router coupled to an external network, i.e., “behind” the router. Placing the firewall behind the router protects devices within the network, but leaves the router exposed to external network attacks.
[0008] Another technique is to place the firewall between the router and the external network, such as a service provide network. This technique, however, may adversely impact the bandwidth available to receive traffic from the external network as the firewall is typically unable to match the level of bandwidth supported by the router.
Summary
[0009] In general, the invention is directed to techniques for providing firewall protection to control plane traffic of a network device. For example, a network device, such as a router, identifies control plane traffic for the network device, and selectively applies firewall analysis to the control plane traffic without impeding the processing of data plane traffic. In other words, firewall protection is provided for the control plane packets destined for the network device. However, other network traffic forwarded by the device, i.e., data plane traffic, need not be similarly analyzed.
[0010] In one embodiment, a method comprises receiving control plane packets and data plane packets with a network device, and forwarding the control plane packets to a firewall component within the network device. The method further comprises processing the control plane packets with the firewall component to detect a network attack.
[0011] In another embodiment, a method comprises receiving control plane packets and data plane packets with a control unit of a router, wherein the control unit includes a forwarding component and a routing component. The method further comprises forwarding the data plane packets to an output interface with the forwarding component, processing the control plane packets with a firewall component, and forwarding the control plane packets to the routing component after processing.
[0012] In another embodiment, a network device comprises a physical interface card that receives control plane packets and data plane packets from a network, a firewall component that processes the control plane packets to detect a network attack, and a forwarding component that directs the control plane packets to the firewall component.
[0013] In another embodiment, the invention is directed to a computer-readable medium containing instructions. The instructions cause a programmable processor to receive control plane packets and data plane packets within a router, forward the data plane packets to an output interface in accordance with routing information, and forward the control plane packets to a routing component after the control plane packets are process with a firewall component within the router.
[0014] Embodiments of the invention may provide one or more advantages. For example, the techniques provide a simple and effect security treatment of control plane traffic for a network device, such as a router. As only control plane traffic is identified and analyzed, e.g., via a firewall service card, data plane traffic may be relatively unaffected. For example, customer traffic handled by the network device may not necessarily experience bandwidth degradation even though stateful firewall analysis is performed on the control plane traffic. In this manner, the firewall protection for the network device may be relatively transparent to data plane traffic handled by the network device.
[0015] Moreover, the techniques may be utilized to provide “stateful” firewall services on the control place traffic. As used herein, the term “stateful” firewall services refers to firewall services that provide inter-packet analysis, i.e., services that generate and maintain state information between control plane packets. The techniques may allow even high-bandwidth routing device to apply stateful firewall protection of the routing device without substantially affecting data plane traffic.
[0016] The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, objects, and advantages of the invention will be apparent from the description and drawings, and from the claims.
Brief Description of Drawings
[0017] FIG. 1 is a block diagram illustrating an example system in which a provider edge (PE) router provides firewall services for control plane traffic.
[0018] FIG. 2 is a block diagram illustrating an exemplary router that provides firewall services for control plane traffic in accordance with the principles of the invention.
[0019] FIG. 3 is a block diagram of an example embodiment of a security service card that provides firewall services for a network device.
[0020] FIG. 4 is a flowchart illustrating exemplary operation of a network device in accordance with the principles of the invention.
[0021] FIG. 5 is a schematic diagram illustrating an exemplary embodiment of a network router that provides stateful firewall services to control plane packets.
Detailed Description
[0022] FIG. 1 is a block diagram illustrating an example system 10 in which a provider edge (PE) router 12 provides firewall services to control plane traffic. The term “control plane traffic,” as used herein, refers to network packets that are destined to a “control plane” of PE router 12. A routing protocol communication, such as a packet that conforms to the Border Gateway Protocol (BGP), is one example of control plane traffic.
[0023] In the illustrated example of FIG. 1 , PE router 12 is an edge router of a service provider network 14 administered by a network service provider, and provides connectivity for customer networks 16A and 16B (collectively, “customer networks 16”). In particular, PE router 12 is coupled to customer edge routers 18A and 18B (collectively, “customer edge routers 18”) of customer networks 16 via access links 20A and 20B, respectively. Each of customer networks 16 may be a network for a site of an enterprise. Each of customer networks 16 may include one or more computing devices (not shown), such as personal computers, laptop computers, handheld computers, workstations, servers, switches, printers, or other devices.
[0024] Service provider network 14 may be coupled to one or more networks administered by other service providers, and may thus form part of a large-scale public network infrastructure, e.g., the Internet. The service provider may provide computing devices within customer networks 16 with access to the Internet via service provider network 14, which allows computing devices within one of customer sites 16 to communicate with computing devices within the Internet or the other one of customer networks 16. Service provider network 14 may include a variety of other network devices (not shown), such as routers, switches, servers, and the like and may be connected to other networks.
[0025] The configuration of the network environment illustrated in FIG. 1 is merely exemplary. For example, service provider network 14 may include any number of provider edge routers coupled to one or more customer networks. Nonetheless, for ease of description, only a single PE router 12 coupled to customer networks 16 is illustrated in FIG. 1 .
[0026] In accordance with the principles of the invention, PE router 12 provides firewall services to control plane traffic. Moreover, in some embodiments, PE router 12 may apply the firewall services only to the control plane traffic without affecting data plane traffic, i.e., traffic that is forwarded through PE router 12 to other computing devices. As described in further detail herein, PE router 12 identifies a packet destined for the control plane of the router, such as a routing protocol communication, and applies one or more firewall services to the identified control plane packet. If PE router 12 identifies a packet as data plane traffic, PE router 12 may forward the packet from an input interface to an output interface without applying the control plane firewall services, but may apply data plane firewall services.
[0027] In some embodiments of the invention, PE router 12 provides “stateful” firewall services to the control plane traffic in order to protect the router from security issues, such as an attack, without substantially affecting the performance of the router. As used herein, the term “stateful” firewall services refers to firewall services that provide inter-packet analysis, i.e., services that generate and maintain state information between control plane packets. Prior to processing the control plane traffic with a control plane, e.g., a routing component, PE router 12 may apply firewall services to detect a security issue, such as a network attack or other security anomalies. PE router 12 may apply, for example, one or more filters, application specific gateways (ADGs) to perform application-specific checks, anomaly detection modules, trend analysis modules, or other security services.
[0028] The control plane traffic that is not rejected by one of the security services is forwarded to the control plane of PE router 12. In addition, feedback information obtained from the analysis of the control plane traffic may also be communicated to the control plane, which may be used for dynamically updating filters or other security services to be applied by the PE router 12. The control plane may, for example, dynamically create one or more interface-specific filters to reject attack traffic being received on one of the interfaces. In this manner, the techniques of the invention may be used to detect and thwart attacks on PE router 12 without substantially affecting performance of the router, e.g., the router's forwarding capability for valid data and control plane traffic.
[0029] In one embodiment, PE router 12 includes a service card (not shown in FIG. 1 ) that assists in the application of the security services to the control plane traffic. The service card may, for example, provide stateful analysis of the control plane traffic to detect any network attack or security anomaly pattern. The service card in turn may provide feedback information to the control plane for dynamic update of the security services applied by PE router 12.
[0030] Although the techniques of the invention have been primarily described with respect to PE router 12, embodiments of the invention are not limited in this regard. Other network devices, such as routers within the core of a network or customer edge routers 18, may perform the functions described herein.
[0031] FIG. 2 is a block diagram illustrating an exemplary router 30 that provides firewall services to control plane traffic in accordance with the principles of the invention. In this example, router 30 provides firewall services to the control plane traffic without affecting data plane traffic, i.e., traffic that is forwarded through router 30 to other devices. Router 30 may, for example, represent an embodiment of PE router 12 of FIG. 1 .
[0032] Router 30 includes a set of one or more interface cards 32A-32N (“IFCs 32”) for communicating packets via inbound links 34A-34N (collectively, “inbound links 34”) and outbound links 36A-36N (collectively, “outbound links 36”). IFCs 32 may be coupled to inbound links 34 and outbound links 36 via a number of interface ports (not show in FIG. 2 ). In addition, router 30 includes a service card 38 that may apply stateful firewall services to control plane traffic, as described in detail below, and may provide other services as well.
[0033] Router 30 further comprises a control unit 40 that may generally be divided into a data plane 42 and a control plane 44. In this example, control plane 44 may be viewed as a routing component of control unit 40, while data plane 42 may be viewed as a forwarding component of the control unit.
[0034] For example, control plane 44 maintains routing information 46, which describes the topology of a network and, in particular, routes through the network. Routing information 46 may include, for example, route data that describes various routes within the network, and corresponding next hop data indicating appropriate neighboring devices within the network for each of the routes. Router 30 updates routing information 46 to accurately reflect the topology of the network using a routing protocol, such as the Border Gateway Protocol (BGP).
[0035] In accordance with routing information 46, data plane 42 maintains one or more forwarding information tables 48A-48K (collectively, “forwarding information tables 48”) that associate network destinations with specific next hops and corresponding interface ports. Each of forwarding information tables 48 may be virtual forwarding instance associated with one or more specific customer networks. Control plane 44 generates forwarding information tables 48 in accordance with routing information 46. Although referred to as “tables” for purposes of illustration, forwarding information tables 48 may take the form of any of a number of data structures, such as databases, files, lists, arrays or other structures.
[0036] In general, data plane 42 forwards packets received from inbound links 34 to a corresponding next hop associated with destinations of the packets. When router 30 receives a packet via one of inbound links 34, for example, data plane 42 associates the packet with one of forwarding information tables 48. Data plane 42 then determines a destination and associated next hop for the packet in accordance with the associated one of forwarding tables 48. For a data plane packets, i.e., a packet destined for external devices, data plane 42 outputs the packet on an outbound link 36 based on the destination.
[0037] During this process, data plane 42 may apply one or more interface filters 52A-52L (collectively, “interface filters 52”). In general, interface filters 52 represent interface-specific filtering rules applied to packet flows. Interface filters 52 may, for example, discard packets when they contain specified information in its packet header or payload, perform policer functions by limiting the bandwidth of an interface, or perform checks on incoming packets. Data plane 42 may apply interface filters 52 upon receiving a packet on a particular one of interfaces 34, upon forwarding a packet to a particular one of outbound interfaces 36, or both. Interface filters 52 may further correspond to individual packet flows received from or forwarded to inbound interfaces 34 or outbound interfaces 36, respectively. In either case, interface filters 52 are typically applied on a packet-by-packet basis.
[0038] In the event data plane 42 determines that an inbound packet is destined for control plane 44, i.e., the packet is a “control plane packet,” stateful firewall services may be applied to the packet prior to forwarding at to control plane 44. In particular, data plane 42 assigns the control plane packet a specific loopback interface based on the one of inbound interfaces 34 on which the control plane packet was received. Consequently, data plane 42 may assign a different loopback interface for different forwarding information tables 48. In this manner, different loopback interfaces may be used for different customers, allowing customer-specific firewall services to be applied.
[0039] After assigning the appropriate loopback interface, data plane 42 forwards the control plane packet to the assigned loopback interface. As a result, data plane 42 applies loopback services 50, which represent security mechanisms, such as access control lists (ACLs), that may be applied on a packet-by-packet basis.
[0040] Upon applying loopback services 50, instead of forwarding the control plane packet to control plane 44, data plane 42 redirects the packet to a firewall component, e.g., service card 38, that applies stateful firewall services. In this exemplary embodiment, service card 38 represents a physical card that may be inserted within router 30 and electrically coupled to control unit 40. Upon receiving control plane packets from data plane 42, service card 38 may perform one or more stateful firewall services to detect a network attack or other security anomaly.
[0041] Again, in this context, the term “stateful” firewall services refers to firewall services that provide inter-packet analysis, i.e., services that generate and maintain state information between control plane packets. In other words, service card 38 generates and maintains state information as control plane packets are received from data plane 40 in order to provide the firewall services. Service card 38 may, for example, analyze the control plane packets and perform protocol verification, anomaly detection, trend detection, abnormal behavior detection, limit checks or other security services.
[0042] If a network attack or other security anomaly is detected, service card 38 may reject and/or log all or a portion of the control plane packets. Otherwise, service card 38 forwards the control plane packet back to data plane 42. Upon receiving the control plane packets, data plane 42 forwards the control plane packets to control plane 44.
[0043] Service card 38 may output feedback communications to control plane 44 based on the packet analysis. The feedback communication may specify a form of a detected network attack or security anomaly, and may include additional information, such as an one or more of input interfaces 34 and IFCs 32 associated with the attack, protocol information, source and destination port information, source network address information or other information.
[0044] Control plane 44 may use the feedback communication provided by service card 38 to update forwarding information tables 48 and update interface filters 52 to be applied by data plane 42. Control plane 44 may, for example, dynamically create one or more interface filters 52 to reject the attack traffic upon being received on one of input interfaces 34. Once a threat is removed or no longer detected, service card 38 may direct control plane 44 to remove the dynamic filters. In some embodiments, service card 38 may associated a time period with a filter, and may direct control plane 44 to remove the filter upon expiration of the time frame. In this manner, embodiments of the invention may be used to detect and thwart attacks on router 30 without substantially affecting performance of the router, e.g., the router's forwarding capability for transit data plane traffic.
[0045] The functions of router 30 may be implemented by executing the instructions of the computer-readable medium with one or more processors, discrete hardware circuitry, firmware, software executing on a programmable processor, or a combination of any of the above. Moreover, data plane 42 and control plane 44 may be functionally integrated or separately. For example, data plane 42 and control plane 44 may be integrated or implemented separately as a routing engine and a forwarding engine. As another example, the functionality described with respect to data plane 42 may be distributed within IFCs 32. Moreover, router 30 may operate according to executable instructions fetched from a computer-readable medium (not shown). Examples of such media include random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other media.
[0046] FIG. 3 is a block diagram of an example embodiment of a service card 50 that provides stateful firewall services for a network device in accordance with the principles of the invention. In the illustrated embodiment, service card 50 includes control plane packet interface 64 that receives control plane packets, e.g., from a data plane of a router or other network device in which the service card is installed. Control plane packet interface 64 buffers the control plane packets in memory for processing by packet analysis modules 51. Each of packet analysis modules 51 provides a security service, and may be implemented in software, hardware or combinations thereof. Moreover, although illustrated separately, packet analysis modules 51 may be implemented as functions, subroutines, software libraries, threads, processes or other modules, and may be readily combined.
[0047] Anomaly detection module 52 analyzes the control plane packets to detect any abnormal behavior, e.g., behavior that is inconsistent with routing or other network protocols. Trend analysis module 54 analyzes the control plane packets to detect trends that may reveal suspicious or malicious behavior. Limit check module 56 applies limit checks to the network protocols to ensure compliance. For example, limit check module 56 may operate in accordance with rules that limit the maximum number of sessions a user may open, e.g., 100 sessions. As another example, limit check module may perform trend analysis to ensure that a user does not open more than a defined number of sessions in a given interval, e.g, no more than ten sessions in a one second interval. Application level gateways 58 may also be used for protocol verification and compliance. Attack defense module 60 may be used to protect the host device in which security service card 50 is installed, e.g., a router, from network attacks. For example, attack defense module 60 may provide port scan protection, denial of service (DOS) protection, distributed DOS (DDOS) protection, TCP attack protection, SYN protection or other forms of protection using known defenses.
[0048] Packet analysis modules 51 generate and maintain state information 62 as the control plane packets are processed. Once processed, control plane packet interface 64 forwards the control plane packets, e.g., back to the originating data plane. If a security issue, such as a network attack or other security anomaly is detected, packet analysis modules 51 may direct control plane packet interface 64 to block all or a portion of the control plane packets.
[0049] Feedback interface 66 outputs feedback communications based on state information 62 generated by packet analysis modules 51. The feedback communications may specify a form of a detected network attack or security anomaly, and may include additional information, such as an one or more of input interfaces 34 and IFCs 32 associated with the attack, protocol information, source and destination port information, source network address information or other information.
[0050] The functions of service card 50 may be implemented by executing the instructions of the computer-readable medium with one or more processors, discrete hardware circuitry, firmware, software executing on a programmable processor, or a combination of any of the above. Service card 50 may, for example, include one or more processors, and may operate according to executable instructions fetched from a computer-readable medium (not shown). Examples of such media include random access memory (RAM), read-only memory (ROM), non-volatile random access memory (NVRAM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other media.
[0051] FIG. 4 is a flowchart illustrating exemplary operation of a network device in accordance with the principles of the invention. For exemplary purposes, the flowchart is described in reference to router 30 of FIG. 2 .
[0052] Initially, router 30 receives a packet via one of inbound links 34 (70). More specifically, one of IFCs 32 receives the packet and forwards the packet to data plane 42.
[0053] Upon receipt of the packet, data plane 42 determines whether the packet is a control plane packet or a data plane packet (72). In particular, data plane 42 associates the inbound packet with one of forwarding information tables 48, and determines a destination and associated next hop for the packet in accordance with the associated one of forwarding tables 48. Packets destined for external devices are considered transit data plane packets. Packets destined for control plane 44 are considered control plane packets.
[0054] In the event the packet is a data plane packet, data plane 42 may apply any interface-specific filters 52 associated with the designated output interface (74), and forward the packet to the next hop on an outbound link 36 (76).
[0055] In the event data plane 42 determines that the inbound packet is a control plane packet, data plane 42 assigns the control plane packet a loopback interface (78), and forwards the control plane packet to the assigned loopback interface (80). As a result, data plane 42 applies loopback services 50 (82), which represent security mechanisms, such as access control lists (ACLs), that may be applied on a packet-by-packet basis.
[0056] Upon applying loopback services 50, data plane 42 redirects the packet to a firewall component, e.g., service card 38, that applies stateful firewall services (84).
[0057] If a network attack or other security anomaly is detected, service card 38 may reject and/or log the control plane packet (85). Otherwise, service card 38 forwards the control plane packet back to data plane 42 for forwarding to control plane 44 (86).
[0058] In addition, service card 38 may output feedback communications to control plane 44 based on the packet analysis for use in updating forwarding information tables 48 and interface filters 52 to be applied by data plane 42 (88, 90).
[0059] In an alternative embodiment, data plane 42 applies does not redirect the control plane packets to service card 38, but applies sampling functions to the loop back interface. In this embodiment, data plane 42 forwards the control plane packets 42 to control plane 44, and forwards copies of all or a portion of the control plane packets to the service card. In this embodiment, service card 38 does not loop back the control plane packets for forwarding to control plane 44, and is unable to specifically reject the control plane packets. However, service card 38 applies stateful inspection, e.g., anomaly detection and trend analysis, and provides feedback communications to control plane 44 for thwarting network attacks and other security anomalies. As a result, this embodiment may be an even less invasive mechanism for applying stateful firewall services to the control plane packets.
[0060] FIG. 5 is a schematic diagram illustrating an exemplary embodiment of a network router 100 that provides stateful firewall services to control plane packets in accordance with the principles of the invention. In the illustrated embodiment, network router 100 includes a chassis 102 for housing control unit 101 having a routing component and a forwarding component (not shown). In the illustrated example, chassis 100 has nine slots for receiving a set of cards. In this example, chassis 100 receives four interface cards (IFCs) 104 and five service cards 106, which include a service card 108 that may provide stateful firewall services to control plane traffic as described herein. Each of IFCs 104 and service cards 106 may be inserted into a corresponding slot of chassis 102 for electrically coupling the card to control unit 101 via a bus, backplane, or other electrical communication mechanism. In addition, IFCs 104 include ports for coupling to communication links. Although not shown in this example, service card 106 may also include ports for coupling to communication links. Although only a single service card 108 capable of applying control plane firewall services is illustrated, multiple service cards may be utilized based on the amount of control plane traffic and the extent of the firewall services desired.
[0061] Various embodiments of the invention have been described. However, one skilled in the art will appreciate that additions or modifications may be made to the described embodiments without departing from the scope of the invention. For example, although the control plane firewall services are described herein as being performed by one or more service cards attached to a network device, in other embodiments consistent with the principles of the invention the control plane firewall services may performed by software, hardware, or a combination of software and hardware integrated with the network device. For example, control plane firewall services may be performed in the data plane, the control plane, or interface cards. Control plane firewall services may also be performed in a distributed fashion, such as partially in one or more service cards, the data plane, the control plane, the interface cards, or some combination of these. Moreover, although the techniques described herein have been primarily described as being implemented in a router, embodiments of the invention are not so limited. Other network devices, such as switches, hubs, routers within the core of a network, customer edge routers, gateways or other network devices may perform the functions described herein. These and other embodiments are within the scope of the following claims.
Claims
Certificate of Correction present
The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.
The invention claimed is:
1. A method for processing packets within a network device having a forwarding component, a routing component and a firewall component, the method comprising:
receiving control plane packets and data plane packets with a network device, wherein the control plane packets are packets destined for a routing component within the network device and which specify a network address of the routing component, and wherein the data plane packets are packets received by the network device that are destined for devices external to the network device;
forwarding the control plane packets from the forwarding component to the firewall component within the network device prior to forwarding the control plane packets from the firewall component to the routing component of the network device, wherein the firewall component is physically separate from the forwarding component and the routing component and electrically coupled to the forwarding component and the routing component;
processing the control plane packets with the physically separate firewall component to detect a network attack;
issuing a feedback communication from the physically separate firewall component to the routing component based on the processing of the control plane packets by the physically separate firewall component; and
establishing one or more filters with the routing component in response to the feedback communication, wherein at least some of the one or more filters specify which control plane packets are to be directed from the forwarding component to the routing component.
2. The method of claim 1, wherein receiving control plane packets and data plane packets comprises receiving the control plane packets and data plane packets with the forwarding component coupled to one or more physical interface cards.
3. The method of claim 2,
wherein the firewall component comprises a service card that provides an operating environment for firewall software, and
wherein forwarding the control plane packets comprises forwarding the control plane packets from the forwarding component to the service card for processing by the firewall software.
4. The method of claim 3, further comprising forwarding the control plane packets from the service card to the routing component after processing the control plane packets with the firewall software.
5. The method of claim 4, wherein issuing a feedback communication comprises issuing a feedback communication from the service card to the routing component based on the processing of the control plane packets by the firewall software.
6. The method of claim 1, wherein processing the control plane packets comprises performing stateful inspection of the packets to detect a security issue.
7. The method of claim 1, wherein processing the control plane packets comprises performing trend analysis on the control plane packets.
8. The method of claim 1, wherein processing the control plane packets comprises determining whether the control plane packets conform to one or more routing protocols.
9. The method of claim 8, wherein determining whether the control plane packets conform to one or more routing protocols comprises processing the packets with application level gateways (ALGs) specific to the routing protocols.
10. The method of claim 1, further comprising forwarding the control plane packets to the routing component after processing the control plane packets.
11. A method comprising:
receiving control plane packets and data plane packets with a control unit of a router, wherein the control unit includes a forwarding component and a routing component, wherein the control plane packets are packets destined for a routing component of the network device and which specify a network address of the routing component, and wherein the data plane packets are packets received by the network device that are destined for devices external to the network device;
forwarding the data plane packets to an output interface with the forwarding component without processing the data plane packets with a firewall component of the network device that is physically separate from and electrically connected to the control unit;
processing the control plane packets with the firewall component that is physically separate from the control unit prior to forwarding the control plane packets from the physically separate firewall component to the routing component within the control unit of the network device; and
forwarding the control plane packets from the physically separate forwarding component to the routing component after processing the control plane packets with the physically separate firewall component.
12. The method of claim 11, further comprising issuing a communication from the firewall component to the routing component based on the processing of the control plane packets by the firewall component.
13. The method of claim 12, further comprising establishing one or more filters with the routing component in response to the feedback communication, wherein the filters specify which control plane packets are to be directed from the forwarding component to the routing component.
14. The method of claim 11, wherein the firewall component comprises a service card that provides an operating environment for firewall software.
15. The method of claim 11, further comprising maintaining routing information with the routing component in accordance with the control plane packets, wherein the routing information specifies routes within a network.
16. The method of claim 15, wherein forwarding the data plane packets comprises forwarding the data plane packets in accordance with the routing information.
17. The method of claim 11, further comprising instead of forwarding the received control plane packets to the routing component, assigning a loopback interface to the received control plane packets based on inbound interfaces on which the control plane packets were received, wherein the loopback interface is associated with the firewall component, and forwarding the control plane packets to the firewall component based on the assigned loopback interface.
18. A network device comprising:
a routing component that maintains routing information in accordance with a topology of the network;
an interface that receives control plane packets and data plane packets from a network, wherein the control plane packets are packets destined for a routing component within the network device and which specify a network address of the routing component, and wherein the data plane packets are packets received by the network device that are destined for devices external to the network device; and
a firewall component that processes the control plane packets to detect a security issue, wherein the firewall component is physically separate from the routing component and a forwarding component of the network device and electrically coupled to the routing component and the forwarding component;
wherein the forwarding component directs the control plane packets from the forwarding component to the physically separate firewall component for processing prior to the network device forwarding the control plane packets to the routing component,
wherein the physically separate firewall component issues a feedback communication to the routing component based on the processing of the control plane packets by the firewall software, and wherein the routing component establishes one or more filters in response to the feedback communication, wherein at least some of the one or more filters specify which control plane packets are to be directed from the forwarding component to the routing component.
19. The network device of claim 18, wherein the firewall component comprises a service card that provides an operating environment for firewall software.
20. The network device of claim 19, wherein the service card forwards the control plane packets to the routing component after processing the control plane packets with the firewall software.
21. The network device of claim 19, wherein the service card issues the feedback communication to the routing component based on the processing of the control plane packets by the firewall software.
22. The network device of claim 18, wherein the firewall component comprises a control packet interface that rejects at least a subset of the control plane packets without forwarding the rejected subset to the routing component.
23. The network device of claim 18, wherein the firewall component includes one or more packet analysis modules that perform stateful inspection of the packets to detect the security issue.
24. The network device of claim 18, wherein the firewall component includes a trend analysis module that performs trend analysis on the control plane packets.
25. The network device of claim 18, wherein the firewall component determines whether the control plane packets conform to one or more routing protocols.
26. The network device of claim 18, wherein the firewall component includes one or more application level gateways (ALGs) to perform application level checks on the control plane packets.
27. The network device of claim 18, wherein the forwarding components mirrors the control plane packets to generate a first stream of control plane packets and a second stream of the control plane packets, and forwards the first stream of the control plane packets to the routing component and the second stream of the control plane to the firewall component.
28. The network device of claim 18, further comprising:
an interface associated with the routing component,
a service card;
wherein the forwarding component redirects the control plane packets to the service card upon determining that the control plane packets are destined for the interface associated with the routing component,
wherein the service card receives the control plane packets and loops the control plane packets back to the forwarding component for communication to the routing component; and
wherein the firewall component is applied to the control plane packets as a service upon entering or exiting the service interface card.
29. A network device comprising:
a service card;
a physical interface that receives control plane packets and data plane packets from a network;
a routing component that maintains routing information in accordance with a topology of the network,
a forwarding component that forwards the data plane packets to devices within the network to which the data plane packets are destined in accordance with the routing information without processing the data plane packets with the service card of the network device; and
a packet analysis module to analyze the control plane packets to detect a network event,
wherein the service card is physically separate from the routing component and the forwarding component and electrically coupled to the routing component and the forwarding component,
wherein the forwarding component redirects the control plane packets to the physically separate service card upon determining that the control plane packets specify a network address of the routing component and are destined for the routing component prior to forwarding the control plane packets from the physically separate service card to the routing component,
wherein the physically separate service card receives the control plane packets and loops the control plane packets back to the forwarding component for communication to the routing component, and
wherein the packet analysis module is applied when the control plane packets enters or exits the physically separate service card.
30. The network device of claim 29, wherein the service card issues a feedback communication to the routing component based on the processing of the control plane packets.
31. A computer-readable storage medium comprising instructions that cause a processor to:
receive control plane packets and data plane packets within a router, wherein the control plane packets are packets destined for a routing component within the network device and which specify a network address of the routing component, and wherein the data plane packets are packets received by the network device that are destined for devices external to the network device;
forward the data plane packets to an output interface in accordance with routing information without processing the data plane packets with firewall software of the network device that is maintained in a firewall component physically separate from and electrically connected to the routing component and forwarding component;
forward the control plane packets from a forwarding component to the physically separate firewall component within the network device prior to forwarding the control plane packets from the physically separate firewall component to the routing component of the network device;
forward the control plane packets from the physically separate firewall component to the routing component after the control plane packets are processed with the firewall software of the physically separate firewall component.
32. The computer-readable storage medium of claim 31, wherein the instructions cause the processor to forward the control plane packets to a service card for processing with the firewall software.
33. The computer-readable storage medium of claim 32, wherein the instructions cause the processor to receive a feedback communication from the service card, and forward the feedback communication from the service card to the control plane.
34. The computer-readable storage medium of claim 33, wherein the instructions cause the processor to forward the feedback communication to the control plane to install filters within a forwarding component that specify which control plane packets are to be directed from the forwarding component to the routing component.
35. A service card operable for insertion within a network device, the service card comprising:
a packet interface to receive control plane packets from a forwarding component of the network device, wherein the control plane packets specify a destination address of a routing component within the network device;
a packet analysis module that processes the control plane packets to detect a network attack; and
a feedback interface that issues a feedback communication to the routing component based on the processing of the control plane packets by the packet analysis module.
36. The service card of claim 35, wherein the packet interface forwards packets to the routing component after processing the control plane packets with the packet analysis module.
37. The service card of claim 35, wherein the control packet interface rejects at least a subset of the control plane packets without forwarding the rejected subset to the routing component.
38. The service card of claim 35, wherein the packet analysis module performs stateful inspection of the control plane packets to detect the network attack.
39. The service card of claim 35, wherein the packet analysis module comprises a trend analysis module that performs trend analysis on the control plane packets.
40. The service card of claim 35, wherein the packet analysis module determines whether the control plane packets conform to one or more routing protocols.
41. The service card of claim 35, wherein the packet analysis module comprises an application level gateway (ALG) to perform application level checks on the control plane packets.
42. A method comprising:
receiving control plane packets with a packet interface of a firewall component in a network device, wherein the control plane packets are received from a physically separate forwarding component of the network device, and wherein the control plane packets are packets destined for a physically separate routing component of the network device and which specify a network address of the physically separate routing component, wherein the firewall component is physically separate from and electrically coupled to the forwarding component and the routing component;
processing the control plane packets with a packet analysis module of the firewall component to detect a control plane security issue prior to forwarding the control plane packets to the physically separate routing component; and
forwarding the control plane packets from the firewall component to the physically separate routing component of the network device after processing the control plane packets with the firewall component.
43. The method of claim 42, further comprising issuing a feedback communication from the firewall component to the routing component based on the processing of the control plane packets.
44. The method of claim 42, wherein processing the control plane packets comprises performing stateful inspection of the packets to detect the control plane security issue.
45. The method of claim 42, wherein processing the control plane packets comprises performing trend analysis on the control plane packets.
46. The method of claim 42, wherein processing the control plane packets comprises determining whether the control plane packets conform to one or more routing protocols.
47. The method of claim 46, wherein determining whether the control plane packets conform to one or more routing protocols comprises processing the packets with application level gateways (ALGs) specific to the routing protocols.
48. A computer-readable storage medium comprising instructions that cause a programmable processor to:
receive control plane packets with a packet interface of a firewall component in a network device, wherein the control plane packets are received from a physically separate forwarding component of the network device, and wherein the control plane packets are packets destined for a physically separate routing component of the network device and which specify a network address of the physically separate routing component, wherein the firewall component is physically separate from and electrically coupled to the forwarding component and the routing component;
process the control plane packets with a packet analysis module of the firewall component to detect a control plane security issue prior to forwarding the control plane packets to the physically separate routing component; and
forward the control plane packets from the firewall component to the physically separate routing component of the router after processing the control plane packets with the firewall component.
49. The computer-readable storage medium of claim 48, wherein the instructions cause the process to issue a feedback communication from the security service card to the routing component based on the processing of the control plane packets.
Patent Citations (47)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3962681(A) | 1976-06-01 | Requa et al. | Applicant |
| US4032899(A) | 1977-06-01 | Jenny et al. | Applicant |
| US4600319(A) | 1986-07-01 | Everett, Jr. | Applicant |
| US5408539(A) | 1995-04-01 | Finlay et al. | Applicant |
| US5490252(A) | 1996-02-01 | Macera et al. | Applicant |
| US5509123(A) | 1996-04-01 | Dobbins et al. | Applicant |
| US5568471(A) | 1996-10-01 | Hershey et al. | Applicant |
| US6011795(A) | 2000-01-01 | Varghese et al. | Applicant |
| US6018765(A) | 2000-01-01 | Durana et al. | Applicant |
| US6148335(A) | 2000-11-01 | Haggard et al. | Applicant |
| US6182146(B1) | 2001-01-01 | Graham-Cumming, Jr. | Applicant |
| US6321338(B1) | 2001-11-01 | Porras et al. | Applicant |
| US6392996(B1) | 2002-05-01 | Hjalmtysson | Applicant |
| US6499088(B1) | 2002-12-01 | Wexler et al. | Applicant |
| US6563796(B1) | 2003-05-01 | Saito | Applicant |
| US6590898(B1) | 2003-07-01 | Uzun | Applicant |
| US6594268(B1) | 2003-07-01 | Aukia et al. | Applicant |
| US6598034(B1) | 2003-07-01 | Kloth | Applicant |
| US6735201(B1) | 2004-05-01 | Mahajan et al. | Applicant |
| US6751663(B1) | 2004-06-01 | Farrell et al. | Applicant |
| US6826713(B1) | 2004-11-01 | Beesley et al. | Applicant |
| US6870817(B2) | 2005-03-01 | Dolinar et al. | Applicant |
| US6970943(B1) | 2005-11-01 | Subramanian et al. | Examiner |
| US6975628(B2) | 2005-12-01 | Johnson et al. | Examiner |
| US6983294(B2) | 2006-01-01 | Jones et al. | Applicant |
| US6985956(B2) | 2006-01-01 | Luke et al. | Applicant |
| US7114008(B2) | 2006-09-01 | Jungck et al. | Applicant |
| US7162740(B2) | 2007-01-01 | Eastlake, III | Applicant |
| US7185368(B2) | 2007-02-01 | Copeland, III | Applicant |
| US7203740(B1) | 2007-04-01 | Putzolu et al. | Examiner |
| US7301899(B2) | 2007-11-01 | Goldstone | Applicant |
| US7362763(B2) | 2008-04-01 | Wybenga et al. | Examiner |
| US7496955(B2) | 2009-02-01 | Akundi et al. | Examiner |
| US2002/0095492(A1) | 2002-07-01 | Kaashoek et al. | Applicant |
| US2002/0126621(A1) | 2002-09-01 | Johnson et al. | Examiner |
| US2002/0141343(A1) | 2002-10-01 | Bays | Applicant |
| US2003/0005145(A1) | 2003-01-01 | Bullard | Applicant |
| US2003/0097557(A1) | 2003-05-01 | Tarquini et al. | Applicant |
| US2003/0110274(A1) | 2003-06-01 | Pazi et al. | Applicant |
| US2003/0120769(A1) | 2003-06-01 | McCollom et al. | Applicant |
| US2003/0214913(A1) | 2003-11-01 | Kan et al. | Applicant |
| US2004/0015721(A1) | 2004-01-01 | Eastlake, III | Applicant |
| US2005/0160289(A1) | 2005-07-01 | Shay | Applicant |
| US2006/0089994(A1) | 2006-04-01 | Hayes | Applicant |
| US2006/0185008(A1) | 2006-08-01 | Le et al. | Applicant |
| US2007/0180511(A1) | 2007-08-01 | Eastlake Iii | Applicant |
| US2007/0294369(A1) | 2007-12-01 | Ginter et al. | Applicant |
Non-Patent Literature (22)
- Juniper Networks, Inc., ‘Combating Bots and Mitigating DDoS Attacks’, Juniper Networks, Inc., 2008, entire document, http://www.juniper.net/solutions/literature/solutionbriefs/351198.pdf.Examiner
- Weaver, A.C. et al., “A Real-Time Monitor for Token Ring Networks,” Military Communications Conference, 1989. MILCOM '89, Oct. 1989, vol. 3, pp. 794-798.Applicant
- Dini, P. et al., “Performance Evaluation for Distributed System Components,” Proceedings of IEEE Second International Workshop on Systems Management, Jun. 1996, pp. 20-29.Applicant
- Integrated Services Adapter, 2000, Cisco Systems, Data Sheet, pp. 1-6, http://www.cisco.com/warp/public/cc/pd/ifaa/svaa/iasvaa/prodlit/ism2—ds.pdf.Applicant
- “The CAIDA Web Site,” www.caida.org.Applicant
- “About Endace,” www.endace.com.Applicant
- “Cisco IOS NetFlow,” www.cisco.com/warp/public/732/Tech/nmp/netflow/index.shtml.Applicant
- U.S. Appl. No. 10/188,567, entitled “Adaptive Network Flow Analysis”, filed Jul. 2, 2002, Scott Mackie.Applicant
- U.S. Appl. No. 10/228,132, entitled “Adaptive Network Router”, filed Aug. 26, 2002, Woo et al.Applicant
- U.S. Appl. No. 10/228,114, entitled “Network Router Having Integrated Flow Accounting and Packet Interception”, filed Aug. 26, 2002, Woo et al.Applicant
- U.S. Appl. No. 10/241,785, entitled “Rate-Controlled Transmission of Traffic Flow Information”, filed Sep. 10, 2002, Sandeep Jain.Applicant
- U.S. Appl. No. 10/228,150, entitled “Network Device Having Accounting Service Card,” filed Aug. 22, 2002, Woo, Hsien-Chung.Applicant
- U.S. Appl. No. 10/839,187, entitled “Port Scanning Mitigation Within A Network,” filed May 5, 2004.Applicant
- “Well-Known TCP Port Number,” www.webopedia.com, 3 pages.Applicant
- “TCP Packet Field Descriptions,” www.ipanalyser.co.uk, Analyser Sales Ltd., Copyright 2003, 2 pages.Applicant
- Michael Egan, “Decomposition of a TCP Packet,” www.passwall.com, 3 pages, Aug. 7, 2000.Applicant
- Mark Gibbs, “A Guide to Original SYN,” www.nwfusion.com, Network World, Nov. 2000, 4 pages.Applicant
- “Sample TCP/IP Packet,” www.passwall.com, Version 0.0.0 @ 03:55/Aug. 7, 2000, Copyright 2002, 6 pages.Applicant
- D.J. Bernstein, “SYN Cookies,” http://cr.yp.to/syncookies.html, Oct. 2003, 3 pages.Applicant
- Jonathan Lemon, “Resisting SYN Flood DoS Attacks with a SYN Cache,” http://people.freebsd.org/˜jlemon/papers/syncache.pdf, 9 pages.Applicant
- Stuart Staniford, et al., “Practical Automated Detection of Stealthy Portscans,” http://downloads.securityfocus.com/library/spice-ccs2000.pdf, 16 pages.Applicant
- U.S. Appl. No. 12/182,619, filed Jul. 30, 2008 entitled “Streamlined Packet Forwarding Using Dynamic Filters For Routing And Security In A Shared Forwarding Plane,”.Applicant