Hi Albert, > If I understood correctly, you have found this segmentation fault when using > IPv6 EIDs > over IPv4 RLOCs? No, I have an Access Router (an Ubuntu box) with egress wired interface connected to IPv4 public network. The interface has an IPv6 connectivity using a tunnel broker service provided by hurricane electric. The AR has its wireless interface providing only IPv6 connectivity to local mobile nodes. Now my lisp MN is connected to this AR and has no direct access to any IPv4 network.
>Could you send the logs at
level 2 when this bug is produced?
Unfortunately I am not saving the logs, I just read them at run time. But I was
pinging a known IPv6 address when it crashed, so I decided to ping a different
one this time (Facebook IPv6 address); and it crashed again, see debug 2 and 3
here lisp segfault - Pastebin.com. I have recently changed the petr on the conf
file, find attached the recent one.
Thanks alot,
lisp segfault - Pastebin.com
root@lispmn:/home/lisp-mn# lispd -f /etc/lispd.conf INFO: LISPmob v0.4 compiled
for Linux INFO: Rights: Effective [4294967295] Permitted [4294967295]
View on pastebin.com Preview by Yahoo
Musab Isah
Research Student,
School of Computing and Communications,
D29, InfoLab21
Lancaster University
On Wednesday, July 9, 2014 5:17 PM, Albert López <[email protected]> wrote:
Hi Musab,
First of all, thank you very much for your feed back. It is very
important for us to improve LISPmob.
If I understood correctly, you have found this segmentation fault
when using IPv6 EIDs over IPv4 RLOCs? Could you send the logs at
level 2 when this bug is produced? I have tried to reproduce it
without success. The configuration file is the same you sent me in
a previous mail? The segmentation fault is produced when you ping
a specific destination or is in general?
Thanks again for your support
Regards
Albert
On 07/09/2014 03:20 PM, MUSAB MUHAMMAD wrote:
Hi all,
>
>
>I have sent a message above about the problem I am having using LISP on IPv6.
>I was having a segfault issue whenever I start the lisp daemon and attempt to
>ping or browse a site. This happen when the IPv6 network is tunnelled through
>IPv4 network. After troubleshooting the problem with Lori and florinc on
>freenode chat, we realised that the 'map_cache_entry->mapping' is a NULL
>pointer and was causing the segmentation fault. Please see the crash report
>here gdb lisp-crash report - Pastebin.com and here to see the null pointer
>(gdb) print map_cache_entry $1 = (lispd_map_cache_entry *) 0x8370258 (gdb) pri
>- Pastebin.com
>
>
>Regards,
>
>
>
>
>
>
>gdb lisp-crash report - Pastebin.com
>GNU gdb (Ubuntu/Linaro 7.4-2012.04-0ubuntu2.1) 7.4-2012.04 Copyright (C) 2012
>Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later
><http://gnu....
>
>
>View on pastebin.com Preview by Yahoo
>
>
>
>
>
>
>(gdb) print map_cache_entry $1 = (lispd_map_cache_entry ...
>(gdb) print map_cache_entry $1 = (lispd_map_cache_entry *) 0x8370258 (gdb)
>print map_cache_entry->mapping $2 = (lispd_mapping_elt *) 0x0 (gdb) print
>map_cache_entry...
>
>
>View on pastebin.com Preview by Yahoo
>
>
>
>
>
>Musab Isah
>
>Research Student,
>School of Computing and Communications,
>D29, InfoLab21
>Lancaster University
lispd.conf
Description: Binary data
