Package: openoverlayrouter Version: 1.2.0+ds1-1 Architecture: amd64 Maintainer: Debian IoT Maintainers Installed-Size: 383 Depends: libc6 (>= 2.15), libconfuse1 (>= 3.0+dfsg~), libxml2 (>= 2.7.4), libzmq5 (>= 3.2.3+dfsg) Filename: ./amd64/openoverlayrouter_1.2.0+ds1-1_amd64.deb Size: 136626 MD5sum: 780f1a7c8c0d579363ffcc562a5b6461 SHA1: 29ae2fd8fbc615cf9c244a9388b6e74f3c630b1c SHA256: c6963056453fc8752ce57dbf33acfffa9be597f01727b1c27c5d3dd656282440 Section: misc Priority: optional Homepage: http://openoverlayrouter.org/ Description: deploy programmable overlay networks The OpenOverlayRouter (OOR) project aims to deliver a flexible and modular open-source implementation to deploy programmable overlay networks. It leverages on encapsulating overlay-specific packets into underlay-compatible packets at the edges of the instantiated overlay and route them over the physical underlying infrastructure. In order to do so, it maps overlay identifiers to underlay locators and keeps those mappings updated over time. In the current version, OOR uses the LISP protocol for the control-plane (e.g. mapping retrieval and updating, etc), NETCONF/YANG for the management-plane (e.g. overlay identifiers provisioning, etc) and can use both LISP and VXLAN-GPE headers for encapsulation. Package: openoverlayrouter Version: 1.2.0+ds1-1 Architecture: i386 Maintainer: Debian IoT Maintainers Installed-Size: 438 Depends: libc6 (>= 2.15), libconfuse1 (>= 3.0+dfsg~), libxml2 (>= 2.7.4), libzmq5 (>= 3.2.3+dfsg) Filename: ./i386/openoverlayrouter_1.2.0+ds1-1_i386.deb Size: 153582 MD5sum: bc9a0ec266047e54561d48e1f917fbb9 SHA1: b95f13d1daa2d477cd5774a718ce3e5e6665d213 SHA256: dcae2fd8807051b2c45670356a6b990d8e1ea56de2a4e41d8cc5cfbb650bb0ee Section: misc Priority: optional Homepage: http://openoverlayrouter.org/ Description: deploy programmable overlay networks The OpenOverlayRouter (OOR) project aims to deliver a flexible and modular open-source implementation to deploy programmable overlay networks. It leverages on encapsulating overlay-specific packets into underlay-compatible packets at the edges of the instantiated overlay and route them over the physical underlying infrastructure. In order to do so, it maps overlay identifiers to underlay locators and keeps those mappings updated over time. In the current version, OOR uses the LISP protocol for the control-plane (e.g. mapping retrieval and updating, etc), NETCONF/YANG for the management-plane (e.g. overlay identifiers provisioning, etc) and can use both LISP and VXLAN-GPE headers for encapsulation. Package: openoverlayrouter-dbgsym Source: openoverlayrouter Version: 1.2.0+ds1-1 Auto-Built-Package: debug-symbols Architecture: amd64 Maintainer: Debian IoT Maintainers Installed-Size: 578 Depends: openoverlayrouter (= 1.2.0+ds1-1) Filename: ./amd64/openoverlayrouter-dbgsym_1.2.0+ds1-1_amd64.deb Size: 525856 MD5sum: 6504bb0e44b6f0af6fb0a190ff7af1d7 SHA1: 7ec79e08a862e57222e7cd3c88ca0bec405bb14f SHA256: 075b70a9375fd53b9fec19706647db13865357f863920f49158d3dd64434c120 Section: debug Priority: extra Homepage: http://openoverlayrouter.org/ Description: Debug symbols for openoverlayrouter Build-Ids: a2d4906a3f934abdb1c8dfd3485a1fea3e91c1aa Package: openoverlayrouter-dbgsym Source: openoverlayrouter Version: 1.2.0+ds1-1 Auto-Built-Package: debug-symbols Architecture: i386 Maintainer: Debian IoT Maintainers Installed-Size: 498 Depends: openoverlayrouter (= 1.2.0+ds1-1) Filename: ./i386/openoverlayrouter-dbgsym_1.2.0+ds1-1_i386.deb Size: 456284 MD5sum: 27a3e740dd34a7cb22e7ade61ab7fd56 SHA1: bbc0d8b0ba5e50653b595baa2694edce4683bcf2 SHA256: 5bfd3b6997cc454c8e60488dc14b5d8a65465d12f9c62c70481f1b983dd6ef54 Section: debug Priority: extra Homepage: http://openoverlayrouter.org/ Description: Debug symbols for openoverlayrouter Build-Ids: 5e585e35cde10e24572221d8c434a9ec5650c86d