Patent classifications
H04L2101/659
Methods for improved network security using asymmetric traffic delivery and devices thereof
Methods, non-transitory computer readable media, application delivery controller (ADC) apparatuses, and network traffic management systems that receive a request including an Internet Protocol (IP) version 6 (IPv6) source address and an IPv6 destination address. A client IP version 4 (IPv4) address of a client from which the request originated and a server IPv4 address of a server are determined from one or more extracted portions of one or more of the IPv6 source address or the IPv6 destination address. The request is modified to include an IPv4 source address and an IPv4 destination address. The IPv4 source address and the IPv4 destination address include the client IPv4 address and the server IPv4 address, respectively. The modified request is sent to the server based on the server IPv4 address included in the IPv4 destination address of the modified request.
Facilitating distributed SNAT service
Some embodiments of the invention provide novel methods for facilitating a distributed SNAT (dSNAT) middlebox service operation for a first network at a host computer in the first network on which the dSNAT middlebox service operation is performed and a gateway device between the first network and a second network. The novel methods enable dSNAT that provides stateful SNAT at multiple host computers, thus avoiding the bottleneck problem associated with providing stateful SNAT at gateways and also significantly reduces the need to redirect packets received at the wrong host by using a capacity of off-the-shelf gateway devices to perform IPv6 encapsulation for IPv4 packets and assigning locally unique IPv6 addresses to each host executing a dSNAT middlebox service instance that are used by the gateway device.
SYSTEMS, METHODS AND APPARATUS FOR GEOFENCE NETWORKS
Systems and methods are disclosed for enforcing at least one rule associated with a geofence. At least one device is constructed and configured in network communication with a server platform and a database. The server platform defines at least one geofence for a region of interest and specifies at least one rule associated with the at least one geofence, thereby creating a rule-space model for the region of interest. The at least one geofence comprises a multiplicity of geographic designators with each geographic designator assigned with a unique IPv6 address. The at least one device receives at least one notification signal regarding the at least one rule from the at least one server platform and implements the at least one rule when the at least one device is within a predetermined distance from the at least one geofence for the region of interest.
Address generation for networks
A network includes at least two nodes that employ a routing protocol to communicate across a network. One of the nodes is a parent node and another of the nodes is a child node of the parent node. An address generator assigns a unique network address to the child node by appending an address value of a number of bits to a parent address of the parent node to create the unique network address for the child node.
METHOD AND APPARATUS FOR SENDING REPLY PACKET, COMPUTING DEVICE, AND STORAGE MEDIUM
The disclosure discloses a network device, an apparatus, and a network system. The network device receives a reply packet sent by a DHCP service device, and determines a first next-hop address from a plurality of next-hop addresses corresponding to a destination IP address of the reply packet, where the first next-hop address is a first tunnel endpoint IP address of the relay device and is different from a tunnel endpoint IP address of another relay device in a target anycast group to which the relay device belongs, and a communication connection is established between each relay device in the target anycast group and the client. The network device may forward the reply packet to the relay device based on the first next-hop address.
Network address allocation management using prefix allocation trees with asynchronous workflows
Disclosed are various embodiments for managing network address allocations using prefix allocation trees. In one embodiment, a request is received to allocate a particular network address block. The request specifies one or more attributes and at least one of a prefix or a size for the particular network address block. A prefix allocation tree is updated to indicate that the particular network address block corresponding to the prefix is allocated instead of free and to associate the attribute(s) with the particular network address block. An identification of an allocation of the network address block is returned in response to the request to allocate the particular network address block. An attribute index of the prefix allocation tree is updated asynchronously to index the attribute(s) in association with the particular network address block.
SYSTEMS AND METHODS FOR ADVERTISING INTERNET PROTOCOL (IP) VERSION 4 NETWORK LAYER ROUTING INFORMATION WITH AN IP VERSION 6 NEXT HOP ADDRESS
A first network device associated with a network may establish an Internet protocol version 6 Multiprotocol BGP session with a second network device associated with the network. The first network device and second network device are both capable of forwarding both IPv4 and IPv6 packets with only an IPv6 address configured on the interface of both the first network device and second network device. The first network device may exchange Multiprotocol Reachability capability with second network device for corresponding 2-tuple Address Family Identifier/Subsequent Address Family Identifier. The first network device may advertise Internet protocol version 4 network layer reachability information and may advertise Internet protocol version 6 network layer reachability information with IPv6 extended next hop encoding using Internet Assigned Numbering Authority assigned capability code value 5 to second network device.
PROVIDING EXTENDIBLE NETWORK CAPABILITIES FOR MANAGED COMPUTER NETWORKS
Techniques are described for managing communications between multiple computing nodes, such as for computing nodes that are part of managed virtual computer networks provided on behalf of users or other entities. In some situations, one or more of the computing nodes of a managed virtual computer network is configured to perform actions to extend capabilities of the managed virtual computer network to other computing nodes that are not part of the managed virtual computer network, such as by forwarding communications between computing nodes of the managed virtual computer network and the other external computing nodes so as to enable the other external computing nodes to participate in the managed virtual computer network. In some situations, the computing nodes may include virtual machine nodes hosted on one or more physical computing machines or systems, such as by or on behalf of one or more users.
Systems and methods for defining and implementing rules for three dimensional geofences
The present invention is directed to methods and systems for enforcing at least one rule within a geofence. The rule is enforced by a fencing agent on an unmanned aerial vehicle (UAV). The geofence is defined by a plurality of geographic designators, with the plurality of geographic designators each being associated with an Internet Protocol (IP) address, preferably an IPv6 address.
Domain Name System Services for Variable-Length Address Networks
A DNS server comprises: a receiver configured to receive a registration request comprising a domain name, a local address, and a scope, the registration request requests registration of the domain name; a processor coupled to the receiver and configured to execute computer instructions that cause the processor to: assign an address to the domain name based on the local address and the scope, and generate a registration response comprising the address; and a transmitter coupled to the processor and configured to transmit the registration response towards an endpoint. The processor may be further configured to cache a correspondence among the domain name, the address, and the scope.