Compressing packet data
US-9036662-B1 · May 19, 2015 · US
US11805045B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11805045-B2 |
| Application number | US-202117160347-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 27, 2021 |
| Priority date | Sep 21, 2017 |
| Publication date | Oct 31, 2023 |
| Grant date | Oct 31, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for selectively transmitting routing information between separated local area network (LAN) interfaces are disclosed. In exemplary embodiments, a network appliance to update a local routing table with IP subnet, neighbor type, source type, and community identifier of a second network appliance; based at least on the local routing table, receive a customized routing policy and subnet exporting policy that permits the network appliance to export a subset of IP addresses from the local routing table to a permitted community of network appliances, wherein the customized routing policy and subnet exporting policy are configured by a network administrator of the network appliance; match the permitted community of network appliances to a new community identifier of a third network appliance; and export the subset of IP addresses of the local routing table to the third network appliance based on the customized routing policy and subnet exporting policy.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for selectively transmitting routing information between separated local area network (LAN) interfaces by a network appliance in a first LAN, the method comprising: receiving, at the network appliance, a first Internet Protocol (IP) subnet of a first remote network appliance in a second LAN; determining, based on a location of the first remote network appliance, a first neighbor type of the first remote network appliance and a first route source type associated with the first IP subnet, wherein the neighbor type is selected from a list comprising at least a branch router, a provider edge (PE) router, and a branch transit router; determining, by the network appliance, a first community identifier of the first remote network appliance based on the first route source type, wherein a respective community identifier includes a string value that indicates a corresponding route source type; updating, at the network appliance, a local routing table based on the IP first subnet, the first neighbor type, the first route source type, and the first community identifier; receiving, at the network appliance, a second IP subnet of a second remote network appliance in a third LAN; determining, by the network appliance, a second neighbor type of the second remote network appliance and a second route source type associated with the second IP subnet of the second remote network appliance; determining, by the network appliance, a second community identifier of the second remote network appliance based on the second route source type; and determining, by the network appliance, whether to export the first subnet from the local routing table to the second remote network appliance based on a subnet exporting policy matching the first and second neighbor types and the first and second community identifiers. 2. The computer-implemented method of claim 1 , wherein the routing information is received using a border gateway protocol (BGP). 3. The computer-implemented method of claim 1 , wherein the community identifier is a border gateway protocol (BGP) community string. 4. The computer-implemented method of claim 1 , wherein the location of the first remote network appliance corresponds to one of a branch location, central location, private cloud network, and data center. 5. The computer-implemented method of claim 1 , wherein the first neighbor type of the first remote network appliance with respect to the network appliance is different from the second neighbor type of the second remote network appliance with respect to the network appliance. 6. The computer-implemented method of claim 1 , wherein the subnet exporting policy indicates which subset of IP addresses from the local routing table is permitted to be forwarded to the second remote network appliance without knowledge of specific IP address prefixes. 7. The computer-implemented method of claim 1 , further comprising: determining a new route export policy at the network appliance; and updating the subnet exporting policy based on the new route export policy. 8. A network appliance for selectively transmitting routing information between separated local area network (LAN) interfaces in a first LAN, the network appliance to: receive a first Internet Protocol (IP) subnet of a first remote network appliance in a second LAN; determine, based on a location of the first remote network appliance, a first neighbor type of the first remote network appliance and a first route source type associated with the first IP subnet, wherein the neighbor type is selected from a list comprising at least a branch router, a provider edge (PE) router, and a branch transit router; determine a first community identifier of the first remote network appliance based on the first route source type, wherein a respective community identifier includes a string value that indicates a corresponding route source type; update a local routing table based on the first IP subnet, the first neighbor type, the first route source type, and the first community identifier; receive a second IP subnet of a second remote network appliance in a third LAN; determine a second neighbor type of the second remote network appliance and a second route source type associated with the second IP subnet of the second remote network appliance; determine a second community identifier of the second remote network appliance based on the second route source type; and determine whether to export the first subnet from the local routing table to the second remote network appliance based on a subnet exporting policy matching the first and second neighbor types and the first and second community identifiers. 9. The network appliance of claim 8 , wherein the routing information is received using a border gateway protocol (BGP). 10. The network appliance of claim 8 , wherein the community identifier is a border gateway protocol (BGP) community string. 11. The network appliance of claim 8 , wherein the location of the first remote network appliance corresponds to one of: a branch location, central location, private cloud network, and data center. 12. The network appliance of claim 8 , wherein the first neighbor type of the first remote network appliance with respect to the network appliance is different from a second neighbor type of the second remote network appliance with respect to the network appliance. 13. The network appliance of claim 8 , wherein the subnet exporting policy indicates which subset of IP addresses from the local routing table is permitted to be forwarded to the second remote network appliance without knowledge of specific IP address prefixes. 14. The network appliance of claim 8 , the network appliance is further to: determine a new route export policy at the network appliance; and update the subnet exporting policy based on the new route export policy. 15. A non-transitory computer-readable storage medium storing a plurality of instructions executable by one or more processors of a network appliance in a first local area network (LAN), the plurality of instructions when executed by the one or more processors cause the one or more processors to: receive a first Internet Protocol (IP) subnet of a first remote network appliance in a second LAN; determine, based on a location of the first remote network appliance, a first neighbor type of the first remote network appliance and a first route source type associated with the first IP subnet, wherein the neighbor type is selected from a list comprising at least a branch router, a provider edge (PE) router, and a branch transit router; determine a first community identifier of the first network appliance based on the first route source type, wherein a respective community identifier includes a string value that indicates a corresponding route source type; update a local routing table based on the first IP subnet, the first neighbor type, the first route source type, and the first community identifier; receive a second IP subnet of a second remote network appliance in a third LAN; determine a second neighbor type of the second remote network appliance and a second route source type associated with the second IP subnet of the second remote network appliance; determine a second community identifier of the second remote network appliance based on the second route source type; and determine whether to export the first subnet from the local routing table to the second remote network appliance based on a subnet exporting policy matching the first and second neighbor types and the first and second community identifiers.
Topology update or discovery · CPC title
by updating distance vector protocols · CPC title
Interdomain routing, e.g. hierarchical routing · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.