# General configuration
#       debug: Debug levels [0..3]
#       map-request-retries: Additional Map-Requests to send per map cache
miss

debug                  = 2
map-request-retries    = 2

# RLOC Probing configuration
#   rloc-probe-interval: interval at which periodic RLOC probes are sent
#     (seconds). A value of 0 disables RLOC Probing
#   rloc-probe-retries: RLOC Probe retries before setting the locator with
#     status down. [0..5]
#   rloc-probe-retries-interval: interval at which RLOC probes retries are
#     sent (seconds) [1..#rloc-probe-interval]

rloc-probing {
    rloc-probe-interval             = 30
    rloc-probe-retries              = 2
    rloc-probe-retries-interval     = 5
}

# NAT Traversal configuration.
#   nat_aware: check if the node is behind NAT
#   site_ID: 64 bits to identify the site which the node is connected to. In
#     hexadecimal
#   xTR_ID: 128 bits to identify the xTR inside the site. In hexadecimal
# Limitation of version 0.3.3 when nat_aware is enabled:
#   - Only one interface is supported.
#   - Only one Map Server and one Map Resolver

nat-traversal {
    nat_aware   = off
    site_ID     = 0000000000000001                  #In doubt, keep the
default value
    xTR_ID      = 00000000000000000000000000000001  #In doubt, keep the
default value
}

# Encapsulated Map-Requests are sent to this map-resolver
# You can define several map-resolvers. Encapsulated Map-Request messages
will
# be sent to only one.
#   address: IPv4 or IPv6 address of the map resolver
map-resolver        = {
        2001:4f8:3:d::61
}

# Map-Registers are sent to this map-server
# You can define several map-servers. Map-Register messages will be sent to
all
# of them.
#   address: IPv4 or IPv6 address of the map-server
#   key-type: Only 1 supported (HMAC-SHA-1-96)
#   key: password to authenticate with the map-server
#   proxy-reply [on/off]: Configure map-server to Map-Reply on behalf of
the xTR

map-server {
        address     = 2001:4f8:3:d::61
        key-type    = 1
        key         = Esbobav9
        proxy-reply = on
}

# Packets addressed to non-LISP sites will be encapsulated to this Proxy-ETR
# You can define several Proxy-ETR. Traffic will be balanced according to
# priority and weight.
#   address: IPv4 or IPv6 address of the Proxy-ETR
#   priority [0-255]: Proxy-ETR with lower values are more preferable.
#   weight [0-255]: When priorities are the same for multiple Proxy-ETRs,
#     the Weight indicates how to balance unicast traffic between them.

proxy-etr {
        address         = 2001:4f8:3:d::60              # isc-pxtr
        priority    = 1
        weight      = 100
}

# IPv4 / IPv6 EID of the node.
# One database-mapping structure is defined for each interface with RLOCs
# associated to this EID
#   eid-prefix: EID prefix (IPvX/mask) of the mapping
#   interface: interface containing the RLOCs associated to this mapping
#   priority_vX [0-255]: Priority for the IPvX RLOC of the interface.
Locators
#     with lower values are more preferable. This is used for both incoming
#     policy announcements and outcoming traffic policy management. (A value
#     of -1  means that IPvX address of that interface is not used)
#   weight [0-255]: When priorities are the same for multiple RLOCs, the
Weight
#     indicates how to balance unicast traffic between them.

database-mapping {
         eid-prefix     = 153.16.31.32/28
         interface      = he-ipv6
         priority_v4    = 1                                     # Priority
of IPv4 locator of the interface eth0 for this EID
         weight_v4      = 100                           # Weight of IPv4
locator of the interface eth0 for this EID
}

database-mapping {
         eid-prefix     = 2610:D0:113F::/48
         interface      = he-ipv6
         priority_v6    = 1                                     # Priority
of IPv6 locator of the interface eth0 for this EID
         weight_v6      = 100                           # Weight of IPv6
locator of the interface eth0 for this EID
}

