Dear Daniele,

Just to inform other members of the community. The map server where you were registering doesn't accept mobile nodes. When the node is compiled as a mobile node (make without specifying platform) the map register has a bit which indicates to the map server that the node is a mobile node. As the map server doesn't accept the mobile node you wasn't able to register to the system.

On the other side, I have seen that when we ask to all the map resolvers for the EID 153.16.44.120, you only obtain answer from the map registers where you registered that EID. We will notify this behaviour to beta network members to try to resolve this situation.

Regards

Albert

On 05/17/2013 10:49 AM, Daniele wrote:
Thanks for the opportunity, I'm in the chat room right now, my nickname is tarcleti.

Regards
Daniele


On 17/mag/2013, at 09:33, Albert López wrote:

Dear Daniele,

From the logs I can see that you doesn't receive a request of you EID from EID 153.16.22.65 and 153.16.22.201. I propose you to connect to our channel in the IRC: '#lispmob' IRC channel on FreeNode to evaluate what could happen and do some tests connecting to our EIDs.

Regards

Albert L.




On 05/16/2013 07:42 PM, Daniele wrote:
Dear all,
I really thank you for all your replies.

I'm trying to isolate the problem one step at once, so in this moment I left connected just the LISPmob client and I completely disconnected the openLISP xTR (EID 153.16.44.112/29 -> RLOC 151.100.122.9).

The LISPmob client's EID is 153.16.44.120/32, it is connected to the physical interface eth0 with the RLOC 151.100.122.234, and its gateway is 151.100.122.1.

I started the lispd daemon and I performed a ping to 3 different EIDs I found in the LISP site: 153.16.10.11, 153.16.22.65, 153.16.22.201. Only the first one worked. Can you try if you can ping them all? I attach the debug (level 2) of lispd.

I want to be sure that the LISPmob client is working fine, after that I'll need to focus to let it communicate with the openLISP xTR.

Thanks again
Daniele






On 16/mag/2013, at 18:22, Albert López wrote:

Dear Daniele,

Could you provide me with the full network configuration of your testbed? IPs, gateways, diagram, how the three elements are interconnected. For the information you are providing, it seems that you have a misconfiguration of your network. If LISPmob and the other PC only have connectivity when openLISP has done the initial ping, it makes me think that they "reach" Internet through openLISP. This is the reason we would like to have the complete diagram of the testbed in order to clarify this situation.

Albert


On 05/16/2013 05:45 PM, Daniele wrote:
I'm thinking to give up! :(

Testing and testing on different EIDs this is what i figured out:

This is my situation here in the lab: I have 3 systems:
1- LISPmob client
2- the openLISP xTR of the other testbed
3- another pc NOT connected to the LISP network..

All these 3 systems go out through a switch and an ethernet interface.

With the openLISP xTR (which is the only one which works) I can ping any EID, but once I do that, I can ping those addresses also from the other hosts that before couldn't ping them, even the one which is not connected to the LISP network!

So actually the LISPmob client is still not working as it should, it works only after I use the openLISP xTR to do the ping, and it basically uses the underlying network like the pc NOT connected to the LISP network.

It's hard to explain, I hope you can understand the problem and help me.

Thanks for the patience.
Daniele



On 16/mag/2013, at 16:38, Albert López wrote:

Here <http://www.lisp4.net/lisp-site/> you can find all the sites which are registered in beta network. You could try to ping one of them. Even they are up, it could be that they don't reply to ping. Try several ones. Again, I would need the debug logs and a wireshark trace from both sides of the testbed (if the second one use LISPmob). Please set the proxy-reply of the configuration file to off in order we could see that you are receiving the map reply. If in the other part of the testbed you are using LISPmob, try to use the new release.

Albert


On 05/16/2013 04:12 PM, Daniele wrote:
Ok, I can ping 153.16.10.11, but the brainstorming is not over.. the EID 153.16.38.132 maybe is down, but do you have some other EID I can try? Because here in the lab I have another LISP testbed (153.16.44.112/29) and with it I can also ping the 153.16.10.11, but not the 153.16.44.120, which is the lisp mob client i am configuring!

The communication between these two sites is the only thing I care, and it is not working!

Daniele



On 16/mag/2013, at 15:26, Albert López wrote:

Hi Daniele,

We have tried to ping the same host than you and we have realized that this host doesn't reply to ping. You could try to ping 153.16.10.11 which is the EID of the www.lisp4.net web page. I hope this one will reply the ping as it has done for us.

Regards

Albert

On 05/16/2013 01:25 PM, Daniele wrote:
Of course thanks, what do you want me to capture? Do I filter the port 4342 for the interfaces while i try a ping?

Thanks
Daniele



On 16/mag/2013, at 13:22, Albert López wrote:

Could you send us a wireshark capture of all interfaces and send us the logs with debug level 3?

Thanks

Albert


On 05/16/2013 01:18 PM, Daniele wrote:

Yes I configured the sysctl options as in the read me file.

On May 16, 2013 1:13 PM, "Alberto Rodriguez-Natal" <[email protected] <mailto:[email protected]>> wrote:

    Hi Daniele,

    I'm assuming that those ping replies that you see on the
    eth0 interface are LISP encapsulated. I don't know if
    you have already check this but, it's the sysctl
    configuration for IP forwarding and rp_filter correct?

    Check the README file on section "Running LISPmob" and
    let us know.

    Best,
    Alberto

    P.S. Thanks Teto for explaining how to get the new
    release alongside with the old one ;)

    On 16 May 2013 13:01, Daniele <[email protected]
    <mailto:[email protected]>> wrote:

        I updated to the 0.3.2 version, same as before. I
        can see that the /32 EID is registered in the map
        server with the correct RLOC, but any ping to it
        doesn't work.

        :(

        This is my lisped.conf file, I'm sure that the 4341
        and 4342 ports are completely open.
        What else can I check?

        Thanks
        Daniele





        On 16/mag/2013, at 11:15, Teto wrote:

        > follow the instructions here to download master
        from git:
        > http://lispmob.org/downloads/linux : something like
        > "git clone git://github.com/LISPmob/lispmob.git
        <http://github.com/LISPmob/lispmob.git> lispmob0.3.2"
        > then you cd lispmob0.3.2, type "make" and it will
        generate an
        > executable in the lispd subdirectory. Be sure to
        call the executable
        > with absolute path otherwise it might call a
        previously installed
        > lispmob.
        >
        > On Thu, May 16, 2013 at 10:54 AM, Daniele
        <[email protected] <mailto:[email protected]>>
        wrote:
        >> Ok, I'll try that, can I install it on top of the
        current version?
        >>
        >> Thanks
        >> Regards
        >> Daniele
        >>
        >>
        >> On 16/mag/2013, at 10:47, Albert López wrote:
        >>
        >> Yesterday we released version 0.3.2. This wan
        announced in the mailing list
        >> [email protected]
        <mailto:[email protected]>. If you are not in
        this mailing list, we encourage you
        >> to subscribe.
        >>
        >> Best regards
        >>
        >> Albert
        >>
        >>
        >> On 05/16/2013 10:42 AM, Daniele wrote:
        >>
        >> Uhm.. What new release do you mean? I'm using the
        0.3 versoin right now..
        >>
        >>
        >> 2013/5/16 Albert López <[email protected]
        <mailto:[email protected]>>
        >>>
        >>> Hi Daniele,
        >>>
        >>> Could you try with the new LISPmob release.
        Remember to follow all the
        >>> instructions of the README any check the FAQ file.
        >>>
        >>> Regards
        >>>
        >>> Albert
        >>
        >>
        >>













Reply via email to