Dear Albert,

I forgot to mention that i am connected to the internet from my school network. So to get access to the internet, i must pass through the gateway. I tried to use its address as RLOC (address returned by the command : host proxy ), but it still does not work !

i used also my phone as a router and its address as RLOC, but i does not work either.

How can i get a "publicly routable RLOC" as you said, since i am not directly connected to the internet ?

Best regards ,

Anas

On Mon, 04 Mar 2013 09:23:11 +0100, Albert López wrote:
Dear Anas,

The current implementation of LISPmob requires that the host has a
publicly routable RLOC, which is neither firewalled, nor behind NAT.
The encapsulated or data packets you are sending are using the private
address as RLOC. As a consequence of this, other nodes doesn't know
how to reach your pc.
Regarding the Encapsulated Map Request that you see, they are
probably generated by your operation system or applications you have
installed. Once LISPmob is running, the routing table is modified to
all packets go through the lisptun0 interface. If no map cache entry
is found for this entry, an encapsulated map request is generated. As
you don't receive the map replay due to the private address of the
RLOC, this encapsulated map request are continuously generated as long
new packets are received in the lisp tun interface.

Regards

Albert

On 03/01/2013 04:43 PM, Zakki Anas wrote:
Hello everybody,

I am currently working on LISP and trying to implement it using the LISPmob solution.

I am actually facing some problems and would be very happy if someone could help me resolving them.

My configuration :