#proxy-itrs = {
#       173.36.193.25
#}

# Current LISP beta-network (lisp4.net/lisp6.net) PITR addresses
# Uncomment the IPv4 or IPv6 list based on your current locators and
# comment the previous 'proxy-itrs' section

# LISP beta-network IPv4 PITRs
#proxy-itrs = {
#       69.31.31.98,            # eqx-ash-pxtr
#       149.20.48.60            # isc-pxtr
#       198.6.255.37,           # asp-pxtr
#       173.36.193.25,          # sjc-pxtr
#       129.250.1.63,           # ntt-amer-pxtr
#       217.8.98.33,            # intouch-pxtr-1
#       217.8.98.35,            # intouch-pxtr-2
#       193.162.145.46,         # tdc-pxtr
#       158.38.1.92,            # uninett-pxtr
#       203.181.249.172,        # apan-pxtr
#       202.51.247.10           # sg-nus-pxtr
#}

# LISP beta-network IPv6 PITRs

proxy-itrs = {
#       2001:590::451f:1f62,            # eqx-ash-pxtr
        2001:4f8:3:d::60                # isc-pxtr
#       2001:418:4:1:deaf:bebe::10d,    # asp-pxtr
#       2001:418:0:1000::613,           # ntt-amer-pxtr
#       2001:200:e000:17::17,           # intouch-pxtr-1
#       2001:67C:21B4:108::b,           # intouch-pxtr-2
#       2001:6c8:41:100:0:2:1:c,        # tdc-pxtr
#       2001:700:0:52E::4,              # uninett-pxtr
#       2001:67C:21B4:107::b            # apan-pxtr
}


$ cat lispd.log
INFO: LISPmob compiled for linux xTR

DEBUG: RLOC Probing Interval: 30
DEBUG: Added 2001:4f8:3:d::61 to map-resolver list
DEBUG-2: 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: Added 2001:4f8:3:d::60 to proxy-itr list
DEBUG-2: EID prefix 153.16.31.32/28 inserted in the database
DEBUG-2: lispd_get_iface_address: interface address from he-ipv6 discarded
(fe80::21a:4dff:fe43:d460)
DEBUG-2: lispd_get_iface_address: interface address from he-ipv6 discarded
(fe80::20e:cff:fec2:ffc8)
DEBUG-2: lispd_get_iface_address: interface address from he-ipv6 discarded
(fe80::20e:cff:fec2:ffc9)
DEBUG-2: lispd_get_iface_address: IPv6 RLOC from interface (he-ipv6):
2001:470:1f0e:10d0::2

DEBUG-2: open_device_binded_raw_socket: open socket 5 in interface he-ipv6
with afi: 10
DEBUG: add_rule: Add rule for source routing of src addr:
2001:470:1f0e:10d0::2
DEBUG-2: add_interface: Interface he-ipv6 with interface index 48 added to
interfaces lists
DEBUG-2: The EID 153.16.31.32/28 has been assigned to the RLOCs of the
interface he-ipv6
DEBUG-2: The EID 153.16.31.32/28 has been assigned to the RLOCs of the
interface he-ipv6
DEBUG-2: add_locator_to_mapping: The locator 2001:470:1f0e:10d0::2 has been
added to the EID 153.16.31.32/28.
DEBUG: Balancing locator vector for 153.16.31.32/28:
DEBUG:   IPv4 locators vector (0 locators):
DEBUG:   IPv6 locators vector (1 locators):   2001:470:1f0e:10d0::2
DEBUG:   IPv4 & IPv6 locators vector (0 locators):
DEBUG: Added EID 153.16.31.32 in the database.
DEBUG-2: EID prefix 2610:d0:113f::/48 inserted in the database
DEBUG-2: The EID 2610:d0:113f::/48 has been assigned to the RLOCs of the
interface he-ipv6
DEBUG-2: The EID 2610:d0:113f::/48 has been assigned to the RLOCs of the
interface he-ipv6
DEBUG-2: add_locator_to_mapping: The locator 2001:470:1f0e:10d0::2 has been
added to the EID 2610:d0:113f::/48.
DEBUG: Balancing locator vector for 2610:d0:113f::/48:
DEBUG:   IPv4 locators vector (0 locators):
DEBUG:   IPv6 locators vector (1 locators):   2001:470:1f0e:10d0::2
DEBUG:   IPv4 & IPv6 locators vector (0 locators):
DEBUG: Added EID 2610:D0:113F:: in the database.
DEBUG: Added 2001:4f8:3:d::61 to map-server list
INFO: Log level: Medium debug
DEBUG: ****** Summary of the configuration ******
DEBUG: ****************** LISP Local Mappings ****************

