Hello Lori and LISPMob Team:
The LISP MN host RLOC 128.107.130.179 using right now is a Cisco IP.
-If possible to avoid the NAT and Firewall issue through the RTR when try to
join the lisp beta network?
-How to specify the RTR in lispd.conf?
// See the log
Please let me know.
Thanks
-----Original Message-----
From: Lori Jakab [mailto:[email protected]]
Sent: Tuesday, September 03, 2013 2:09 AM
To: Lin Feng (linfeng)
Cc: [email protected]
Subject: Re: [Contactus-linux] [Linux] : Can not ping MS/MR after joining LISP
beta network
Hi Lin,
You should post these kind of support questions on the LISPmob-users mailing
list, where the responses are archived and indexed by search engines to the
benefit of the larger LISPmob community.
On Sep 3, 2013, at 9:46 AM, Lin Feng (linfeng) wrote:
> Thank you Lori. Got some issues after joining LISP beta network with the
> information provided.
>
> 1] I tried to provision my LISPMob MN (Ubuntu 12.04 host) with
> IPV4 EID 153.16.22.147/32 as you provided and start the LISP MN
> according to http://lispmob.org/documentation->Running LISPmob with
> command like sudo lispd -f /etc/lispd.conf after adding the IPv4
> EID/MS/MR/PXTR information you provided into lispd.conf and change
> /etc/sysctl.conf
>
> 2] However once this LISP MN join the LISP beta network,...
> I can not ping MS/MR 149.20.48.77 and SJC-PXTR 173.36.193.25 and more.
> There is no issue to ping MS/MR/SJC-PXTR before starting lispd and join the
> beta network.
>
> Both 'ip addr' and 'ip route' output looks fine even after joining beta n/w.
>
> You can find the detailed log before and after running lispd on Ubuntu 12.04
> LISP host.
> The LISPMob host RLOC is 128.107.130.179
This looks like a Cisco IP address, and it is most likely behind a restrictive
firewall. I cannot ping it from a non-Cisco network (but can from a Cisco
laptop). The Map-Server shows your EID as never registered, so probably the
Map-Register packets never reached the server. We had some partial success
using LISPmob from the Guest wireless network, which was outside the firewall,
and from lab servers that are in the DMZ. I recommend you use a VM in a
non-Cisco network for LISPmob.
-Lori
>
> 3] Could you please have a look on the log and see if there is any issue for
> LISP MN to join the beta n/w?
>
>
> Thanks
>
> Lin
>
>
>
> -----Original Message-----
> From: Lori Jakab [mailto:[email protected]]
> Sent: Monday, September 02, 2013 2:01 AM
> To: Lin Feng (linfeng)
> Cc: [email protected]
> Subject: Re: [Contactus-linux] [Linux] : Need to join LISP beta
> network
>
> Hi Lin,
>
> I just provisioned v4 and v6 EIDs for you, here are your connection details:
>
> IPv4 EID: 153.16.22.147/32
> IPv6 EID: 2610:d0:1219:128::13/128
> Map Server: 149.20.48.77
> Map Server password: Mos7Knik
> Map Resolver: 149.20.48.77
>
> You can find more information about the Beta network (like potential
> Proxy-ETR if you need one) here:
> http://www.lisp4.net/images/lisp-ddt.pdf
>
> Should you have any issues or questions, please post to the LISPmob-users
> mailing list for support.
>
> Best regards,
> -Lori
>
> On Aug 30, 2013, at 1:28 AM, Lin Feng (linfeng) wrote:
>
>> Thank you, Alberto. Please keep us posted..
>>
>> -----Original Message-----
>> From: Alberto Rodriguez-Natal [mailto:[email protected]]
>> Sent: Thursday, August 29, 2013 11:46 AM
>> To: Lin Feng (linfeng)
>> Cc: [email protected]
>> Subject: Re: [Contactus-linux] [Linux] : Need to join LISP beta
>> network
>>
>> Hi Lin,
>>
>> Thank you for the details. We have all the information we need. There is no
>> problem in provision you both IPv4 and IPv6 EIDs ;). Usually, the provision
>> is a matter of just a few days, but right now part of the team is on
>> vacation and some delay is expected. We'll get back to you with the
>> connectivity details ASAP.
>>
>> Thanks!
>> Alberto
>>
>> On 29 August 2013 01:29, Lin Feng (linfeng) <[email protected]> wrote:
>>> Thank you Alberto. Please see reply and let me know the detail asap.
>>>
>>> * geographical location of the intended deployment (we need to
>>> provision mapping service on Map-Servers topologically close to
>>> you);
>>>
>>> ++++[Lin] I am in San Jose, California, USA.
>>>
>>> * Linux distribution you will use;
>>>
>>> ++++[Lin] I am using Ubuntu 12.04 , kernel 3.0.35
>>>
>>> * the scenarios and use cases you are most interested in (e.g.,
>>> multihoming, IPv6 transition, ingress traffic engineering, just
>>> learning a new tech, etc.);
>>> * how did you learn about LISP beta-network and the LISPmob project.
>>>
>>> ++++[Lin] We are evaluating the LISP technology for the purpose of
>>> ++++IP mobility. In the areas
>>>
>>>
>>> - To keep LISP MN IP address or session persistence even when the
>>> user LISP-MN roaming into different service provider, access n/w
>>> 3G/Wif or even different country
>>> - Proper Authentication of LISP MN
>>> -IPv6 Transition
>>> - MultiHoming,
>>> -Ingress Traffic Engineering,
>>>
>>> If possible, please assign both IPv6 and IPv4 EID for my linux host :-).
>>>
>>>
>>>
>>> Thanks
>>>
>>> lin
>>> -----Original Message-----
>>> From: Alberto Rodriguez-Natal [mailto:[email protected]]
>>> Sent: Wednesday, August 28, 2013 6:30 AM
>>> To: Lin Feng (linfeng)
>>> Cc: [email protected]
>>> Subject: Re: [Contactus-linux] [Linux] : Need to join LISP beta
>>> network
>>>
>>> Hi Lin,
>>>
>>> We will be more than glad to provide you connectivity. Keep in mind that
>>> you will need a public IP address to use as RLOC since the beta-network
>>> doesn't support NAT traversal (yet).
>>>
>>> We will need a few pieces of information before we can provision
>>> your EID
>>> space:
>>>
>>> * geographical location of the intended deployment (we need to
>>> provision mapping service on Map-Servers topologically close to
>>> you);
>>> * Linux distribution you will use;
>>> * the scenarios and use cases you are most interested in (e.g.,
>>> multihoming, IPv6 transition, ingress traffic engineering, just
>>> learning a new tech, etc.);
>>> * how did you learn about LISP beta-network and the LISPmob project.
>>>
>>> Once we have the above info, we will provide you with all the information
>>> you need to get you started. We recommend you explore the documentation on
>>> our web site http://lispmob.org/ and subscribe to the LISPmob users mailing
>>> list at https://lispmob.org/mailman/listinfo/users.
>>>
>>> Thank you for your interest in LISPmob!
>>>
>>> Alberto
>>>
>>
>> _______________________________________________
>> Contactus-linux mailing list
>> [email protected]
>> https://lispmob.org/mailman/listinfo/contactus-linux
>
> <before_run_lispd.txt><after_run_lispd.txt>
Script started on Tue Jan 6 23:58:52 1970
root@ccc823:/lispmob/mylog# ifconfig
eth9 Link encap:Ethernet HWaddr 00:04:9f:02:af:77
inet addr:128.107.130.179 Bcast:128.107.131.255 Mask:255.255.254.0
inet6 addr: 2001:420:303:1320:2d7f:931:8463:9d2a/64 Scope:Global
inet6 addr: 2001:420:303:1320:204:9fff:fe02:af77/64 Scope:Global
inet6 addr: fe80::204:9fff:fe02:af77/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39220 errors:0 dropped:2 overruns:0 frame:0
TX packets:15300 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5465113 (5.4 MB) TX bytes:4537984 (4.5 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:23 errors:0 dropped:0 overruns:0 frame:0
TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2116 (2.1 KB) TX bytes:2116 (2.1 KB)
root@ccc823:/lispmob/mylog# ip route
default via 128.107.130.1 dev eth9 proto static
128.107.130.0/23 dev eth9 proto kernel scope link src 128.107.130.179
metric 1
169.254.0.0/16 dev eth9 scope link metric 1000
root@ccc823:/lispmob/mylog# ping 128.107.130.1
PING 128.107.130.1 (128.107.130.1) 56(84) bytes of data.
64 bytes from 128.107.130.1: icmp_req=1 ttl=255 time=2.80 ms
64 bytes from 128.107.130.1: icmp_req=2 ttl=255 time=43.5 ms
^C
--- 128.107.130.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.803/23.164/43.525/20.361 ms
root@ccc823:/lispmob/mylog# ping 128.107.130.1
PING 128.107.130.1 (128.107.130.1) 56(84) bytes of data.
64 bytes from 128.107.130.1: icmp_req=1 ttl=255 time=2.78 ms
64 bytes from 128.107.130.1: icmp_req=2 ttl=255 time=20.0 ms
^C
--- 128.107.130.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.786/11.396/20.006/8.610 ms
root@ccc823:/lispmob/mylog# ping 149.20.48..[K77
PING 149.20.48.77 (149.20.48.77) 56(84) bytes of data.
64 bytes from 149.20.48.77: icmp_req=1 ttl=239 time=51.1 ms
64 bytes from 149.20.48.77: icmp_req=2 ttl=239 time=71.6 ms
^C
--- 149.20.48.77 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 51.103/61.372/71.641/10.269 ms
root@ccc823:/lispmob/mylog# ping 173.36.193.25
PING 173.36.193.25 (173.36.193.25) 56(84) bytes of data.
64 bytes from 173.36.193.25: icmp_req=1 ttl=244 time=2.67 ms
64 bytes from 173.36.193.25: icmp_req=2 ttl=244 time=29.9 ms
^C
--- 173.36.193.25 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.671/16.323/29.976/13.653 ms
root@ccc823:/lispmob/mylog# cat /etc/lispd.config[K[K
#
#
# lispd example config file
#
#
# General configuration
# debug: Debug levels [0..3]
# map-request-retries: Additional Map-Requests to send per map cache miss
debug = 3
map-request-retries = 2
# 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 = {
149.20.48.77
}
# 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 = 149.20.48.77
key-type = 1
key = Mos7Knik
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 = 173.36.193.25
priority = 1
weight = 100
}
#IPv4 EID: 153.16.22.147/32
#IPv6 EID: 2610:d0:1219:128::13/128
#Map Server: 149.20.48.77
#Map Server password: Mos7Knik
#Map Resolver: 149.20.48.77
# 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.22.147/32
interface = eth9
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
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
}
# List of PITRs to SMR on handover
# address: IPv4 or IPv6 address of the Proxy-ITR
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
#}
root@ccc823:/lispmob/mylog# exit
exit
Script done on Wed Jan 7 00:00:47 1970
Script started on Tue Jan 6 22:29:46 1970
root@ccc823:/lispmob/mylog# l[Kwhich lispd
/usr/local/sbin/lispd
root@ccc823:/lispmob/mylog# lisdp -f[K[K[K[K[K[K[K[K
root@ccc823:/lispmob/mylog# lispd -f /etc/lispd.conf
INFO: LISPmob compiled for mobile node
DEBUG: Added 149.20.48.77 to map-resolver list
DEBUG-2: add_locator_to_mapping: The locator 173.36.193.25 has been added to
the EID 0.0.0.0/0.
DEBUG: Added 173.36.193.25 to proxy-etr list
DEBUG: Added 173.36.193.25 to proxy-itr list
DEBUG-3: The entry 153.16.22.147 is not a local EID
DEBUG-2: EID prefix 153.16.22.147/32 inserted in the database
DEBUG-2: lispd_get_iface_address: MN's IPv4 RLOC from interface (eth9):
128.107.130.179
DEBUG-2: open_device_binded_raw_socket: open socket 3 in interface eth9 with
afi: 2
DEBUG-2: lispd_get_iface_address: MN's IPv6 RLOC from interface (eth9):
2001:420:303:1320:2d7f:931:8463:9d2a
DEBUG-2: open_device_binded_raw_socket: open socket 4 in interface eth9 with
afi: 10
DEBUG-2: add_interface: Interface eth9 with interface index 2 added to
interfaces lists
DEBUG-2: The EID 153.16.22.147/32 has been assigned to the RLOCs of the
interface eth9
DEBUG-2: add_locator_to_mapping: The locator 128.107.130.179 has been added to
the EID 153.16.22.147/32.
DEBUG-2: The EID 153.16.22.147/32 has been assigned to the RLOCs of the
interface eth9
DEBUG-2: add_locator_to_mapping: The locator
2001:420:303:1320:2d7f:931:8463:9d2a has been added to the EID 153.16.22.147/32.
DEBUG: Balancing locator vector for 153.16.22.147/32:
DEBUG: IPv4 locators vector (1 locators): 128.107.130.179
DEBUG: IPv6 locators vector (1 locators):
2001:420:303:1320:2d7f:931:8463:9d2a
DEBUG: IPv4 & IPv6 locators vector (2 locators): 128.107.130.179
2001:420:303:1320:2d7f:931:8463:9d2a
DEBUG: Added EID 153.16.22.147 in the database.
DEBUG: Added 149.20.48.77 to map-server list
INFO: Log level: High Debug
DEBUG: ****** Summary of the configuration ******
DEBUG: ****************** LISP Local Mappings ****************
DEBUG: IDENTIFIER (EID): 153.16.22.147/32 (IID = -1)
DEBUG: | Locator (RLOC) | Status | Priority/Weight |
DEBUG: | 128.107.130.179 | Up | 1/100 |
DEBUG: | 2001:420:303:1320:2d7f:931:8463:9d2a | Up | 1/100 |
DEBUG:
DEBUG: *******************************************************
DEBUG: **************** LISP Mapping Cache ******************
DEBUG: *******************************************************
DEBUG: ******************* Map-Servers list ********************************
DEBUG: | Locator (RLOC) | Key Type |
DEBUG: | 149.20.48.77 | HMAC-SHA-1-96 |
DEBUG: ************* Map-Resolvers ***************
DEBUG: | Locator (RLOC) |
DEBUG: | 149.20.48.77 |
DEBUG: ************************* Proxy ETRs List ****************************
DEBUG: | Locator (RLOC) | Status | Priority/Weight |
DEBUG: | 173.36.193.25 | Up | 1/100 |
DEBUG: ************* Proxy-ITRs ***************
DEBUG: | Locator (RLOC) |
DEBUG: | 173.36.193.25 |
DEBUG: Balancing locator vector for 0.0.0.0/0:
DEBUG: IPv4 locators vector (1 locators): 173.36.193.25
DEBUG: IPv6 locators vector (0 locators):
DEBUG: IPv4 & IPv6 locators vector (0 locators):
DEBUG: Initializing lispd timers...
DEBUG-2: Default IPv4 iface eth9
DEBUG-2: Default IPv6 iface eth9
DEBUG-2: Default IPv4 control iface eth9: 128.107.130.179
DEBUG-2: Default IPv6 control iface eth9: 2001:420:303:1320:2d7f:931:8463:9d2a
DEBUG-3: TUN/TAP ifindex is: 5
DEBUG: TUN/TAP mtu set to 1440
DEBUG-2: Tunnel fd at creation is 7
DEBUG: TUN interface UP.
DEBUG: added 153.16.22.147 EID to TUN interface.
DEBUG: Installed default route via TUN device
DEBUG: Installed default route via TUN device
DEBUG-3: open_udp_socket: socket at creation: 8
DEBUG-3: open_udp_socket: socket at creation: 9
DEBUG-3: open_raw_input_socket: socket at creation: 10
DEBUG-3: open_udp_socket: socket at creation: 11
DEBUG-3: open_raw_input_socket: socket at creation: 12
DEBUG-3: open_udp_socket: socket at creation: 13
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Register message for 153.16.22.147/32 to Map Server 149.20.48.77
DEBUG: Reprogrammed map register in 60 seconds
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 153.16.22.147/32: Encap: N, Probe: N, SMR:
Y, SMR-inv: N
DEBUG: SMR'ing Proxy ITR 173.36.193.25 for EID 153.16.22.147/32
INFO: LISPmob (0.3.2): 'lispd' started...
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 173.36.193.25
DEBUG-3: Fordwarding native for destination 173.36.193.25
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: lookup_map_cache_node: The entry 91.189.89.134 is not found in the map
cache
DEBUG: No map cache retrieved for eid 91.189.89.134
DEBUG-2: Added map cache entry for EID: 91.189.89.134/32
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4569 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4825 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG: Retransmiting Map Request for EID: 91.189.89.134
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG: No Map Reply fot EID 91.189.89.134/32 after 2 retries. Removing map
cache entry ...
DEBUG-2: Deleting map cache entry: 91.189.89.134/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: lookup_map_cache_node: The entry 91.189.89.134 is not found in the map
cache
DEBUG: No map cache retrieved for eid 91.189.89.134
DEBUG-2: Added map cache entry for EID: 91.189.89.134/32
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4569 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4825 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG: Retransmiting Map Request for EID: 91.189.89.134
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG: No Map Reply fot EID 91.189.89.134/32 after 2 retries. Removing map
cache entry ...
DEBUG-2: Deleting map cache entry: 91.189.89.134/32
DEBUG-3: Received notification from net link
DEBUG-2: ===>process_netlink_msg: Received new address message
DEBUG: precess_address_change: New address detected for interface eth9 ->
2001:420:303:1320:204:9fff:fe02:af77
DEBUG-2: ===>process_netlink_msg: Received new address message
DEBUG: precess_address_change: New address detected for interface eth9 ->
2001:420:303:1320:2d7f:931:8463:9d2a
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: lookup_map_cache_node: The entry 91.189.89.134 is not found in the map
cache
DEBUG: No map cache retrieved for eid 91.189.89.134
DEBUG-2: Added map cache entry for EID: 91.189.89.134/32
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4569 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4825 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG: Retransmiting Map Request for EID: 91.189.89.134
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG: No Map Reply fot EID 91.189.89.134/32 after 2 retries. Removing map
cache entry ...
DEBUG-2: Deleting map cache entry: 91.189.89.134/32
DEBUG-2: *** Init SMR notification ***
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Register message for 153.16.22.147/32 to Map Server 149.20.48.77
DEBUG: Start SMR for local EID 153.16.22.147/32
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 153.16.22.147/32: Encap: N, Probe: N, SMR:
Y, SMR-inv: N
DEBUG: SMR'ing Proxy ITR 173.36.193.25 for EID 153.16.22.147/32
DEBUG-2: *** Finish SMR notification ***
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 173.36.193.25
DEBUG-3: Fordwarding native for destination 173.36.193.25
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: lookup_map_cache_node: The entry 91.189.89.134 is not found in the map
cache
DEBUG: No map cache retrieved for eid 91.189.89.134
DEBUG-2: Added map cache entry for EID: 91.189.89.134/32
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4569 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.22.147 | Orig dst: 91.189.89.134
DEBUG-3: select_src_rmt_locators_from_balancing_locators_vec: src EID:
153.16.22.147, rmt EID: 0.0.0.0, protocol: 6, src port: 4825 , dst port: 47873
--> src RLOC: 128.107.130.179, dst RLOC: 173.36.193.25
DEBUG-3: OUTPUT: Encap src: 128.107.130.179 | Encap dst: 173.36.193.25
DEBUG-3: Fordwarded eid 91.189.89.134 to petr
DEBUG: Retransmiting Map Request for EID: 91.189.89.134
DEBUG-3: open_udp_socket: socket at creation: 15
DEBUG: Sent Map-Request packet for 91.189.89.134/32: Encap: Y, Probe: N, SMR:
N, SMR-inv: N
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 149.20.48.77
DEBUG-3: Fordwarding native for destination 149.20.48.77
DEBUG: No Map Reply fot EID 91.189.89.134/32 after 2 retries. Removing map
cache entry ...
DEBUG-2: Deleting map cache entry: 91.189.89.134/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 10.21.76.61
DEBUG-3: The entry 128.107.130.179 is not a local EID
DEBUG-3: Fordwarding native for destination 10.21.76.61
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 10.21.76.61
DEBUG-3: The entry 128.107.130.179 is not a local EID
DEBUG-3: Fordwarding native for destination 10.21.76.61
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 10.21.76.61
DEBUG-3: The entry 128.107.130.179 is not a local EID
DEBUG-3: Fordwarding native for destination 10.21.76.61
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 128.107.130.179 | Orig dst: 10.21.76.61
Script started on Tue Jan 6 22:41:03 1970
]0;root@ccc823: /lispmob/mylogroot@ccc823:/lispmob/mylog# ifconfig
eth9 Link encap:Ethernet HWaddr 00:04:9f:02:af:77
inet addr:128.107.130.179 Bcast:128.107.131.255 Mask:255.255.254.0
inet6 addr: 2001:420:303:1320:2d7f:931:8463:9d2a/64 Scope:Global
inet6 addr: 2001:420:303:1320:204:9fff:fe02:af77/64 Scope:Global
inet6 addr: fe80::204:9fff:fe02:af77/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27108 errors:0 dropped:2 overruns:0 frame:0
TX packets:10584 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3767953 (3.7 MB) TX bytes:2831018 (2.8 MB)
lispTun0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:153.16.22.147 P-t-P:153.16.22.147 Mask:255.255.255.255
UP POINTOPOINT RUNNING MTU:1440 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:2775 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:0 (0.0 B) TX bytes:1023818 (1.0 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:15 errors:0 dropped:0 overruns:0 frame:0
TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1444 (1.4 KB) TX bytes:1444 (1.4 KB)
B
]0;root@ccc823: /lispmob/mylogroot@ccc823:/lispmob/mylog# ip route
0.0.0.0/1 dev lispTun0 proto static
default via 128.107.130.1 dev eth9 proto static
128.0.0.0/1 dev lispTun0 proto static
128.107.130.0/23 dev eth9 proto kernel scope link src 128.107.130.179
metric 1
169.254.0.0/16 dev eth9 scope link metric 1000
B
B
]0;root@ccc823: /lispmob/mylogroot@ccc823:/lispmob/mylog# ping
128.107.130.179[K[K
PING 128.107.130.1 (128.107.130.1) 56(84) bytes of data.
64 bytes from 128.107.130.1: icmp_req=1 ttl=255 time=0.604 ms
64 bytes from 128.107.130.1: icmp_req=2 ttl=255 time=0.575 ms
^C
--- 128.107.130.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 999ms
rtt min/avg/max/mdev = 0.575/0.589/0.604/0.028 ms
A
]0;root@ccc823: /lispmob/mylogroot@ccc823:/lispmob/mylog# ping 149.20.48.77
PING 149.20.48.77 (149.20.48.77) 56(84) bytes of data.
^C
A
D
-G-- 149.20.48.77 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8001ms
]0;root@ccc823: /lispmob/mylogroot@ccc823:/lispmob/mylog# ping
172.[K[K3.37[K7.193.25
PING 173.37.193.25 (173.37.193.25) 56(84) bytes of data.
^C
--- 173.37.193.25 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1005ms
A
