Oh, thanks!

See you soon.

Musab

Sent from Samsung Mobile

-------- Original message --------
From: Lori Jakab <[email protected]> 
Date: 18/08/2014  13:38  (GMT+00:00) 
To: MUSAB MUHAMMAD <[email protected]>,Alberto Rodriguez-Natal 
<[email protected]> 
Cc: [email protected],Lori Jakab <[email protected]> 
Subject: Re: [LISPmob-users] Running LISP MN on IPv6 Networks 
 
I'll be back tomorrow

-Lori (from a LISP-MN phone)

On August 18, 2014 1:06:13 PM CEST, MUSAB MUHAMMAD <[email protected]> wrote:
Hi Alberto,

Thanks for the reply. How soon do you think he will be back? I have a paper 
submission deadline for 24th of August and wanted to run some tests on the LISP 
MN protocol to include it in my analysis, the sooner I can get it working the 
better.

Regards,
 
Musab Isah
Research Student,
School of Computing and Communications,
D29, InfoLab21
Lancas! ter University


On Monday, August 18, 2014 10:45 AM, Alberto Rodriguez-Natal 
<[email protected]> wrote:


Hi Musab,

Thank you for the details. As you said, Lori is away rigth now but he should be 
back soon. He will then re-allocate your EID ASAP. If that doesn't work please 
come back to us and we'll try to find out what's happening. 

Thanks,
Alberto


On Wed, Aug 13, 2014 at 5:51 PM, MUSAB MUHAMMAD <[email protected]> wrote:
Hi Alberto,

Actually before even the handover I don't have any communication going on most 
of the times. My node will have connectivity but as soon as LISP daemon is 
started, no communication is possible afterwards (no pings, no browsing, 
nothing). Now even the few times that we get the connectivity a simple 
horizontal handover means losing connectivity and coming back to the previous 
network will not solve the problem. In simple terms, LISP is not really working 
for me on IPv6 network and hopefully we can continue the troubleshooting from 
where we stop with Lori. And by the way, I have installed the latest release of 
the protocol.

I have no problem communicating with other LISP-based nodes, as I was able to 
ping an EID provided by Lori, but communicating with non-LISP systems seems to 
be the problem we have. I tried all the available petr/pitr in the example conf 
file but to no success. Lori was to add my EID in one of the tunnel routers to 
see if that makes communication possible but he, obviously, went on leave 
before doing that.

Regards,
 
Musab Isah
Research Student,
School of Computing and Communications,
D29, InfoLab21
Lancaster University


On Wednesday, August 13, 2014 3:15 PM, Alberto Rodriguez-Natal 
<[email protected]> wrote:


Hi Musab,

Sorry for the late reply, the LISPmob team is currently on vacation, so expect 
some delay on our responses.

Could you please let us know which kind of handover did you try to attempt? A 
simple switch of wireless access point using the same wlan interface 
(horizontal handover) or an inter-technology movement from, for instance, a 
wifi interface to a 3g interface (vertical handover)?

Thanks,
Alberto


On Mon, Aug 11, 2014 at 2:06 PM, MUSAB MUHAMMAD <[email protected]> wrote:
Hi all,

I have set up LISP MN on a native IPv6 network and have all configurations 
(hopefully) correctly set up. My mobile node only seems to have Internet 
connection when the lispd is started, but disconnect from network once a 
handover is attempted. Even the connection at the start of the lisp daemon is 
not guaranteed as more often than not, no communication is achieved once the 
daemon starts. I tried with all the available petr/pitr on the 
lispd.conf.example file but to no avail.

I have a perfectly working network, until the lisp daemon is started and my 
conclusion is that there is a problem with LISP overlay network itself. Is 
there anyone here please, that has LISP MN working on a native IPv6 network? 
I'll be glad, if there is, to please share your experience with me.

I attached my configuration and log files, hopefully someone can direct me of 
what to do next or discover any problem with my connectivity.

Regards,
 
Musab Isah
Research Student,
School of Computing and Communications,
D29, InfoLab21
Lancaster University






Reply via email to