Hi Yu-hyun,

I think that you have some basic conceptual errors. A LISP mobile node (MN) is like an xTR (tunnel router) but in an end host. When a host implements LISP-MN, it is able to encapsulate its own traffic into lisp packets so it doesn't need an xTR. You can check this <http://lispmob.org/sites/default/files/users/user1/documents/LISPmob_Whitepaper.pdf> paper for more information. I have also seen that you use EIDs as RLOCs. This is wrong except you are trying to do advanced scenarios like LISP over LISP. The EIDs identify hosts, and are assigned independently of the network topology while RLOCs identify network attachment points, and are used for routing. Sites of the Map Server are used to indicate the EIDs that can be registered to the Map Server but not RLOCs. If you are trying to do an advanced scenario, please let me know which is your schema of your testbed explaining with detail what you are trying to do.

Best regards

Albert

El 04/01/16 a les 17:46, 신유현 ha escrit:

Hello,

I have tried to make a simple local test-bed and xTR received no packets from MN. The scenario i have tried is as follows : There are two MN(say MN_1 and MN_2), two xTR(say xTR_1 and xTR_2) and one MS. I have expected MN_1 and MN_2 exchanges packets through xTR_1 and xTR_2, but when i sent a ping from one MN to the other,it seemd like xTR_1 and xTR_2 were not used. At the mapserver, the locator of MN_1 and MN_2 were ip address of MN_1 and MN_2 each, not ip address of xTR_1 and xTR_2.

Google drive link to my configuration files for local scenario : https://drive.google.com/folderview?id=0B3SRnMyDZ_PIQUJvMWlFLTJ2bVE&usp=sharing

I have tried modifying configuration files, but failed to register xTR's ip address as locater of MN nodes and the only locater registered at the local mapserver for MN_1/MN_2 node was ip address of MN_1/MN_2. I suspect that my configuration is not correct.

Regards,

Yu-hyun.


Reply via email to