DEBUG: IDENTIFIER (EID): 153.16.31.32/28 (IID = -1)

DEBUG: |               Locator (RLOC)            | Status | Priority/Weight
|
DEBUG: |                   2001:470:1f0e:10d0::2 |     Up |       0/0
|
DEBUG:

DEBUG: IDENTIFIER (EID): 2610:d0:113f::/48 (IID = -1)

DEBUG: |               Locator (RLOC)            | Status | Priority/Weight
|
DEBUG: |                   2001:470:1f0e:10d0::2 |     Up |       1/100
|
DEBUG:

DEBUG: *******************************************************

DEBUG: **************** LISP Mapping Cache ******************

DEBUG: *******************************************************

DEBUG: ******************* Map-Servers list ********************************
DEBUG: |               Locator (RLOC)            |       Key Type          |
DEBUG: |                        2001:4f8:3:d::61 |     HMAC-SHA-1-96       |
DEBUG: ************* Map-Resolvers ***************
DEBUG: |               Locator (RLOC)            |
DEBUG: |                        2001:4f8:3:d::61 |
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:4f8:3:d::60 |
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 he-ipv6

DEBUG: del_route: deleted route  from the system
DEBUG: del_route: deleted route  from the system
DEBUG: add_route: added route to the system: src addr:
2001:470:1f0e:10d0::2, dst prefix:::/1, gw: -, table: 254
DEBUG: add_route: added route to the system: src addr:
2001:470:1f0e:10d0::2, dst prefix:8000::/1, gw: -, table: 254
DEBUG-2: Default IPv6 control iface he-ipv6: 2001:470:1f0e:10d0::2

