Hi Dino,
The version of NAT traversal implemented by OOR follows
draft-ermagan-lisp-nat-traversal. More exactly, it implements version 2
of the draft which is the version supported by the routers of LISP beta
network. If remember correctly, your NAT traversal implementation uses
info request/reply to maintain the hole in the NAT box. We are using EMR
and data Map Notify so I believe the implementations wouldn't be
interoperable. Unfortunately we are yet to test it since we are short in
time at this moment.
Best regards
Albert
On 07/06/16 16:17, Dino Farinacci wrote:
How well does your NAT traversal implementation interoperate with mine?
Dino
On Jun 7, 2016, at 4:40 AM, Albert López<alo...@ac.upc.edu> wrote:
Hi all,
The OpenOverlayRouter community is proud to announce the availability of OOR
1.1! This new version introduces NAT traversal support for OOR, along with
several bugfixes. Try it out here [1].
We are also proud to announce that the Android flavor of OOR has been
officially released in the Google Play store. You can get the app here [2].
Feel free to try the new release and send us any comment or feedback through
the mailing lists [3]!
Thanks,
The OOR team
[1]https://github.com/OpenOverlayRouter/oor/wiki/Downloads
[2]https://play.google.com/store/apps/details?id=org.openoverlayrouter.noroot
[3]https://github.com/OpenOverlayRouter/oor/wiki/Mailing-lists
_______________________________________________
announce mailing list
annou...@openoverlayrouter.org
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/announce
_______________________________________________
Users mailing list
Users@openoverlayrouter.org
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@openoverlayrouter.org
http://mail.openoverlayrouter.org/cgi-bin/mailman/listinfo/users
