<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hi Rod, <br>
<br>
Your diagram is correct. You have more information of how nat
works <a
href="https://tools.ietf.org/html/draft-ermagan-lisp-nat-traversal-11">here</a>.
I think that Cisco boxes implements version 2 of this draft. Our
xTR implementation is a mix of 2 and 10. <br>
Regarding our Map Server implementation, as we don't support NAT
traversal, the code discards these messages. The MS/MR sg-nus-pxtr
has NAT support if you want to have a try.<br>
<br>
Best regards<br>
<br>
Albert<br>
<br>
<br>
On 10/10/16 11:50, Rod Dines wrote:<br>
</div>
<blockquote
cite="mid:CAAG27YJwcnqX7117QAXo-6cVzaMa4xwSsc5nRM6FsUy6poJTcg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div style="font-size:12.8px">Sorry errors in the fifth and
sixth line in my scenario:</div>
<div style="font-size:12.8px"><br>
</div>
<div style="font-size:12.8px">xTR-MN --> NAT -->
Info-Request (type 7) --> MSMR Map Server </div>
<div style="font-size:12.8px">xTR-MN --> NAT -->
Info-Reply (with RTRs) <-- MSMR Map Server<br>
</div>
<div style="font-size:12.8px">xTR-MN --> NAT --> ECM
Data-Map_Reg --> RTR <br>
</div>
<div style="font-size:12.8px">
RTR --> Map_Reg (RTR
RLOC) --> MSMR (Map Server on LISP-BETA)<br>
</div>
<div style="font-size:12.8px">
RTR <-- ECM
(Data_Map_Notify(RTR RLOC)) <-- MSMR (Map Server on
LISP-BETA)<br>
</div>
<div style="font-size:12.8px">xTR-MN <-- NAT <--
Map_Notify <-- RTR<br>
</div>
<div style="font-size:12.8px">xTR-MN --> NAT --> ECM Data
--> RTR --> DATA OUT (to LISP direct
or legacy via PETR)<br>
</div>
<div style="font-size:12.8px">xTR-MN --> NAT <-- ECM Data
<-- RTR <-- DATA IN (from LISP direct
or legacy via PITR)<br>
</div>
<div><br>
</div>
<div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Rod Dines</b> <span
dir="ltr"><<a moz-do-not-send="true"
href="mailto:murdoch.edu.au@roddines.com">murdoch.edu.au@roddines.com</a>></span><br>
Date: 10 October 2016 at 17:45<br>
Subject: Re: A LISP Map Server that supports Info-Request and
Info-Reply messages?<br>
To: Albert López <<a moz-do-not-send="true"
href="mailto:alopez@ac.upc.edu">alopez@ac.upc.edu</a>><br>
Cc: <a moz-do-not-send="true" href="mailto:users@lispmob.org">users@lispmob.org</a><br>
<br>
<br>
<div dir="ltr">Hi Albert:
<div><br>
</div>
<div>Thanks for the fast response and I will join the new
mail list.<br>
<div><br>
</div>
<div>I understand that you only have support for NAT in
xTR but I am under the impression that an xTR (MN)
behind a NAT sends an Info-Request to a Map-Server to
initiate a Info-Reply by the Map Server to establish the
NAT info and a list of RTR's. Is this not correct?</div>
<div><br>
</div>
<div>My scenario:</div>
<div><br>
</div>
<div>xTR-MN --> NAT --> Info-Request (type 7)
--> MSMR Map Server </div>
<div>xTR-MN --> NAT --> Info-Reply (with RTRs)
<-- MSMR Map Server<br>
</div>
<div>xTR-MN --> NAT --> ECM Data-Map_Reg -->
RTR <br>
</div>
<div>
RTR --> Map_Reg (RTR RLOC) -->
MSMR (Map Server on LISP-BETA)<br>
</div>
<div>
RTR <-- Map_Notify(RTR RLOC) <--
MSMR (Map Server on LISP-BETA)<br>
</div>
<div>xTR-MN --> NAT --> ECM Data-Map_Reg -->
RTR <br>
</div>
<div>xTR-MN --> NAT --> ECM Data
--> RTR --> DATA OUT (to LISP direct or legacy
via PETR)<br>
</div>
<div>xTR-MN --> NAT <-- ECM Data
<-- RTR <-- DATA IN (from LISP direct or legacy
via PITR)<br>
</div>
<div><br>
</div>
<div>The source for the OOR map server receive-message
handler as follows does not support this.</div>
<div><br>
</div>
<div>
<div>static int</div>
<div><span style="background-color:rgb(255,255,0)">ms_recv_msg(</span>oor_ctrl_dev_t
*dev, lbuf_t *msg, uconn_t *uc)</div>
<div>{</div>
<div> int ret = BAD;</div>
<div> lisp_msg_type_e type;</div>
<div> lisp_ms_t *ms;</div>
<div><br>
</div>
<div> ms = lisp_ms_cast(dev);</div>
<div> type = lisp_msg_type(msg);</div>
<div><br>
</div>
<div> if (type == LISP_ENCAP_CONTROL_TYPE) {</div>
<div> if (lisp_msg_ecm_decap(msg, &uc->rp)
!= GOOD)</div>
<div> return (BAD);</div>
<div> type = lisp_msg_type(msg);</div>
<span class="gmail-">
<div> }</div>
<div><br>
</div>
<div> switch(type) {</div>
<div> case LISP_MAP_REQUEST:</div>
<div> ret = ms_recv_map_request(ms, msg, uc);</div>
<div> break;</div>
<div> case LISP_MAP_REGISTER:</div>
<div> ret = ms_recv_map_register(ms, msg, uc);</div>
<div> break;</div>
<div> case LISP_MAP_REPLY:</div>
<div> case LISP_MAP_NOTIFY:</div>
<div> case LISP_INFO_NAT:</div>
<div> OOR_LOG(LDBG_3, "Map-Server: Received
control message with type %d."</div>
<div> " Discarding!", type);</div>
<div> break;</div>
</span>
<div> default:</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</div>
<div class="gmail-HOEnZb">
<div class="gmail-h5">
<div class="gmail_extra"><br>
<div class="gmail_quote">On 10 October 2016 at 17:19,
Albert López <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:alopez@ac.upc.edu" target="_blank">alopez@ac.upc.edu</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px
0px 0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<div
class="gmail-m_1537562624030189278m_2841027481310102314moz-cite-prefix">Hi
Rod,<br>
<br>
We only have support for NAT in xTRs. The
support of nat traversal in Map Servers and RTRs
is not yet implemented. Some Cisco boxes have
support for NAT but is not official and have
some limitations (only one xTR behind the same
NAT). The RTR implementation of OOR is only
supporting ELPs (Explicit Locator Path). If you
are interested in this functionality and can
give you some examples. <br>
On the other hand, would you mind to use the new
<a moz-do-not-send="true"
href="https://github.com/OpenOverlayRouter/oor/wiki/Mailing-lists"
target="_blank">mailing list</a>? We are
trying to do a rebrand of the project.<br>
<br>
Thanks<span
class="gmail-m_1537562624030189278HOEnZb"><font
color="#888888"><br>
<br>
Albert</font></span>
<div>
<div class="gmail-m_1537562624030189278h5"><br>
<br>
<br>
<br>
<br>
On 10/10/16 10:36, Rod Dines wrote:<br>
</div>
</div>
</div>
<div>
<div class="gmail-m_1537562624030189278h5">
<blockquote type="cite">
<div dir="ltr"><br clear="all">
<div>Hi Albert/Others:</div>
<div><br>
</div>
<div>While I have had some success
(crashes after an approx an hour) I
can't seem to get Lisp-MN behind a NAT
sorted out at all. I assumed the
OOR-MSMR could handle the Info-Request
and Info-Reply but it returns a
discarding error and inspecting source
appears to not have any implementation</div>
<div><br>
</div>
<div>
<div>switch(type) {</div>
<div> case LISP_MAP_REQUEST:</div>
<div> ret =
ms_recv_map_request(ms, msg, uc);</div>
<div> break;</div>
<div> case LISP_MAP_REGISTER:</div>
<div> ret =
ms_recv_map_register(ms, msg, uc);</div>
<div> break;</div>
<div> case LISP_MAP_REPLY:</div>
<div> case LISP_MAP_NOTIFY:</div>
<div><span
style="background-color:rgb(255,255,0)">
case LISP_INFO_NAT:</span></div>
<div><span
style="background-color:rgb(255,255,0)">
OOR_LOG(LDBG_3, "Map-Server:
Received control message with type
%d."</span></div>
<div><span
style="background-color:rgb(255,255,0)">
" Discarding!",
type);</span></div>
<div> break;</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>I also find that implementing a RTR
configuration is far from clear. Do you
have any example configurations or
tutorials? Or am I just looking to do
something not yet sorted out?</div>
<div><br>
</div>
<div>If a NATed MN is possible can you
please explain how am I suppose to get a
MSMR that will help me determine the NAT
configuration and work with a RTR list?
Does Cisco do it in their IOS version?
Is there an older or forked version of
oor or lispmob source I should be using?</div>
<div><br>
</div>
<div>Do you have any further info besides
you published papers on the RTR. I have
the slides and whitepaper from the
LispMob site.</div>
<div><br>
</div>
<div>Regards, Rod,</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<br clear="all">
<div><br>
</div>
-- <br>
<div
class="gmail-m_1537562624030189278m_2841027481310102314gmail_signature">
<div dir="ltr"><span
style="font-size:12.8px">Rod Dines</span><br
style="font-size:12.8px">
Honours in Internetworking and Network
Security Research<br
style="font-size:12.8px">
<span style="font-size:12.8px">Perth,
Western Australia</span><br
style="font-size:12.8px">
<span style="font-size:12.8px"><a
moz-do-not-send="true"
href="tel:%2B61-449891222"
value="+61449891222"
target="_blank">+61-449891222</a></span><br
style="font-size:12.8px">
<span style="font-size:12.8px"><span
class="gmail-TSRSpan"
id="gmail-TSRSpan_11"><img
moz-do-not-send="true"
class="gmail-TSRWebRatingIcon"
style="width: 16px; height:
16px; border: 0px;"></span><span
class="TSRSpan" id="TSRSpan_12"><img
moz-do-not-send="true"
class="TSRWebRatingIcon"
src="chrome-extension://ohhcpmplhhiiaoiddkfboafbhiknefdf/TMToolbar/image/tooltip/webicon_gray.png"
style="width: 16px; height:
16px; border: 0px;"></span><a
moz-do-not-send="true"
href="http://www.roddines.com"
target="_blank"
style="background-color:rgb(189,189,189)">www.roddines.com</a></span><br>
</div>
</div>
</div>
</blockquote>
<br>
<p><br>
</p>
</div>
</div>
<pre class="gmail-m_1537562624030189278m_2841027481310102314moz-signature" cols="72">--
</pre>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail-m_1537562624030189278gmail_signature">
<div dir="ltr"><span style="font-size:12.8px">Rod
Dines</span><br style="font-size:12.8px">
Honours in Internetworking and Network Security
Research<br style="font-size:12.8px">
<span style="font-size:12.8px">Perth, Western
Australia</span><br style="font-size:12.8px">
<span style="font-size:12.8px"><a
moz-do-not-send="true"
href="tel:%2B61-449891222" value="+61449891222"
target="_blank">+61-449891222</a></span><br
style="font-size:12.8px">
<span style="font-size:12.8px"><a
moz-do-not-send="true"
href="http://www.roddines.com" target="_blank">www.roddines.com</a></span><br>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature">
<div dir="ltr"><span style="font-size:12.8px">Rod Dines</span><br
style="font-size:12.8px">
Honours in Internetworking and Network Security Research<br
style="font-size:12.8px">
<span style="font-size:12.8px">Perth, Western Australia</span><br
style="font-size:12.8px">
<span style="font-size:12.8px">+61-449891222</span><br
style="font-size:12.8px">
<span style="font-size:12.8px"><a moz-do-not-send="true"
href="http://www.roddines.com" target="_blank">www.roddines.com</a></span><br>
</div>
</div>
</div>
</blockquote>
<br>
<br>
</body>
</html>