Multi-access interface for internet protocol security
A method may include providing a multi-access interface for network traffic, comprising: receiving information regarding topology of a virtual private network and storing the topology in the form of a routing table. A method may include providing an interface for network traffic, comprising: in a virtual private network comprising a plurality of tunnels delivering only information associated with OSI Level 3, receiving a network communication and performing multicast forwarding among the plurality of tunnels using multicast forwarding from OSI Level 2. A method may include providing an interface for network traffic, comprising, in a virtual private network: establishing a connection between a first node of the virtual private network and a second node serving as a virtual private network broker and fetching, by the first node from the virtual private network broker, information regarding one or more other nodes of the virtual private network.
1. A computer-implemented method for providing a multi-access interface for network traffic, comprising:
storing a routing table associated with the multi-access interface;
implementing a virtual private network component;
receiving, from the virtual private network component, information regarding topology of a virtual private network, wherein the information regarding the topology includes Internet Protocol Security (IPSec) tunnel information, and wherein the information is received via a standard routing table command and/or application programming interface (API);
storing the topology in the routing table, wherein the topology is stored as routes according to a standard routing table format, and wherein the topology is stored only within the routing table and is not duplicated within the virtual private network component; and
transmitting network traffic according to the topology stored in the routing table.
2. The computer-implemented method of claim 1 , wherein storing the topology comprises storing, in the routing table, information regarding next hop gateway definitions.
3. The computer-implemented method of claim 1 , wherein storing the topology comprises storing, in the routing table, information regarding point-to-point tunnels and/or point-to-multipoint tunnels that defines the topology.
4. A system comprising:
at least one processor; and
a non-transitory, computer-readable medium embodying instructions executable by the at least one processor for:
storing a routing table associated with the multi-access interface;
implementing a virtual private network component;
receiving, from the virtual private network component, information regarding topology of a virtual private network, wherein the information regarding the topology includes Internet Protocol Security (IPSec) tunnel information, and wherein the information is received via a standard routing table command and/or application programming interface (API);
storing the topology in the routing table, wherein the topology is stored as routes according to a standard routing table format, and wherein the topology is stored only within the routing table and is not duplicated within the virtual private network component; and
transmitting network traffic according to the topology stored in the routing table.
5. The system of claim 4 , wherein storing the topology comprises storing, in the routing table, information regarding next hop gateway definitions.
6. The system of claim 4 , wherein storing the topology comprises storing, in the routing table, information regarding point-to-point tunnels and/or point-to-multipoint tunnels that defines the topology.
7. A non-transitory, computer-readable medium embodying computer-executable instructions configured for:
storing a routing table associated with the multi-access interface;
implementing a virtual private network component;
receiving, from the virtual private network component, information regarding topology of a virtual private network, wherein the information regarding the topology includes Internet Protocol Security (IPSec) tunnel information, and wherein the information is received via a standard routing table command and/or application programming interface (API);
storing the topology in the routing table, wherein the topology is stored as routes according to a standard routing table format, and wherein the topology is stored only within the routing table and is not duplicated within the virtual private network component; and
transmitting network traffic according to the topology stored in the routing table.
8. The medium of claim 7 , wherein storing the topology comprises storing, in the routing table, information regarding next hop gateway definitions.
9. The medium of claim 7 , wherein storing the topology comprises storing, in the routing table, information regarding point-to-point tunnels and/or point-to-multipoint tunnels that defines the topology.