Hi Albert, I have a simple topology involving 2 Access Routers and one LISP mobile node (MN). The MN has Internet connectivity via both the ARs without any problem. The Intention is to start LISP MN and move between these ARs so that the MN can autoconfigure new RLOCs as the 2 routers advertise different prefixes. Now the difficulty I am having is that the MN cannot communicate once LISP daemon is started althoug It works fine with IPv4 RLOCs and EID but not when IPv6 is involved. It sends map register and receive map notify as you will see from the log but nothing further than that.
I have attached my conf and log files as requested. Regards, Musab Isah Research Student, School of Computing and Communications, D29, InfoLab21 Lancaster University On Monday, September 1, 2014 12:12 PM, Albert López <[email protected]> wrote: Hi Musab, Sorry for the delay. I have been on holidays. I have tested IPv6 EIDs over IPv4 and IPv6 rlocs without problems. Most part of the tests have been done in a local testbed but we also have done some test with real EIDs. Could you provide me with more details of your scenario, configuration files, logs... Regards Albert On 28/08/14 13:09, MUSAB MUHAMMAD wrote: Hi all, > > >Today I ran LISP MN on an IPv4 network using IPv4 EIDs and it worked fine. I >tried to run it with IPv6 EID on top of IPv4 network, which used to work >before, but it didn't. Is there anyone out there that has LISP MN with IPv6 >EID working on top either IPv4 or IPv6 network so that we can learn from >him/her? I will consider silence/no-reply as NO. If there is none, then is it >safe to assume that LISP MN for IPv6 networks is currently not working? > > >Regards, > >Musab Isah > >Research Student, >School of Computing and Communications, >D29, InfoLab21 >Lancaster University > > > >On Tuesday, August 19, 2014 9:17 PM, Lori Jakab <[email protected]> wrote: > > > >Hi Musab, > > >I’m back in office, but I’m not sure what you mean by "Lori was to add my EID >in one of the tunnel routers to see if that makes communication possible”. I >don’t think we talked about re-allocation of your EID as Alberto suggests. I >looked at the IRC logs, but I’m still not sure what was I supposed to try. >Let’s talk on IRC, or give me a bit more detail. > > >-Lori > > >On Aug 18, 2014, at 4:21 PM, Musab Isah <[email protected]> wrote: > > > >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 >>> >>> >>> >> >> >> > > >
lispd.conf
Description: Binary data
root@lispmn:/etc# lispd -f /etc/lispd.conf INFO: Processing configuration file /etc/lispd.conf DEBUG: RLOC Probing Interval: 30 DEBUG: converted addr_str [2001:4c08:2016:2064::2] to address [2001:4c08:2016:2064::2] DEBUG: Added 2001:4c08:2016:2064::2 to map-resolver list DEBUG: converted addr_str [84.88.16.10] to address [84.88.16.10] DEBUG-3: lookup_referral_cache_exact_node: The entry 0.0.0.0/0 is not found in the referral cache DEBUG-2: Added referral cache entry for EID: 0.0.0.0/0 DEBUG-3: add_locator_to_mapping: The locator 84.88.16.10 has been added to the EID 0.0.0.0/0. DEBUG-3: lookup_referral_cache_exact_node: The entry ::/0 is not found in the referral cache DEBUG-2: Added referral cache entry for EID: ::/0 DEBUG-3: add_locator_to_mapping: The locator 84.88.16.10 has been added to the EID ::/0. DEBUG: Added 84.88.16.10 to ddt root node list DEBUG: converted addr_str [2001:40B0:1::F0F2] to address [2001:40b0:1::f0f2] DEBUG-3: add_locator_to_mapping: The locator 2001:40b0:1::f0f2 has been added to the EID 0.0.0.0/0. DEBUG-3: add_locator_to_mapping: The locator 2001:40b0:1::f0f2 has been added to the EID ::/0. DEBUG: Added 2001:40B0:1::F0F2 to ddt root node list DEBUG: converted addr_str [2001:4f8:3:d::60] to address [2001:4f8:3:d::60] DEBUG-3: add_locator_to_mapping: The locator 2001:4f8:3:d::60 has been added to the EID 0.0.0.0/0. DEBUG: Added 2001:4f8:3:d::60 to proxy-etr list DEBUG: converted addr_str [69.31.31.98] to address [69.31.31.98] DEBUG: Added 69.31.31.98 to proxy-itr list DEBUG: converted addr_str [149.20.48.60] to address [149.20.48.60] DEBUG: Added 149.20.48.60 to proxy-itr list DEBUG: converted addr_str [198.6.255.37] to address [198.6.255.37] DEBUG: Added 198.6.255.37 to proxy-itr list DEBUG: converted addr_str [173.36.193.25] to address [173.36.193.25] DEBUG: Added 173.36.193.25 to proxy-itr list DEBUG: converted addr_str [129.250.1.63] to address [129.250.1.63] DEBUG: Added 129.250.1.63 to proxy-itr list DEBUG: converted addr_str [217.8.98.33] to address [217.8.98.33] DEBUG: Added 217.8.98.33 to proxy-itr list DEBUG: converted addr_str [217.8.98.35] to address [217.8.98.35] DEBUG: Added 217.8.98.35 to proxy-itr list DEBUG: converted addr_str [193.162.145.46] to address [193.162.145.46] DEBUG: Added 193.162.145.46 to proxy-itr list DEBUG: converted addr_str [158.38.1.92] to address [158.38.1.92] DEBUG: Added 158.38.1.92 to proxy-itr list DEBUG: converted addr_str [203.181.249.172] to address [203.181.249.172] DEBUG: Added 203.181.249.172 to proxy-itr list DEBUG: converted addr_str [202.51.247.10] to address [202.51.247.10] DEBUG: Added 202.51.247.10 to proxy-itr list DEBUG: converted addr_str [2001:590::451f:1f62] to address [2001:590::451f:1f62] DEBUG: Added 2001:590::451f:1f62 to proxy-itr list DEBUG: converted addr_str [2001:4f8:3:d::60] to address [2001:4f8:3:d::60] DEBUG: Added 2001:4f8:3:d::60 to proxy-itr list DEBUG: converted addr_str [2001:418:4:1:deaf:bebe::10d] to address [2001:418:4:1:deaf:bebe:0:10d] DEBUG: Added 2001:418:4:1:deaf:bebe::10d to proxy-itr list DEBUG: converted addr_str [2001:418:0:1000::613] to address [2001:418:0:1000::613] DEBUG: Added 2001:418:0:1000::613 to proxy-itr list DEBUG: converted addr_str [2001:200:e000:17::17] to address [2001:200:e000:17::17] DEBUG: Added 2001:200:e000:17::17 to proxy-itr list DEBUG: converted addr_str [2001:67C:21B4:108::b] to address [2001:67c:21b4:108::b] DEBUG: Added 2001:67C:21B4:108::b to proxy-itr list DEBUG: converted addr_str [2001:6c8:41:100:0:2:1:c] to address [2001:6c8:41:100:0:2:1:c] DEBUG: Added 2001:6c8:41:100:0:2:1:c to proxy-itr list DEBUG: converted addr_str [2001:700:0:52E::4] to address [2001:700:0:52e::4] DEBUG: Added 2001:700:0:52E::4 to proxy-itr list DEBUG: converted addr_str [2001:67C:21B4:107::b] to address [2001:67c:21b4:107::b] DEBUG: Added 2001:67C:21B4:107::b to proxy-itr list DEBUG-3: The entry 2610:d0:21a0::1 is not a local EID DEBUG-2: EID prefix 2610:d0:21a0::1/48 inserted in the database DEBUG-2: =>process_netlink_msg: Received new address message DEBUG-2: Finish pocessing netlink message DEBUG-2: lispd_get_iface_address_nl: Couldn't get iface address from afi DEBUG-2: =>process_netlink_msg: Received new address message DEBUG-2: =>process_netlink_msg: Received new address message DEBUG-2: new_device_binded_raw_socket: open socket 6 in interface wlan0 with afi: 10 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG-2: add_interface: Interface wlan0 with interface index 3 added to interfaces lists DEBUG-2: The EID 2610:d0:21a0::1/48 has been assigned to the RLOCs of the interface wlan0 DEBUG-2: The EID 2610:d0:21a0::1/48 has been assigned to the RLOCs of the interface wlan0 DEBUG-3: add_locator_to_mapping: The locator 2001:630:80:7682:8102:2821:a382:d331 has been added to the EID 2610:d0:21a0::1/48. DEBUG: Balancing locator vector for 2610:d0:21a0::1/48: DEBUG: IPv4 locators vector (0 locators): DEBUG: IPv6 locators vector (1 locators): 2001:630:80:7682:8102:2821:a382:d331 DEBUG: IPv4 & IPv6 locators vector (0 locators): DEBUG: Added EID 2610:D0:21A0::1 in the database. DEBUG: converted addr_str [2001:4c08:2016:2064::2] to address [2001:4c08:2016:2064::2] DEBUG: Added 2001:4c08:2016:2064::2 to map-server list DEBUG: Balancing locator vector for 0.0.0.0/0: DEBUG: IPv4 locators vector (0 locators): DEBUG: IPv6 locators vector (1 locators): 2001:4f8:3:d::60 DEBUG: IPv4 & IPv6 locators vector (0 locators): INFO: Log level: High Debug DEBUG: ****** Summary of the configuration ****** DEBUG: ****************** LISP Local Mappings **************** DEBUG: IDENTIFIER (EID): 2610:d0:21a0::1/48 (IID = 0) DEBUG: | Locator (RLOC) | Status | Priority/Weight | DEBUG: | 2001:630:80:7682:8102:2821:a382:d331 | Up | 1/100 | DEBUG: DEBUG: ******************************************************* DEBUG: **************** LISP Mapping Cache ****************** DEBUG: ******************************************************* DEBUG: ******************* Map-Servers list ******************************** DEBUG: | Locator (RLOC) | Key Type | DEBUG: | 2001:4c08:2016:2064::2 | HMAC-SHA-1-96 | DEBUG: ************* Map-Resolvers *************** DEBUG: | Locator (RLOC) | DEBUG: | 2001:4c08:2016:2064::2 | DEBUG: ************************* Proxy ETRs List **************************** DEBUG: | Locator (RLOC) | Status | Priority/Weight | DEBUG: | 2001:4f8:3:d::60 | Up | 1/100 | DEBUG: ************* Proxy-ITRs *************** DEBUG: | Locator (RLOC) | DEBUG: | 2001:67c:21b4:107::b | DEBUG: | 2001:700:0:52e::4 | DEBUG: | 2001:6c8:41:100:0:2:1:c | DEBUG: | 2001:67c:21b4:108::b | DEBUG: | 2001:200:e000:17::17 | DEBUG: | 2001:418:0:1000::613 | DEBUG: | 2001:418:4:1:deaf:bebe:0:10d | DEBUG: | 2001:4f8:3:d::60 | DEBUG: | 2001:590::451f:1f62 | DEBUG: | 202.51.247.10 | DEBUG: | 203.181.249.172 | DEBUG: | 158.38.1.92 | DEBUG: | 193.162.145.46 | DEBUG: | 217.8.98.35 | DEBUG: | 217.8.98.33 | DEBUG: | 129.250.1.63 | DEBUG: | 173.36.193.25 | DEBUG: | 198.6.255.37 | DEBUG: | 149.20.48.60 | DEBUG: | 69.31.31.98 | INFO: **************** DDT: LISP Referral Cache ****************** INFO: IDENTIFIER (EID): 0.0.0.0/0 (IID = 0), TTL: 0 Type: Node Referral INFO: | Locator (RLOC) | Status | Priority/Weight | INFO: | 84.88.16.10 | Up | 10/100 | INFO: | 2001:40b0:1::f0f2 | Up | 10/100 | INFO: INFO: IDENTIFIER (EID): ::/0 (IID = 0), TTL: 0 Type: Node Referral INFO: | Locator (RLOC) | Status | Priority/Weight | INFO: | 84.88.16.10 | Up | 10/100 | INFO: | 2001:40b0:1::f0f2 | Up | 10/100 | INFO: INFO: **************** DDT: LISP MS Referral Cache ****************** INFO: ******************************************************* DEBUG: Balancing locator vector for 0.0.0.0/0: DEBUG: IPv4 locators vector (0 locators): DEBUG: IPv6 locators vector (1 locators): 2001:4f8:3:d::60 DEBUG: IPv4 & IPv6 locators vector (0 locators): DEBUG-2: Default IPv6 iface wlan0 DEBUG-2: Default IPv6 control iface wlan0: 2001:630:80:7682:8102:2821:a382:d331 DEBUG-3: TUN/TAP ifindex is: 10 DEBUG: TUN/TAP mtu set to 1440 DEBUG-2: Tunnel fd at creation is 7 DEBUG: TUN interface UP. DEBUG: added 2610:d0:21a0::1 EID to TUN interface. DEBUG: add_route: added route to the system: src addr: -, dst prefix:::/1, gw: -, table: 254 DEBUG: add_route: added route to the system: src addr: -, dst prefix:8000::/1, gw: -, table: 254 DEBUG-3: new_udp_socket: socket at creation: 8 DEBUG-3: new_raw_input_socket: socket at creation: 9 DEBUG-3: new_udp_socket: socket at creation: 10 DEBUG-3: new_udp_socket: socket at creation: 11 DEBUG-3: new_raw_input_socket: socket at creation: 12 DEBUG-3: new_udp_socket: socket at creation: 13 DEBUG-2: =>process_netlink_msg: Received link message DEBUG-2: process_nl_new_link: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received link message DEBUG-2: process_nl_new_link: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received link message DEBUG-2: process_nl_new_link: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new address message DEBUG-2: process_nl_add_address: the netlink message is not for any interface associated with RLOCs (lispTun0 / 10) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: Finish pocessing netlink message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the netlink message is not for any interface associated with RLOCs (lispTun0) DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the extractet address from the netlink messages is a local link address: fe80::fa1a:67ff:fe5b:a14b discarded DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: process_nl_new_route: the extractet address from the netlink messages is a local link address: fe80::fa1a:67ff:fe5b:a14b discarded DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: Finish pocessing netlink message INFO: LISPmob v0.4.1 compiled for Linux INFO: LISPmob (v0.4.1): 'lispd' started... INFO: Running as a LISP mobile node DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Register message for 2610:d0:21a0::1/48 to Map Server at 2001:4c08:2016:2064::2 DEBUG: Reprogrammed map register for 2610:d0:21a0::1/48 in 3 seconds DEBUG-2: **** Init SMR notification **** DEBUG: No Map Notify received. Retransmitting map register. DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Register message for 2610:d0:21a0::1/48 to Map Server at 2001:4c08:2016:2064::2 DEBUG: Reprogrammed map register for 2610:d0:21a0::1/48 in 3 seconds DEBUG-2: *** Finish SMR notification *** DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 2610:d0:21a0::1 56383 | Orig dst: 2001:4860:4860::8888 53 DEBUG-3: lookup_map_cache_node: The entry 2001:4860:4860::8888 is not found in the map cache DEBUG: No map cache retrieved for eid 2001:4860:4860::8888 DEBUG-2: Added map cache entry for EID: 2001:4860:4860::8888/128 DEBUG: handle_map_cache_miss_with_ddt: Start DDT process to resolve 2001:4860:4860::8888. Process started from prefix ::/0 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2001:4860:4860::8888/128 to 2001:40b0:1::f0f2: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0x31ec31ac-0xac7c9d74 DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID: 2610:d0:21a0::1, rmt EID: 0.0.0.0, protocol: 17, src port: 56383 , dst port: 53 --> src RLOC: 2001:630:80:7682:8102:2821:a382:d331, dst RLOC: 2001:4f8:3:d::60 DEBUG-3: OUTPUT: Encap src: 2001:630:80:7682:8102:2821:a382:d331 | Encap dst: 2001:4f8:3:d::60 DEBUG-3: Fordwarded packet to petr: 2001:4f8:3:d::60 DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: Finish pocessing netlink message DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: :: 0 | Orig dst: ff02::16 0 DEBUG-3: The entry :: is not a local EID DEBUG-3: Fordwarding native for destination ff02::16 DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: Finish pocessing netlink message DEBUG-3: INPUT (No LISP data): UDP dest: 28087 DEBUG-3: Received IPv6 packet in the control input buffer (4342) DEBUG-2: Received a LISP control message at 2001:630:80:7682:8102:2821:a382:d331 DEBUG: Received a LISP Map-Notify message DEBUG-2: Map Notify confirms correct registration of the prefix 2610:d0:21a0::1/48 DEBUG: Reprogrammed map register for 2610:d0:21a0::1/48 in 60 seconds DEBUG: Start SMR for local EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:67c:21b4:107::b: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c18931-0xb1fcb475 DEBUG: SMR'ing Proxy ITR 2001:67c:21b4:107::b for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:700:0:52e::4: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c05564-0xe47cb575 DEBUG: SMR'ing Proxy ITR 2001:700:0:52e::4 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:6c8:41:100:0:2:1:c: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c09bbd-0xbdfeb575 DEBUG: SMR'ing Proxy ITR 2001:6c8:41:100:0:2:1:c for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:67c:21b4:108::b: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c0e270-0xf0ffb575 DEBUG: SMR'ing Proxy ITR 2001:67c:21b4:108::b for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:200:e000:17::17: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c32d87-0xa77cb675 DEBUG: SMR'ing Proxy ITR 2001:200:e000:17::17 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:418:0:1000::613: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c36c88-0xa87db675 DEBUG: SMR'ing Proxy ITR 2001:418:0:1000::613 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:418:4:1:deaf:bebe:0:10d: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c3a9b6-0xb6fcb675 DEBUG: SMR'ing Proxy ITR 2001:418:4:1:deaf:bebe:0:10d for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:4f8:3:d::60: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c3f5b7-0xb7fcb675 DEBUG: SMR'ing Proxy ITR 2001:4f8:3:d::60 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG: Sent Map-Request packet for 2610:d0:21a0::1/48 to 2001:590::451f:1f62: Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x30c2706b-0xeb7db775 DEBUG: SMR'ing Proxy ITR 2001:590::451f:1f62 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 202.51.247.10 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 203.181.249.172 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 158.38.1.92 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 193.162.145.46 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 217.8.98.35 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 217.8.98.33 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 129.250.1.63 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 173.36.193.25 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 198.6.255.37 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 149.20.48.60 for EID 2610:d0:21a0::1/48 DEBUG-2: Record information EID: 2610:d0:21a0::1/48 DEBUG-2: Record information Locator: 2001:630:80:7682:8102:2821:a382:d331 P:1-W:100-MP:255-MW:0 Reachable: 1 Probed: 0 DEBUG-2: send_control_msg: Couldn't send control message. No output interface with afi 2. DEBUG: Couldn't sent Map-Request packet for 2610:d0:21a0::1/48: Encap: N, Probe: N, SMR: Y, SMR-inv: N DEBUG: Coudn't SMR Proxy ITR 69.31.31.98 for EID 2610:d0:21a0::1/48 DEBUG-2: Completed processing of LISP control message DEBUG-3: INPUT (No LISP data): UDP dest: 28087 DEBUG-3: Received IPv6 packet in the control input buffer (4342) DEBUG-2: Received a LISP control message at 2001:630:80:7682:8102:2821:a382:d331 DEBUG: Received a LISP Map-Notify message DEBUG-2: Map Notify confirms correct registration of the prefix 2610:d0:21a0::1/48 DEBUG: Reprogrammed map register for 2610:d0:21a0::1/48 in 60 seconds DEBUG-2: Completed processing of LISP control message DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: Finish pocessing netlink message DEBUG-3: INPUT (No LISP data): UDP dest: 28087 DEBUG-3: Received IPv6 packet in the control input buffer (4342) DEBUG-2: Received a LISP control message at 2001:630:80:7682:8102:2821:a382:d331 DEBUG: Received a LISP Map-Referral message DEBUG-2: process_map_referral: Nonce of the Map Referral is: 0x31ec31ac-0xac7c9d74 DEBUG-2: process_map_referral_record:Answer from 2001:40b0:1::f0f2 : Authoritative: 1 , Incomplete: 0 DEBUG-2: IDENTIFIER (EID): 2001:4800::/21 (IID = 0), TTL: 15 Type: Delegation hole DEBUG-3: lookup_referral_cache_exact_node: The entry 2001:4800::/21 is not found in the referral cache DEBUG-2: Added referral cache entry for EID: 2001:4800::/21 DEBUG-2: Added map cache entry for EID: 2001:4800::/21 DEBUG-2: EID prefix of the map cache entry 2001:4860:4860::8888/128 changed to 2001:4800::/21. DEBUG: Activated negative map cache with prefix 2001:4800::/21. The entry will expire in 15 minutes. DEBUG-2: Completed processing of LISP control message DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: :: 0 | Orig dst: ff02::16 0 DEBUG-3: The entry :: is not a local EID DEBUG-3: Fordwarding native for destination ff02::16 DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new route message DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:fa1a:67ff:feaf:f14e DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:8102:2821:a382:d331 DEBUG-2: Finish pocessing netlink message DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 2610:d0:21a0::1 37008 | Orig dst: 2001:4860:4860::8888 53 DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID: 2610:d0:21a0::1, rmt EID: 0.0.0.0, protocol: 17, src port: 37008 , dst port: 53 --> src RLOC: 2001:630:80:7682:8102:2821:a382:d331, dst RLOC: 2001:4f8:3:d::60 DEBUG-3: OUTPUT: Encap src: 2001:630:80:7682:8102:2821:a382:d331 | Encap dst: 2001:4f8:3:d::60 DEBUG-3: Fordwarded packet to petr: 2001:4f8:3:d::60 DEBUG-3: INPUT (No LISP data): UDP dest: 53 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 2610:d0:21a0::1 54212 | Orig dst: 2001:4860:4860::8888 53 DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID: 2610:d0:21a0::1, rmt EID: 0.0.0.0, protocol: 17, src port: 54212 , dst port: 53 --> src RLOC: 2001:630:80:7682:8102:2821:a382:d331, dst RLOC: 2001:4f8:3:d::60 DEBUG-3: OUTPUT: Encap src: 2001:630:80:7682:8102:2821:a382:d331 | Encap dst: 2001:4f8:3:d::60 DEBUG-3: Fordwarded packet to petr: 2001:4f8:3:d::60 DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:fa1a:67ff:feaf:f14e DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:8102:2821:a382:d331 DEBUG-2: Finish pocessing netlink message DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 2610:d0:21a0::1 49790 | Orig dst: 2001:4860:4860::8888 53 DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID: 2610:d0:21a0::1, rmt EID: 0.0.0.0, protocol: 17, src port: 49790 , dst port: 53 --> src RLOC: 2001:630:80:7682:8102:2821:a382:d331, dst RLOC: 2001:4f8:3:d::60 DEBUG-3: OUTPUT: Encap src: 2001:630:80:7682:8102:2821:a382:d331 | Encap dst: 2001:4f8:3:d::60 DEBUG-3: Fordwarded packet to petr: 2001:4f8:3:d::60 DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:fa1a:67ff:feaf:f14e DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:8102:2821:a382:d331 DEBUG-2: Finish pocessing netlink message DEBUG-3: INPUT (No LISP data): UDP dest: 53 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 2610:d0:21a0::1 45750 | Orig dst: 2001:4860:4860::8888 53 DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID: 2610:d0:21a0::1, rmt EID: 0.0.0.0, protocol: 17, src port: 45750 , dst port: 53 --> src RLOC: 2001:630:80:7682:8102:2821:a382:d331, dst RLOC: 2001:4f8:3:d::60 DEBUG-3: OUTPUT: Encap src: 2001:630:80:7682:8102:2821:a382:d331 | Encap dst: 2001:4f8:3:d::60 DEBUG-3: Fordwarded packet to petr: 2001:4f8:3:d::60 DEBUG-3: Received notification from net link DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:fa1a:67ff:feaf:f14e DEBUG-2: =>process_netlink_msg: Received new address message DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:fa1a:67ff:feaf:f14e/128 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG: precess_address_change: New address detected for interface wlan0 -> 2001:630:80:7682:8102:2821:a382:d331 DEBUG-2: Finish pocessing netlink message ^CDEBUG: Terminal interrupt. Cleaning up... DEBUG: del_rule: Removed rule in ip rule table for source routing of src prefix: 2001:630:80:7682:8102:2821:a382:d331/128 DEBUG-2: remove_locator_from_mapping: The locator (null) has not been found in the mapping with EID prefix 2610:d0:21a0::1/48. DEBUG-2: remove_locator_from_list: The locator 2001:630:80:7682:8102:2821:a382:d331 has not been found. DEBUG-2: remove_locator_from_mapping: The locator 2001:630:80:7682:8102:2821:a382:d331 has not been found in the mapping with EID prefix 2610:d0:21a0::1/48. DEBUG-3: free_map_cache_db: Releasing memory of map cache DEBUG-3: free_local_db: Releasing memory of local mappings DEBUG-2: Droping referral cache... root@lispmn:/etc#