• I am using the following EID : 153.16.254.1/32
• my RLOC : 172.20.10.4 (since i am connected to the internet at home and this is the private address assigned by my router OR shall i use its address ? ) • the mapping system (Map server - Map resolver) : 217.8.98.46 (retrieved from http://www.lisp4.net/images/lisp-ddt.pdf)

The problems noticed :

• I can see a map register with my EID towards the map server when LISPmob starts. • Then immediately, there are several Encapsulated Map Request sent to those addresses 62.201.129.203 and 62.201.129.201 ( although i am not sending anything to them at all ! )

Please find below the configuration file lispd.conf and the logs, and attached a wireshark capture of the traffic i am seeing on my wireless interface.

Best regards,

Anas ZAKKI

-- lispd.conf :

#
# LISP Config
#
# Encapsulated Map-Requests are sent to this map resolver
map-resolver = 217.8.98.46
# Register to this map server
map-server {
address     = 217.8.98.46     # 128.223.156.35
key-type = 1     # SHA1
key     = foo%bar
proxy-reply = on     # ask ms to proxy reply
}
# Encapsulate packets for non-LISP sites to this Proxy-ETR
proxy-etr {
address = 217.8.98.33
priority = 1
weight = 100
}
# IPv4 EID of the mobile node
database-mapping {
eid-prefix = 153.16.254.1/32
interface = wlan0
priority_v4    = 1
weight_v4 = 100
priority_v6    = 1
weight_v6 = 100
}
# Static cache entries
static-map-cache {
eid-prefix = 153.16.10.0/24
rloc = 172.20.10.4     #128.223.156.134
priority = 1
weight = 100
}
# List of PITRs to SMR on handover
proxy-itrs = {
69.31.31.98,     # eqx-ash-pxtr
149.20.48.60,     # isc-pxtr
198.6.255.37,     # asp-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
}



--Logs :

root@ubuntu:/home/pape# lispd -f /etc/lispd.conf -d 3
DEBUG: Added 217.8.98.46 to map-resolver list
DEBUG: Added 217.8.98.33 to proxy-etr list
DEBUG: Added 69.31.31.98 to proxy-itr list
DEBUG: Added 149.20.48.60 to proxy-itr list
DEBUG: Added 198.6.255.37 to proxy-itr list
DEBUG: Added 129.250.1.63 to proxy-itr list
DEBUG: Added 217.8.98.33 to proxy-itr list
DEBUG: Added 217.8.98.35 to proxy-itr list
DEBUG: Added 193.162.145.46 to proxy-itr list
DEBUG: Added 158.38.1.92 to proxy-itr list
DEBUG: Added 203.181.249.172 to proxy-itr list
DEBUG-2: The entry 153.16.254.1 is not found in the data base
DEBUG-2: Identifier 153.16.254.1/32 inserted in the database
DEBUG-3: lispd_get_iface_address: MN's IPv4 RLOC from interface (wlan0): 172.20.10.4 DEBUG: lispd_get_iface_address: interface address discarded (fe80::7add:8ff:fee0:cacb) DEBUG-3: lispd_get_iface_address: No IPv6 RLOC configured for interface wlan0
DEBUG-2: add_interface: Interface wlan0 added to interfaces lists
DEBUG: Added identifier 153.16.254.1 in the database.
DEBUG: Added 217.8.98.46 to map-server list
DEBUG-2: Added map cache entry for EID: 153.16.10.0/24
DEBUG: Added static-map-cache (EID:153.16.10.0 -> RLOC:172.20.10.4)
INFO: Log level: High Debug
DEBUG: ****** Summary of the configuration ******
DEBUG: *** LISP Local EIDs ***
DEBUG: 153.16.254.1/32 (IID = -1)

DEBUG: Locator State Priority/Weight
DEBUG: 172.20.10.4
DEBUG: Up
DEBUG: 1/100
DEBUG:
DEBUG: *** LISP Mapping Cache ***
DEBUG: 153.16.10.0/24 (IID = 0),
DEBUG: uptime: 01:00:00, expires: 05:15:00, via
DEBUG: static
DEBUG: active: Yes
DEBUG: Locator State Priority/Weight Data In/Out 1
DEBUG: 172.20.10.4
DEBUG: Up
DEBUG: 1/100
DEBUG: 0/0
DEBUG:
DEBUG: *** Map-Servers list: ***
DEBUG: 217.8.98.46 key-type: 1
DEBUG: *** Map-Resolvers ***
DEBUG: 217.8.98.46
DEBUG: *** Proxy ETRs List ***
DEBUG: 217.8.98.33 priority: 1 weight: 100
DEBUG: *** Proxy-ITRs ***
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: 198.6.255.37
DEBUG: 149.20.48.60
DEBUG: 69.31.31.98
DEBUG-2: Default IPv4 iface wlan0
DEBUG-2: Default IPv4 control iface wlan0
DEBUG-3: TUN/TAP ifindex is: 9
DEBUG: TUN/TAP mtu set to 1440
DEBUG-2: Tunnel fd at creation is 6
DEBUG: TUN interface UP.
DEBUG: added 153.16.254.1 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: 7
DEBUG-3: open_udp_socket: socket at creation: 8
DEBUG-3: open_udp_socket: socket at creation: 9
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent map register for 153.16.254.1/32 to maps server 217.8.98.46
DEBUG: Reprogrammed map register for 153.16.254.1/32 in 60 seconds
INFO: LISPmob: 'lispd' started...
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.254.1 | Orig dst: 62.201.129.203
DEBUG-3: lookup_eid_cache_node: The entry 62.201.129.203 is not found in the map cache
DEBUG: No map cache retrieved for eid 62.201.129.203
DEBUG-2: Added map cache entry for EID: 62.201.129.203/32
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.203/32
DEBUG-3: OUTPUT: Encap src: 172.20.10.4 | Encap dst: 217.8.98.33
DEBUG-3: Fordwarded eid 62.201.129.203 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.254.1 | Orig dst: 62.201.129.201
DEBUG-3: lookup_eid_cache_node: The entry 62.201.129.201 is not found in the map cache
DEBUG: No map cache retrieved for eid 62.201.129.201
DEBUG-2: Added map cache entry for EID: 62.201.129.201/32
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.201/32
DEBUG-3: OUTPUT: Encap src: 172.20.10.4 | Encap dst: 217.8.98.33
DEBUG-3: Fordwarded eid 62.201.129.201 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.203/32
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.201/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG: Retransmiting Map Request for EID: 62.201.129.203
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.203/32
DEBUG: Retransmiting Map Request for EID: 62.201.129.201
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.201/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG: No Map Reply fot EID 62.201.129.203/32 after 2 retries. Removing map cache entry ...
DEBUG-2: Deleting map cache EID entry 62.201.129.203/32
DEBUG: No Map Reply fot EID 62.201.129.201/32 after 2 retries. Removing map cache entry ...
DEBUG-2: Deleting map cache EID entry 62.201.129.201/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.254.1 | Orig dst: 62.201.129.203
DEBUG-3: lookup_eid_cache_node: The entry 62.201.129.203 is not found in the map cache
DEBUG: No map cache retrieved for eid 62.201.129.203
DEBUG-2: Added map cache entry for EID: 62.201.129.203/32
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.203/32
DEBUG-3: OUTPUT: Encap src: 172.20.10.4 | Encap dst: 217.8.98.33
DEBUG-3: Fordwarded eid 62.201.129.203 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 153.16.254.1 | Orig dst: 62.201.129.201
DEBUG-3: lookup_eid_cache_node: The entry 62.201.129.201 is not found in the map cache
DEBUG: No map cache retrieved for eid 62.201.129.201
DEBUG-2: Added map cache entry for EID: 62.201.129.201/32
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.201/32
DEBUG-3: OUTPUT: Encap src: 172.20.10.4 | Encap dst: 217.8.98.33
DEBUG-3: Fordwarded eid 62.201.129.201 to petr
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.203/32
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.201/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG: Retransmiting Map Request for EID: 62.201.129.203
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.203/32
DEBUG: Retransmiting Map Request for EID: 62.201.129.201
DEBUG-3: open_udp_socket: socket at creation: 10
DEBUG: Sent Map-Request packet for 62.201.129.201/32
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG-3: Received packet in the tun buffer
DEBUG-3: OUTPUT: Orig src: 172.20.10.4 | Orig dst: 217.8.98.46
DEBUG-3: Fordwarding native for destination 217.8.98.46
DEBUG: No Map Reply fot EID 62.201.129.203/32 after 2 retries. Removing map cache entry ...
DEBUG-2: Deleting map cache EID entry 62.201.129.203/32
DEBUG: No Map Reply fot EID 62.201.129.201/32 after 2 retries. Removing map cache entry ...
DEBUG-2: Deleting map cache EID entry 62.201.129.201/32
^CDEBUG: Terminal interrupt. Cleaning up...

--
Anas ZAKKI

Élève-ingénieur en dernière année à l'ENSEEIHT
Département des Télécoms et réseaux
[email protected]
+33 6 66 84 07 07

Reply via email to