Hi Albert, Unfortunatly, it doesn't work... I'll continue to track the problem.
Again, thank you ... Carole ________________________________ De : Albert López <[email protected]> Envoyé : mardi 3 juin 2014 12:04 À : Carole BONAN; [email protected] Objet : Re: [LISPmob-users] LISPmob router on Ubuntu Hi Carole, I think that the problem is that the router is sending the control messages through eth1 interface. If you could check using wireshark .... May be in a future we will add a control interface, meanwhile I think that if you add this to de configuration file it could work. database-mapping { eid-prefix = 1.1.1.0/30 interface = eth0 priority_v4 = 2 # 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 = 2 # 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 } database-mapping { eid-prefix = 1.1.1.0/30 interface = eth1 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 } Order is important. When LISPmob selects the default interface, it will use the first interface UP: eth0 When LISPmob sends data traffic, it will use priority and weight. As interface eth1 is preferable to eth0, it will use eth1 to send traffic Let me know if it works. Regards Albert On 06/03/2014 11:08 AM, Carole BONAN wrote: Albert, Thank you very much for the time you spent on my problem. Here are the files/logs you asked me: ip config (ifconfig command) : eth0 Link encap:Ethernet HWaddr 08:00:27:f7:a2:8f inet adr:192.168.100.4 Bcast:192.168.100.255 Masque:255.255.255.0 adr inet6: fe80::a00:27ff:fef7:a28f/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Packets reçus:94 erreurs:0 :0 overruns:0 frame:0 TX packets:70 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 Octets reçus:13944 (13.9 KB) Octets transmis:10906 (10.9 KB) eth1 Link encap:Ethernet HWaddr 08:00:27:aa:fa:c6 inet adr:192.168.2.1 Bcast:192.168.2.255 Masque:255.255.255.0 adr inet6: fe80::a00:27ff:feaa:fac6/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Packets reçus:56 erreurs:0 :0 overruns:0 frame:0 TX packets:151 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 Octets reçus:9994 (9.9 KB) Octets transmis:18616 (18.6 KB) eth2 Link encap:Ethernet HWaddr 08:00:27:2d:33:87 inet adr:192.168.1.4 Bcast:192.168.1.255 Masque:255.255.255.0 adr inet6: fe80::a00:27ff:fe2d:3387/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Packets reçus:94 erreurs:0 :0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:1000 Octets reçus:20057 (20.0 KB) Octets transmis:7228 (7.2 KB) lispTun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 UP POINTOPOINT RUNNING MTU:1440 Metric:1 Packets reçus:0 erreurs:0 :0 overruns:0 frame:0 TX packets:31 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:500 Octets reçus:0 (0.0 B) Octets transmis:3224 (3.2 KB) lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:Hôte UP LOOPBACK RUNNING MTU:65536 Metric:1 Packets reçus:1456 erreurs:0 :0 overruns:0 frame:0 TX packets:1456 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 Octets reçus:116480 (116.4 KB) Octets transmis:116480 (116.4 KB) routes: (route -n): Destination Passerelle Genmask Indic Metric Ref Use Iface 1.1.1.0 0.0.0.0 255.255.255.252 U 0 0 0 lispTun0 10.51.80.0 192.168.100.2 255.255.255.0 UG 0 0 0 eth0 10.51.85.0 192.168.100.3 255.255.255.0 UG 0 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1 192.168.3.0 192.168.2.2 255.255.255.0 UG 0 0 0 eth1 192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 ip rules : 0: from all lookup local 3: from 192.168.2.1 lookup 3 32766: from all lookup main 32767: from all lookup default PxTR configuration file: debug = 3 map-request-retries = 2 pxtr-mode = on rloc-probing { rloc-probe-interval = 0 rloc-probe-retries = 2 rloc-probe-retries-interval = 5 } nat-traversal { nat_aware = off site_ID = 0000000000000001 #In doubt, keep the default value xTR_ID = 00000000000000000000000000000001 #In doubt, keep the default value } map-resolver = {192.168.100.1} map-server { address = 192.168.100.1 key-type = 1 key = XXXXXXXXXXXXX proxy-reply = on } database-mapping { eid-prefix = 1.1.1.0/30 interface = eth1 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 } and logs of the PxTR (level 3) INFO: LISPmob v0.4 compiled for Linux DEBUG: RLOC Probing dissabled DEBUG: converted addr_str [192.168.100.1] to address [192.168.100.1] DEBUG: Added 192.168.100.1 to map-resolver list DEBUG-3: The entry 1.1.1.0 is not a local EID DEBUG-2: EID prefix 1.1.1.0/30 inserted in the database DEBUG-2: lispd_get_iface_address: IPv4 RLOC from interface (eth1): 192.168.2.1 DEBUG-2: open_device_binded_raw_socket: open socket 5 in interface eth1 with afi: 2 DEBUG: add_rule: Added rule in ip rule table for source routing of src prefix: 192.168.2.1/32 DEBUG-2: lispd_get_iface_address: interface address from eth1 discarded (fe80::a00:27ff:fef7:a28f) DEBUG-2: lispd_get_iface_address: interface address from eth1 discarded (fe80::a00:27ff:feaa:fac6) DEBUG-2: lispd_get_iface_address: interface address from eth1 discarded (fe80::a00:27ff:fe2d:3387) DEBUG-3: lispd_get_iface_address: No IPv6 RLOC configured for interface eth1 DEBUG-2: add_interface: Interface eth1 with interface index 3 added to interfaces lists DEBUG-2: The EID 1.1.1.0/30 has been assigned to the RLOCs of the interface eth1 DEBUG-3: add_locator_to_mapping: The locator 192.168.2.1 has been added to the EID 1.1.1.0/30. DEBUG-2: The EID 1.1.1.0/30 has been assigned to the RLOCs of the interface eth1 DEBUG: Balancing locator vector for 1.1.1.0/30: DEBUG: IPv4 locators vector (1 locators): 192.168.2.1 DEBUG: IPv6 locators vector (0 locators): DEBUG: IPv4 & IPv6 locators vector (0 locators): DEBUG: Added EID 1.1.1.0 in the database. DEBUG: converted addr_str [192.168.100.1] to address [192.168.100.1] DEBUG: Added 192.168.100.1 to map-server list WARNING: No Proxy-ETR defined. Packets to non-LISP destinations will be forwarded natively (no LISP encapsulation). This may prevent mobility in some scenarios. INFO: Log level: High Debug DEBUG: ****** Summary of the configuration ****** DEBUG: ****************** LISP Local Mappings **************** DEBUG: IDENTIFIER (EID): 1.1.1.0/30 (IID = 0) DEBUG: | Locator (RLOC) | Status | Priority/Weight | DEBUG: | 192.168.2.1 | Up | 1/100 | DEBUG: DEBUG: ******************************************************* DEBUG: **************** LISP Mapping Cache ****************** DEBUG: ******************************************************* DEBUG: ******************* Map-Servers list ******************************** DEBUG: | Locator (RLOC) | Key Type | DEBUG: | 192.168.100.1 | HMAC-SHA-1-96 | DEBUG: ************* Map-Resolvers *************** DEBUG: | Locator (RLOC) | DEBUG: | 192.168.100.1 | DEBUG-2: Droping referral cache... DEBUG-2: Default IPv4 iface eth1 DEBUG-2: Default IPv4 control iface eth1: 192.168.2.1 DEBUG-3: TUN/TAP ifindex is: 7 DEBUG: TUN/TAP mtu set to 1440 DEBUG-2: Tunnel fd at creation is 6 DEBUG: TUN interface UP. DEBUG: add_route: added route to the system: src addr: -, dst prefix:1.1.1.0/30, gw: -, table: 254 DEBUG-3: open_udp_socket: socket at creation: 7 DEBUG-3: open_raw_input_socket: socket at creation: 8 DEBUG-3: open_udp_socket: socket at creation: 9 DEBUG-3: open_udp_socket: socket at creation: 10 DEBUG-3: open_raw_input_socket: socket at creation: 11 DEBUG-3: open_udp_socket: socket at creation: 12 INFO: LISPmob (v0.4): 'lispd' started... INFO: Running as an xTR router 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 (eth2) 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 (eth0) 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: Finish pocessing netlink 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 (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 (eth0) 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: Finish pocessing netlink message DEBUG-3: Received IPv4 packet in the control input buffer (4342) DEBUG-2: Received a LISP control message DEBUG: Received a LISP Map-Request message DEBUG-3: lookup_map_cache_node: The entry 1.1.1.1 is not found in the map cache DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: lookup_map_cache_node: The entry 1.1.1.1 is not found in the map cache DEBUG: No map cache retrieved for eid 1.1.1.1 DEBUG-2: Added map cache entry for EID: 1.1.1.1/32 DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd99cef77-0x77ef8d7f DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: Retransmiting Map Request for EID: 1.1.1.1 (1 retries) DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd8bfd0be-0xbedcaf7f DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: Retransmiting Map Request for EID: 1.1.1.1 (2 retries) DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd6ac3087-0xafbcbd7f DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: Retransmiting Map Request for EID: 1.1.1.1 (3 retries) DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd4bf7024-0x2cfcaf7f DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: No Map Reply for EID 1.1.1.1/32 after 3 retries. Removing map cache entry ... DEBUG-2: Deleting map cache entry: 1.1.1.1/32 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: lookup_map_cache_node: The entry 1.1.1.1 is not found in the map cache DEBUG: No map cache retrieved for eid 1.1.1.1 DEBUG-2: Added map cache entry for EID: 1.1.1.1/32 DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd17822dd-0xffaeed7f DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: Retransmiting Map Request for EID: 1.1.1.1 (1 retries) DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0xd0a0212e-0x3eadbd7f DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: Retransmiting Map Request for EID: 1.1.1.1 (2 retries) DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0x2ebed29a-0xbadeaf7f DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: Retransmiting Map Request for EID: 1.1.1.1 (3 retries) DEBUG: Sent Map-Request packet for 1.1.1.1/32 to 192.168.100.1: Encap: Y, Probe: N, SMR: N, SMR-inv: N . Nonce: 0x2ca149cf-0xffcdbd7f DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 DEBUG-3: fordward_to_petr: Proxy-etr not found DEBUG-3: Fordwarding native for destination 1.1.1.1 DEBUG: No Map Reply for EID 1.1.1.1/32 after 3 retries. Removing map cache entry ... DEBUG-2: Deleting map cache entry: 1.1.1.1/32 DEBUG-3: INPUT (4341): Inner src: 1.1.1.1 | Inner dst: 192.168.3.2 DEBUG-3: Received packet in the tun buffer DEBUG-3: OUTPUT: Orig src: 192.168.3.2 | Orig dst: 1.1.1.1 INFO: Exiting ... Best regards, Carole ________________________________ De : Albert López <[email protected]><mailto:[email protected]> Envoyé : mardi 3 juin 2014 09:35 À : Carole BONAN; [email protected]<mailto:[email protected]> Objet : Re: [LISPmob-users] LISPmob router on Ubuntu If I understood correctly, the problem is in the PiTR functionality. Do you have configured in the PxTR the database mapping of your EIDs? To implement the PiTR functionality we add a route into the routing table to send all traffic whose destination is an EID (configured in the configuration file as a database mapping) into the tun interface. If you already have this configured, then I will need you to send me the logs of the PxTR (level 3), the configuration file (removing the password) and the routing information: ip r, ip a , ip rule. Best regards Albert