DEBUG: TUN/TAP mtu set to 1440
DEBUG-2: Tunnel fd at creation is 6
DEBUG: TUN interface UP.
DEBUG: added 127.0.0.127 EID to TUN interface.
DEBUG: add_route: added route to the system: src addr: -, dst prefix:
0.0.0.0/1, gw: -, table: 254
DEBUG: add_route: added route to the system: src addr: -, dst prefix:
128.0.0.0/1, gw: -, table: 254
DEBUG: added ::127 EID to TUN interface.
DEBUG: add_route: added route to the system: src addr:
2001:470:1f0e:10d0::2, dst prefix:::/1, gw: -, table: 254
DEBUG: add_route: added route to the system: src addr:
2001:470:1f0e:10d0::2, dst prefix:8000::/1, gw: -, table: 254
INFO: LISPmob (0.3.3): 'lispd' started...
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 (eth0)
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 (eth0)
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 (eth2)
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 (eth1)
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: =>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: =>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_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_nl_new_route: the netlink message is not for any interface
associated with RLOCs (eth1)
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 (eth2)
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 (eth0)
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 (eth1)
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 (eth2)
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: process_nl_new_route: Process new gateway associated to the
interface he-ipv6:  2001:470:1f0e:10d0::1
DEBUG: add_route: added route to the system: src addr: -, dst prefix:-/0,
gw: 2001:470:1f0e:10d0::1, table: 48
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: =>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: =>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: Sent Map-Register message for 153.16.31.32/28 to Map Server at
2001:4f8:3:d::61
DEBUG: Sent Map-Register message for 2610:d0:113f::/48 to Map Server at
2001:4f8:3:d::61
DEBUG: Reprogrammed map register in 60 seconds
DEBUG-2: *** Init SMR notification ***
DEBUG: Sent Map-Register message for 153.16.31.32/28 to Map Server at
2001:4f8:3:d::61
DEBUG: Start SMR for local EID 153.16.31.32/28
DEBUG: Sent Map-Request packet for 153.16.31.32/28 to 2001:4f8:3:d::60:
Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x8de60814-0xb44e6f5a
DEBUG:   SMR'ing Proxy ITR 2001:4f8:3:d::60 for EID 153.16.31.32/28
DEBUG: Sent Map-Register message for 2610:d0:113f::/48 to Map Server at
2001:4f8:3:d::61
DEBUG: Start SMR for local EID 2610:d0:113f::/48
DEBUG: Sent Map-Request packet for 2610:d0:113f::/48 to 2001:4f8:3:d::60:
Encap: N, Probe: N, SMR: Y, SMR-inv: N . Nonce: 0x8de74737-0xb74b6f5a
DEBUG:   SMR'ing Proxy ITR 2001:4f8:3:d::60 for EID 2610:d0:113f::/48
DEBUG-2: *** Finish SMR notification ***
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_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: No map cache retrieved for eid 8.8.4.4
DEBUG-2: Added map cache entry for EID: 8.8.4.4/32
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xa243e82d-0xbdeeeb5e
DEBUG-2: =>process_netlink_msg: Received  new route message
DEBUG-2: =>process_netlink_msg: Received  new route message
DEBUG: Retransmiting Map Request for EID: 8.8.4.4 (1 retries)
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xb7aef3ee-0xfeff6f5a
DEBUG: Retransmiting Map Request for EID: 8.8.4.4 (2 retries)
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xb5af64ad-0xbd6a6f5a
DEBUG: No Map Reply fot EID 8.8.4.4/32 after 2 retries. Removing map cache
entry ...
DEBUG-2: Deleting map cache entry: 8.8.4.4/32
DEBUG: No map cache retrieved for eid 8.8.8.8
DEBUG-2: Added map cache entry for EID: 8.8.8.8/32
DEBUG: Sent Map-Request packet for 8.8.8.8/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0x97696b8b-0xbf6fe976
DEBUG: Retransmiting Map Request for EID: 8.8.8.8 (1 retries)
DEBUG: Sent Map-Request packet for 8.8.8.8/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xa9af08c7-0xc74e6f5a
DEBUG: Sent Map-Request packet for 0.0.0.0/0 to 2001:4f8:3:d::60: Encap: N,
Probe: Y, SMR: N, SMR-inv: N . Nonce: 0xafaefc08-0xcafa6f5a
DEBUG: Retransmiting Map Request for EID: 8.8.8.8 (2 retries)
DEBUG: Sent Map-Request packet for 8.8.8.8/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xafa00c59-0xdb4a695a
DEBUG: No map cache retrieved for eid 8.8.4.4
DEBUG-2: Added map cache entry for EID: 8.8.4.4/32
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0x84034824-0xe44eeb72
DEBUG: No Map Reply fot EID 8.8.8.8/32 after 2 retries. Removing map cache
entry ...
DEBUG-2: Deleting map cache entry: 8.8.8.8/32
DEBUG: Retransmiting Map Request for EID: 8.8.4.4 (1 retries)
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xa2af6d2f-0xef6b6f5a
DEBUG: Retransmiting Map-Request Probe for locator 2001:4f8:3:d::60 and
EID: 0.0.0.0/0 (1 retries)
DEBUG: Sent Map-Request packet for 0.0.0.0/0 to 2001:4f8:3:d::60: Encap: N,
Probe: Y, SMR: N, SMR-inv: N . Nonce: 0xa0af772a-0xef7b6f5a
DEBUG: Retransmiting Map Request for EID: 8.8.4.4 (2 retries)
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xa0a077cb-0xcf7b695a
DEBUG: No map cache retrieved for eid 8.8.8.8
DEBUG-2: Added map cache entry for EID: 8.8.8.8/32
DEBUG: Sent Map-Request packet for 8.8.8.8/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xb24e3d7e-0xff7bef5e
DEBUG: No Map Reply fot EID 8.8.4.4/32 after 2 retries. Removing map cache
entry ...
DEBUG-2: Deleting map cache entry: 8.8.4.4/32
DEBUG: Retransmiting Map Request for EID: 8.8.8.8 (1 retries)
DEBUG: Sent Map-Request packet for 8.8.8.8/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xa7af5dc0-0xca5b6f5a
DEBUG: Retransmiting Map-Request Probe for locator 2001:4f8:3:d::60 and
EID: 0.0.0.0/0 (2 retries)
DEBUG: Sent Map-Request packet for 0.0.0.0/0 to 2001:4f8:3:d::60: Encap: N,
Probe: Y, SMR: N, SMR-inv: N . Nonce: 0xa5af130d-0xcd5f6f5a
DEBUG: Retransmiting Map Request for EID: 8.8.8.8 (2 retries)
DEBUG: Sent Map-Request packet for 8.8.8.8/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xa5aff43a-0xfefa6f5a
DEBUG: No Map Reply fot EID 8.8.8.8/32 after 2 retries. Removing map cache
entry ...
DEBUG-2: Deleting map cache entry: 8.8.8.8/32
DEBUG: No map cache retrieved for eid 8.8.4.4
DEBUG-2: Added map cache entry for EID: 8.8.4.4/32
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xdb7b4317-0xdf4ffb5a
DEBUG-2: =>process_netlink_msg: Received  new route message
DEBUG-2: =>process_netlink_msg: Received  new route message
DEBUG: Retransmiting Map Request for EID: 8.8.4.4 (1 retries)
DEBUG: Sent Map-Request packet for 8.8.4.4/32 to 2001:4f8:3:d::61: Encap:
Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd9af1f3f-0xff5b6f5a
DEBUG: Terminal interrupt. Cleaning up...
DEBUG: del_route: deleted route  from the system
DEBUG: del_rule: Removed rule for source routing of src addr:
2001:470:1f0e:10d0::2
INFO: Exiting ...


