{"id":13497866,"url":"https://github.com/OpenOverlayRouter/oor","last_synced_at":"2025-03-28T22:31:52.611Z","repository":{"id":217947517,"uuid":"47321500","full_name":"OpenOverlayRouter/oor","owner":"OpenOverlayRouter","description":"OpenOverlayRouter is an implementation to create programmable overlay networks.","archived":false,"fork":false,"pushed_at":"2020-09-03T06:50:10.000Z","size":9352,"stargazers_count":123,"open_issues_count":8,"forks_count":39,"subscribers_count":19,"default_branch":"master","last_synced_at":"2024-10-31T14:36:38.717Z","etag":null,"topics":["lisp","openwrt","overlay","router"],"latest_commit_sha":null,"homepage":"http://openoverlayrouter.org/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/OpenOverlayRouter.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":"AUTHORS","dei":null,"publiccode":null,"codemeta":null}},"created_at":"2015-12-03T09:23:44.000Z","updated_at":"2024-09-11T13:31:10.000Z","dependencies_parsed_at":null,"dependency_job_id":"b5e14d0d-9f06-4e89-8d75-5126bb55526e","html_url":"https://github.com/OpenOverlayRouter/oor","commit_stats":null,"previous_names":["openoverlayrouter/oor"],"tags_count":22,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenOverlayRouter%2Foor","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenOverlayRouter%2Foor/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenOverlayRouter%2Foor/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/OpenOverlayRouter%2Foor/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/OpenOverlayRouter","download_url":"https://codeload.github.com/OpenOverlayRouter/oor/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":246110275,"owners_count":20725025,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["lisp","openwrt","overlay","router"],"created_at":"2024-07-31T20:00:43.530Z","updated_at":"2025-03-28T22:31:52.593Z","avatar_url":"https://github.com/OpenOverlayRouter.png","language":"C","readme":"Overview\n--------\n\nThe Open Overlay Router (OOR) project aims to deliver a flexible and modular\nopen-source implementation to deploy programmable overlay networks. It\nleverages on encapsulating overlay-specific packets into underlay-compatible\npackets at the edges of the instantiated overlay and route them over the\nphysical underlying infrastructure. In order to do so, it maps overlay\nidentifiers to underlay locators and keeps those mappings updated over \ntime. In the current version, OOR uses the LISP protocol for the \ncontrol-plane (e.g. mapping retrieval and updating, etc), NETCONF/YANG for \nthe management-plane (e.g. overlay identifiers provisioning, etc) and can \nuse both LISP and VXLAN-GPE headers for encapsulation. \n\nMost of the OOR architecture revolves around the LISP protocol and its \ncomponents, that we introduce briefly here. The Locator/ID Separation \nProtocol (LISP) is an IETF protocol (RFC6830) that decouples the semantics \nof identity and location on current IP addresses. It uses the concept of \nEndpoint IDentifiers (EIDs) to name hosts in edge networks, and Routing \nLOCators (RLOCs) for nodes in transit networks. EIDs and RLOCs are \nsyntactically indistinguishable from current IPv4 and IPv6 addresses, \nenabling backwards compatibility with the existing Internet architecture. \nA distributed database, the Mapping System, is responsible for maintaining \nthe associations between EIDs and RLOCs. LISP Mobile Node (LISP-MN) is a \nspecification to enable fast host mobility using LISP. For convenience, OOR \nuses terminology borrowed from the LISP protocol and thus uses the term EID \nfor the overlay identifiers and the term RLOC for the underlay locators. \nRegarding the LISP devices that OOR implements, currently it can operate as \nan xTR, LISP-MN, MS, MR, DDT Node or RTR.\n\nNowadays, OOR runs on desktop Linux, OpenWrt home routers and Android and iOS \ndevices. The current reference platform for OOR development is Ubuntu \nServer 16.04 LTS (Xenial Xerus), OpenWrt 18.06 and Android 6.0 (Marshmallow),\niOS 11.3.\n\nOOR can work together with the Vector Packet Processing (VPP) technology to \nobtain an xTR capable to reach bandwith close to the 10 GBps. To use VPP as \nthe OOR dataplane, refears to the README.vpp.md.\n\nOpenOverlayRouter is a rename of the LISPmob.org project.\n\n\nNetwork Prerequisites\n---------------------\n\nRunning a Open Overlay Router device on the public Internet requires the following:\n\nxTR - MN\n\n  * an EID from a Mapping Service Provider (MSP),\n  * the RLOC of the Map-Server that will accept the registration of this EID,\n  * an authentication token to register the EID with the Map-Server,\n  * the RLOC of a Map-Resolver,\n  * the RLOC of a Proxy-ETR,\n  * a publicly routable RLOC for the device running OOR, which is neither \n  firewalled, nor behind NAT (see however \"NAT traversal\" section for details on \n  this).\n\nRTR\n  * the RLOC of a Map-Resolver,\n  * a publicly routable RLOC for the device running OOR, which is neither \n  firewalled, nor behind NAT.\n\nMS - MR - DDT\n  * a publicly routable RLOC for the device running OOR, which is neither \n  firewalled, nor behind NAT.\n\nThe above information is used for configuring 'oor' via the configuration file \n'oor.conf'. See section \"OpenWrt\" for OpenWrt configuration details,\"Android\" \nfor Android configuration details and \"iOS\" for Apple iOS configuration.\n\nVisit http://www.lisp4.net/ for more info on the deployment status of the LISP\nbeta-network and how you can join the testbed.\n\nSoftware Prerequisites\n----------------------\n\nTo build Open Overlay Router for a standard Linux, you will need:\n\n  * a Linux hosts\n  * a C compiler (tested with `gcc`)\n  * GNU make\n  * git, unless you use a tarball\n  * libConfuse\n  * gengetopt\n  * libcap v2+\n  * libzmq v3\n  * libxml2\n\nOn Debian-derived Linux distributions (including Ubuntu), installing the\nfollowing packages will provide all necessary dependencies:\n\n  * 'build-essential'\n  * 'git-core'\n  * 'libconfuse-dev'\n  * 'gengetopt'\n  * 'libcap2-bin'\n  * 'libzmq3-dev'\n  * 'libxml2-dev'\n\nThe latest version of the Open Overlay Router source code can be obtained \nfrom Github:\n\n    git clone git://github.com/OpenOverlayRouter/oor.git\n\n\nInstallation\n------------\n\nTo build the code for Linux operating run the following in the top-level directory:\n\n    make \n\nTo install it in `/usr/local/sbin`, run\n\n    sudo make install\n\nA `Vagrantfile` is provided for quick installation in a dedicated VM, see the\n\"Using Vagrant\" section.\n    \nTo build the code for OpenWrt you will need the OpenWrt official SDK. However,\nfor your convenience, we encourage you to install the official packet from OpenWrt\nrepository. Check section \"OpenWrt\" for details.\n\nRunning Open Overlay Router\n---------------------------\n\nOnce the code is successfully installed on the device, `oor.conf.example` should \nbe copied to `/etc/oor.conf` and edited with the proper values. Again, see \nsection 'OpenWrt' for OpenWrt details about this. Additionally the device's \ninterface used for physical network connectivity (such as 'eth0', 'wlan0' or 'ppp0')\n must also be specified in the configuration file.\n\nPrior to execute Open Overlay Router, make sure that each external interface (such \nas 'wan0') has defined a default route with different 'metric' in the routing\ntable (there is a 'default' entry for each outgoing interface). In most cases,\nthis is auto-configured by the operating system during start-up.\n\nCheck that sysctl options configuration is correct. Make sure that rp_filter\nkernel network parameter is disabled. It is disabled by default in OpenWrt, but,\nfor instance, it is enabled by default in Ubuntu. Make sure too that IP\nforwarding is enabled. It should be enabled by default in OpenWrt.  \n    \nYou can instruct your system to auto-configure these values during system\nboot-up if you add the following lines to `/etc/sysctl.conf`. Remember to \nreboot your system after adding these lines.\n\n    net.ipv4.conf.default.rp_filter=0\n    net.ipv4.conf.all.rp_filter=0\n    net.ipv4.ip_forward=1\n    net.ipv6.conf.all.forwarding=1\n\nThe user space daemon can be started by a non privileged user with the appropriate \npermissions (particularly CAP_NET_ADMIN and CAP_NET_RAW). Such user can run the \ndaemon with: \n\n    oor -f /etc/oor.conf\n\nIt will set up networking and register to the mapping system, after which you\ncan enjoy all the benefits of LISP. \n\n\nFeatures\n--------\n\nThis is the list of supported features at this moment\n\n* xTR / MN\n\n    - Register to the Mapping System\n    - Request mappings\n    - Reply to mapping requests\n    - Encapsulate data packets (LISP and VXLAN-GPE)\n    - Decapsulate data packets (LISP and VXLAN-GPE)\n    - RLOC Probing (user configurable)\n    - IPv6 full support (EIDs and RLOCs)\n    - Interface management \n    - Multihoming\n    - Experimental NAT traversal\n    - Explicit Locator Path (ELPs)\n    - Instance ID / VNI support\n    - NETCONF/YANG configurable\n    - VPP support (only for IPv4 RLOCs)\n    - Specify destination EID prefixes (only linux and OpenWrt)\n    - Remote RLOC registration\n\n* RTR\n\n    - Request mappings\n    - Reply to mapping requests\n    - Reencapsulate data packets (LISP and VXLAN-GPE)\n    - RLOC Probing (user configurable)\n    - IPv6 full support (EIDs and RLOCs)\n    - Interface management \n    - Multihoming\n    - Explicit Locator Path (ELPs)\n    - Instance ID / VNI support\n    - Experimental NAT traversal\n\n* MS / MR\n\n    - Process registration requests\n    - Notify correct registration\n    - Accept more specific entries\n    - Reply to mapping requests when Proxy Relpy activated\n    - Forward requests to xTRs\n    - IPv6 full support (EIDs and RLOCs)\n    - Interface management \n    - Explicit Locator Path (ELPs)\n    - Instance ID support\n    - Experimental NAT traversal\n    - Process DDT Map Requests\n\n* DDT\n    - DDT authoritative sites\n    - DDT delegated sites\n    - Process encapsulated DDT map request\n    - Generate Map Referrals\n    - Instance ID / VNI support\n\n* DDT-MR\n    - Process mapping requests and forward them to DDT root nodes\n    - Process replies from DDT mapping system\n    - Instance ID / VNI support\n    \nNote: OOR doesn't support overlapping local prefixes with different IIDs when operating as \na XTR or MN.    \n\nMobile Node mode (MN)\n---------------------\nWhen 'oor' is running in MN mode, the EID obtained configured is associated to \nthe 'lispTun0' virtual interface. Two /1 routes covering the full IP addresses \nspace should appear in the routing table. These routes should be pointing to \n'lispTun0' device. The following lines show an example of how 'ip addr' and 'ip \nroute' will look like with IPv4, expect a similar output with IPv6:\n\n    $ ip addr\n    1: lo: \u003cLOOPBACK,UP,LOWER_UP\u003e mtu 16436 qdisc noqueue state UNKNOWN \n        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n        inet 127.0.0.1/8 scope host lo\n           valid_lft forever preferred_lft forever\n    2: eth0: \u003cBROADCAST,MULTICAST,UP,LOWER_UP\u003e mtu 1500 qdisc pfifo_fast state UP qlen 1000\n        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n        inet \u003cRLOC\u003e brd \u003cRLOC_BROADCAST\u003e scope global eth0\n           valid_lft forever preferred_lft forever\n    3: lispTun0: \u003cPOINTOPOINT,UP,LOWER_UP\u003e mtu 1450 qdisc pfifo_fast state UNKNOWN qlen 500\n        link/none \n        inet \u003cEID\u003e scope host lispTun0\n\n\n    $ ip route\n    \u003cRLOC_Network\u003e dev eth0  proto kernel  scope link  src \u003cRLOC\u003e\n    169.254.0.0/16 dev eth0  scope link  metric 1000\n    0.0.0.0/1 dev lispTun0\n    128.0.0.0/1 dev lispTun0\n    default via \u003cRLOC_GW\u003e dev eth0  metric 100\n\nxTR mode\n--------\n \nTo configure Open Overlay Router to use it on x Tunnel Router (xTR) mode take into \naccount the following considerations.\n\nAn EID /30 (at least) prefix is required for IPv4 EIDs. For IPv6 you should have \na /126 (at least). This prefix should be used as the network prefix for the subnet\nwhere the hosts on the EID space connected to the router are allocated. Assign \nthe EID to an interface on the router and configure it as you would do for a normal\nnetwork prefix (static configuration, DHCP, etc...). No EID is used for the 'lispTun0' \ninterface in router mode (a local address is automatically used by OOR instead).\nThe following lines show an example of how 'ip addr' and 'ip route' will look like \nwith IPv4, expect a similar output with IPv6:\n\n    $ ip addr\n    1: lo: \u003cLOOPBACK,UP,LOWER_UP\u003e mtu 16436 qdisc noqueue state UNKNOWN \n        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n        inet 127.0.0.1/8 scope host lo\n           valid_lft forever preferred_lft forever\n    2: eth0: \u003cBROADCAST,MULTICAST,UP,LOWER_UP\u003e mtu 1500 qdisc pfifo_fast state UP qlen 1000\n        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n        inet \u003cRLOC\u003e brd \u003cRLOC_BROADCAST\u003e scope global eth0\n           valid_lft forever preferred_lft forever\n    3: eth1: \u003cBROADCAST,MULTICAST,UP,LOWER_UP\u003e mtu 1500 qdisc pfifo_fast state UP qlen 1000\n        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n        inet \u003cEID1\u003e brd \u003cEID1_BROADCAST\u003e scope global eth0\n           valid_lft forever preferred_lft forever\n    4: eth2: \u003cBROADCAST,MULTICAST,UP,LOWER_UP\u003e mtu 1500 qdisc pfifo_fast state UP qlen 1000\n        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n        inet \u003cEID2\u003e brd \u003cEID2_BROADCAST\u003e scope global eth0\n           valid_lft forever preferred_lft forever\n    5: lispTun0: \u003cPOINTOPOINT,UP,LOWER_UP\u003e mtu 1440 qdisc pfifo_fast state UNKNOWN qlen 500\n        link/none \n\n\n    $ ip route\n    \u003cRLOC_Network\u003e dev eth0  proto kernel  scope link  src \u003cRLOC\u003e\n    \u003cEID1_Network\u003e dev eth1  proto kernel  scope link  src \u003cEID1\u003e\n    \u003cEID2_Network\u003e dev eth2  proto kernel  scope link  src \u003cEID2\u003e\n    default via \u003cRLOC_GW\u003e dev eth0  metric 100\n\n\n    $ ip rule\n    0:      from all lookup local \n    x:      from \u003cRLOC\u003e lookup x \n    99:     from all to \u003cEID1_Network\u003e lookup main\n    99:     from all to \u003cEID2_Network\u003e lookup main  \n    100:    from \u003cEID1_Network\u003e lookup 100\n    100:    from \u003cEID2_Network\u003e lookup 100 \n    32766:  from all lookup main \n    32767:  from all lookup default\n\nThis output is only valid when OOR is not compiled to work with VPP.\n\nRTR mode\n--------\n\nWhen running in RTR mode, Open Overlay Router serves as a Re-encapsulating Tunnel Router \nthat decapsulates the received traffic to reencapsulate it again towards the next hop.\nAn RTR can also be used to provide NAT support to xTRs/MNs when it works together with a\nMS with NAT Traversal support.\n\nTo configure an RTR, select the corresponding operating-mode and fill the parameters \nof the RTR section and Tunnel Router general configuration of the configuration file.\nThe following lines show an example of how 'ip addr' and 'ip route' will look like \nwith IPv4, expect a similar output with IPv6:\n\n    $ ip addr\n    1: lo: \u003cLOOPBACK,UP,LOWER_UP\u003e mtu 16436 qdisc noqueue state UNKNOWN \n        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\n        inet 127.0.0.1/8 scope host lo\n           valid_lft forever preferred_lft forever\n    2: eth0: \u003cBROADCAST,MULTICAST,UP,LOWER_UP\u003e mtu 1500 qdisc pfifo_fast state UP qlen 1000\n        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n        inet \u003cRLOC1\u003e brd \u003cRLOC1_BROADCAST\u003e scope global eth0\n           valid_lft forever preferred_lft forever\n    3: eth1: \u003cBROADCAST,MULTICAST,UP,LOWER_UP\u003e mtu 1500 qdisc pfifo_fast state UP qlen 1000\n        link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff\n        inet \u003cRLOC2\u003e brd \u003cRLOC2_BROADCAST\u003e scope global eth0\n           valid_lft forever preferred_lft forever\n    4: lispTun0: \u003cPOINTOPOINT,UP,LOWER_UP\u003e mtu 1440 qdisc pfifo_fast state UNKNOWN qlen 500\n        link/none \n\n    $ ip route\n    \u003cRLOC1_Network\u003e dev eth0  proto kernel  scope link  src \u003cRLOC1\u003e\n    \u003cRLOC2_Network\u003e dev eth1  proto kernel  scope link  src \u003cRLOC2\u003e\n    default via \u003cRLOC_GW_1\u003e dev eth0  metric 100\n    default via \u003cRLOC_GW_2\u003e dev eth1  metric 110\n\n    $ ip rule\n    0:      from all lookup local \n    x:      from \u003cRLOC1\u003e lookup x \n    y:     from \u003cRLOC2\u003e lookup y\n    32766:  from all lookup main \n    32767:  from all lookup default\n\nMS mode\n-------\n\nOpen Overlay Router can be configured as a basic Map Server (MS) where configured EID prefixes\ncan be registered by xTRs. OOR will also reply to MapRequests addressed to those prefixes.\nMS can be associated with an RTR in order to provide NAT support to xTRs/MN.\n\nTo configure Open Overlay Router as a MS/MR, select the corresponding operating-mode and \nfill the parameters of the MS section of the configuration file.\n\nDDT mode\n--------\n\nOpen Overlay Router implements the LISP Delegated Database Tree (LISP-DDT) specified\nin the RFC 8111. LISP-DDT is a hierarchical distributed database that embodies the \ndelegation of authority to provide mappings from LISP EIDs to RLOCs. It is a statically \ndefined distribution of the EID namespace among a set of LISP-speaking servers called \n\"DDT nodes\".  Each DDT node is configured as \"authoritative\" for one or more EID-prefixes, \nalong with the set of RLOCs for Map-Servers or \"child\" DDT nodes to which more-specific \nEID-prefixes are delegated.\n\nTo configure OOR as a DDT node, define the authoritative sites and the delegated sites.\nDelegated sites could be of type MAP_SERVER_DDT_NODE if the next hop is a Map Server, or \nCHILD_DDT_NODE if next hop is a DDT node with more-specific EID prefix information.\nThe node authoritative for all EID space is usually called DDT ROOT node.\n\nMR mode\n-------\n\nA LISP Map Resolver (MR) is a node that forwards Map Requests from xTRs to the MSs \nresponsibles of the requested EID. The MR implemented by Open Overlay Router use LISP-DDT to\nfind the suitable MS.\n\nTo configure OOR as a MR, specify the addresses of the DDT Root nodes to be used.\n\n\nUsing Vagrant\n-------------\n\nThe top-level directory of the tree has a `Vagrantfile` to allow quick\ncreation of a VM with all prerequisites preinstalled so the code can be built\nquickly in an isolated environment. This is especially useful for development\non platforms other than Linux, where code editing is done on the native host\nOS, and the Linux VM created by Vagrant is used only for building and testing\nthe code.\n\nVagrant automatically sets up a shared folder `/vagrant` pointing to the\nfolder where the Vagrantfile resides, in this case the top-level folder of the\nsource tree. This way, changes to the source code on the host computer are\nautomatically reflected in the VM, and binaries created in the VM are also\nautomatically available to the host OS.\n\nTo create the VM, run:\n\n    vagrant up\n\nThis will create a VM called `oor-dev` by downloading the base box (currently\nUbuntu 17.10), updating packages to the latest version, and installing build\ndependencies for OOR. It may be useful to install the `vagrant-cachier` plugin\nto cache Ubuntu packages, in order to speed up rebuilds of the VM, if done\noften:\n\n    vagrant plugin install vagrant-cachier\n\nOnce provisioning of the VM finished, it can be accessed with:\n\n    vagrant ssh\n\nThere is also a VM definition called `oor-dev-android`, which is not\nprovisioned by default. It does all of the above, and in addition it creates\nthe environment for building the Android APK. Provisioning it requires using\nthe VM name explicitly in the `vagrant up` command:\n\n    vagrant up oor-dev-android\n    \nUsing Dockers\n-------------\n\nDocker is a platform that is based on packaging applications in containers. It \nimmediately improves security, reduce costs and gain cloud portability.\nAll these improvements can be achieved without changing the original code.\n\nThe OOR can work as a Docker Container. This will allow to get the lifecycle of \nOOR from development to production shorter receiving and running automatically \nthe last code of OOR from github. \n\nUsing OOR as a container can also be used to provide LISP support to other running\ncontainers in the host. \n\nIn the Docker directory you can find a README.md file with more details in how to \ncreate and use OOR as a container.\n\n\nOpenWrt\n-------\n\nTo enable OpenWrt configuration mode and the specific routing\noperations, the code should have been compiled with the\n`platform=OpenWrt` option during OpenWrt package creation. Please note that the best\nway to get Open Overlay Router on OpenWrt is using the official package from OpenWrt\nrepository or get a precompiled binary  from the  github website\n(https://github.com/OpenOverlayRouter/oor/wiki/Downloads). \n\nIn OpenWrt, the configuration is performed through the OpenWrt standard\nconfiguration tool UCI, instead of using 'oor.conf' file. Configure the UCI\nfile manually in '/etc/config/oor' (by default), use the UCI CLI application,\nor use the web interface (if available). The configuration fields are analogue\nto those in the 'oor.conf' file.\n\nAndroid\n-------\n\nOpen Overlay Router includes support for Android devices operating as LISP-MN.\nPlease see the [android/README.md](android/README.md) file to get details on\nOpen Overlay Router for Android installation, compilation and usage.\n\niOS\n---\n\nOpen Overlay Router includes support for iOS devices operating as LISP-MN.\nPlease see the [Apple/README.md](Apple/README.md) file to get details on\nOpen Overlay Router for iOS installation, compilation and usage.\n\nVPP\n---\n\nOpen Overlay Router has adopted VPP as a new data plane that can be used to \nencapsulate and decapsulate LISP traffic in a high performance rate.\nPlease see the VPP/README.md file to get details on how to configure OOR and\nVPP to work together. \n\nNAT traversal\n-------------\n\nSince version 1.1, Open Overlay Router includes experimental NAT traversal \ncapabilities for the modalities of xTR and MN (see LISP NAT traversal draft). \nIn order to use NAT traversal with Open Overlay Router you will need a MS and \nan RTR (Re-encapsulating Tunnel Router) that are NAT traversal capable. If you \nare using the beta-network, please take into account that, at the time of this \nwriting (release 1.1), not all devices on the beta-network have been updated \nto support NAT traversal yet.\n\n\nIf NAT traversal feature is enabled, Open Overlay Router is configured to send \nall data traffic through RTRs even if the interface has a public address. On its \ncurrent form, NAT traversal support on Open Overlay Router ignores IPv6 addresses \non RLOC interfaces, besides, the current NAT traversal implementation in the \nbeta-network only supports the registration of a single EID prefix per device. \n\nContact\n-------\n\nShould you have questions regarding the use of the Open Overlay Router distribution, \nplease subscribe to the users@openoverlayrouter.org mailing list and ask there\n(http://mail.openoverlayrouter.org/mailman/listinfo/users).\n\nIf you wish to participate in the development of Open Overlay Router, use the \ndedicated mailing list, devel@openoverlayrouter.org \n(http://mail.openoverlayrouter.org/mailman/listinfo/devel).\n\nAdditionally, important announcements are sent to the low volume mailing list\nannounce@openoverlayrouter.org \n(http://mail.openoverlayrouter.org/mailman/listinfo/announce).\n\nMore interactive help can sometimes be obtained on the '#openoverlayrouter' IRC channel on\nFreeNode.\n\nBugs you encounter should be filed at the [repository's issue tracker on\nGithub](https://github.com/OpenOverlayRouter/oor/issues).\n","funding_links":[],"categories":["C"],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FOpenOverlayRouter%2Foor","html_url":"https://awesome.ecosyste.ms/projects/github.com%2FOpenOverlayRouter%2Foor","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2FOpenOverlayRouter%2Foor/lists"}