On Thursday, October 24, 2013, Albert López wrote:

>  Hi Daniel,
>
> Could you provide us the logs at level 2 please?
>
> Thanks
>
> Albert
>
> On 10/24/2013 03:24 PM, Daniel Justice wrote:
>
> Yes, that works.  However, I'm not getting map-responses to my
> map-requests like what happened when I first tried with v4.  Can someone
> check my information?
>
> On Tuesday, October 22, 2013, Lori Jakab wrote:
>
>> On Oct 22, 2013, at 6:42 PM, Daniel Justice wrote:
>>
>> > Are there any public v6 ms/mr's out there?  I went tried to resolve the
>> cisco and isc servers to v6 addresses, but didn't have any luck.  I'm
>> wanting to try multi-homed v6, but I don't want to go dual-stack due to the
>> configuration of my lab (lots of v6 space, one v4 address).  Thanks,
>>
>>
>> I assume you tried resolving isc-mr-ms.rloc.lisp4.net to IPv6 addresses.
>>  There is a separate DNS name space for IPv6, ending in lisp6.net.  So
>>
>> $ host isc-mr-ms.rloc.lisp6.net
>> isc-mr-ms.rloc.lisp6.net has IPv6 address 2001:4f8:3:d::61
>>
>> $ host asp-mr-ms.rloc.lisp6.net
>> asp-mr-ms.rloc.lisp6.net has IPv6 address 2001:418:4:1:deaf:bebe::10d
>>
>> HTH,
>> -Lori
>
>
>
>

Reply via email to