Hola Alberto, Thanks for your quick reply. I was checking sysctl net.ipv4.conf.eth0.rp_filter is set to 0
If I am using lig without lispd running it gives me the same output. But with lispd running it gives following root@lisp-router:~# lig -m 149.20.48.61 141.1.1.1 Send map-request to 149.20.48.61 for 141.1.1.1 ... Send map-request to 149.20.48.61 for 141.1.1.1 ... Send map-request to 149.20.48.61 for 141.1.1.1 ... *** No map-reply received *** root@lisp-router:~# ip route 0.0.0.0/1 dev lispTun0 proto static default via X.X.157.254 dev eth0 metric 100 X.X.156.0/23 dev eth0 proto kernel scope link src X.X.157.52 128.0.0.0/1 dev lispTun0 proto static 192.168.0.0/16 via 192.168.254.254 dev eth2 192.168.254.0/24 dev eth2 proto kernel scope link src 192.168.254.146 root@lisp-router:~# sysctl net.ipv4.conf.eth0.rp_filter net.ipv4.conf.eth0.rp_filter = 0 Debug-Output is following DEBUG: Added 149.20.48.61 to map-resolver list DEBUG: Added 149.20.48.60 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 <my-eid> is not found in the data base DEBUG-2: Identifier <my-eid>/32 inserted in the database DEBUG-3: lispd_get_iface_address: MN's IPv4 RLOC from interface (eth0): 91.66.157.52 DEBUG-2: add_interface: Interface eth0 added to interfaces lists DEBUG: Added identifier <my-eid> in the database. DEBUG-2: The entry <my-eid-ipv6> is not found in the data base DEBUG-2: Identifier <my-eid-ipv6>/128 inserted in the database DEBUG-2: The EID <my-eid-ipv6>/128 has been assigned to the RLOCs of the interface eth0 DEBUG: Added identifier <my-eid-ipv6> in the database. DEBUG: Added 217.8.97.6 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:128.223.156.134) INFO: Log level: High Debug DEBUG: ****** Summary of the configuration ****** DEBUG: *** LISP Local EIDs *** DEBUG: <my-eid>/32 (IID = -1) DEBUG: Locator State Priority/Weight DEBUG: 91.66.157.52 DEBUG: Up DEBUG: 1/100 DEBUG: DEBUG: <my-eid-ipv6>/128 (IID = -1) DEBUG: Locator State Priority/Weight DEBUG: 91.66.157.52 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: 128.223.156.134 DEBUG: Up DEBUG: 1/100 DEBUG: 0/0 DEBUG: DEBUG: *** Map-Servers list: *** DEBUG: 217.8.97.6 key-type: 1 DEBUG: *** Map-Resolvers *** DEBUG: 149.20.48.61 DEBUG: *** Proxy ETRs List *** DEBUG: 149.20.48.60 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 eth0 DEBUG-2: Default IPv4 control iface eth0 DEBUG-3: TUN/TAP ifindex is: 8 DEBUG: TUN/TAP mtu set to 1450 DEBUG-2: Tunnel fd at creation is 6 DEBUG: LISP EID v4 address <my-eid> 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: Sent map register for <my-eid>/32 to maps server 217.8.97.6 DEBUG-3: open_udp_socket: socket at creation: 9 DEBUG: Sent map register for <my-eid-ipv6>/128 to maps server 217.8.97.6 DEBUG: Reprogrammed map register for <my-eid-ipv6>/128 in 60 seconds INFO: LISPmob: 'lispd' started... DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 217.8.97.6 DEBUG-3: Fordwarding native for destination 217.8.97.6 DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 217.8.97.6 DEBUG-3: Fordwarding native for destination 217.8.97.6 DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 149.20.48.61 DEBUG-3: Fordwarding native for destination 149.20.48.61 DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 149.20.48.61 DEBUG-3: Fordwarding native for destination 149.20.48.61 DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 149.20.48.61 DEBUG-3: Fordwarding native for destination 149.20.48.61 DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: Recieved something in the timer fd DEBUG-3: open_udp_socket: socket at creation: 9 DEBUG: Sent map register for <my-eid>/32 to maps server 217.8.97.6 DEBUG-3: open_udp_socket: socket at creation: 9 DEBUG: Sent map register for <my-eid-ipv6>/128 to maps server 217.8.97.6 DEBUG: Reprogrammed map register for <my-eid-ipv6>/128 in 60 seconds DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 217.8.97.6 DEBUG-3: Fordwarding native for destination 217.8.97.6 DEBUG-3: Recieved packet in the tun buffer DEBUG-3: Packet received dst. to: 217.8.97.6 DEBUG-3: Fordwarding native for destination 217.8.97.6 DEBUG: Terminal interrupt. Cleaning up... ...... So I don't have a clue what it is. The only thing I see is, that all communication is blocked when lispd is running. As soon as I stop it routing works again. The Kabeldeutschland IP is a routeable public IP. I tried to ssh it from my Deutsche Telekom Address (which is another german provider) with no problem. BTW. Is it possible to run lispd on top of only a ipv6 address ? So I could try to put an ipv6 tunnel into the VM. Bueno, gracias. Stefan Am 20.02.2013 um 14:15 schrieb Alberto Rodríguez-Natal <[email protected]>: > Hi Stefan, > > First of all, thank you for your interest in LISPmob! > > Everything seems fine in your configuration, I'm a bit puzzled why it is not > working. We use Ubuntu 12.04 too for our tests, so it's not a problem of the > OS. Let me ask you to perform a few steps to try to figure out what's > happening. > > Just to be sure, check if rp_filter option is disabled before running > LISPmob: > sysctl net.ipv4.conf.eth0.rp_filter. > If it is enabled, please disable it with: > sudo sysctl net.ipv4.conf.eth0.rp_filter=0 > > Try querying the Mapping System with "lig" to see if you can get any > Map-Reply in your vm. > Compile it from https://github.com/LISPmob/lig and run it with "./lig -m > [map-resolver] [EID]". You should see something like this: > > root@lisp-mob10:/home/lisp/lig# ./lig -m 149.20.48.61 141.1.1.1 > Send map-request to 149.20.48.61 for 141.1.1.1 ... > Received map-reply from 149.20.48.61 with rtt 0.18500 secs > Mapping entry for EID '141.1.1.1': > 128.0.0.0/4, instance ID: 0, via map-reply, record ttl: 4, not auth, not > mobile > Negative cache entry, action: forward-native > > You can also try to run LISPmob with the highest debug level (lispd -d 3) and > forward us the output (beware, with data traffic that will provide a huge > amount of output :P). > > We'll be waiting for your reply! > > Best, > Alberto > > > On 20 February 2013 11:23, Stefan Sachse <[email protected]> wrote: > Hello to all, > I am quite exited about this project. > Last week Lori was so kind to grant me access to the beta-network. > So for Testing I set up a vm with > Ubuntu 12.04.2 LTS > Gave it a routeable public IP from Kabel-Deutschland on my eth0 > > eth0 Link encap:Ethernet Hardware Adresse 00:0c:29:X:X:X > inet Adresse:X.X.157.X Bcast:X.X.157.255 Maske:255.255.254.0 > UP BROADCAST RUNNING MULTICAST MTU:576 Metrik:1 > RX packets:7588 errors:0 dropped:0 overruns:0 frame:0 > TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:1000 > RX-Bytes:505127 (505.1 KB) TX-Bytes:2564 (2.5 KB) > > > My /etc/lispd.conf is following > > # > # lispd config > # > debug = 2 # Debug level [0..3] > map-request-retries = 4 # send 2 before giving up > > # > # LISP Config > # > > # Encapsulated Map-Requests are sent to this map resolver > #map-resolver = 217.8.98.42 # intouch-ams-mr-ms > #map-resolver = 195.50.116.18 # intouch-ams-mr-ms > #map-resolver = 173.36.254.164 # intouch-ams-mr-ms > map-resolver = 149.20.48.61 # intouch-ams-mr-ms > > # Register to this map server > map-server { > address = 217.8.97.6 # intouch-mn-rtr > key-type = 1 # SHA1 > key = XXXXXXX # intentionally blanked ;-) > 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 # intouch-pxtr-1 > address = 149.20.48.60 # intouch-pxtr-1 > priority = 1 > weight = 100 > } > > # IPv4 EID of the mobile node > database-mapping { > eid-prefix = XXXXXXXXXXXXXX > interface = eth0 > priority_v4 = 1 > weight_v4 = 100 > priority_v6 = 1 > weight_v6 = 100 > } > > # IPv6 EID of the mobile node > database-mapping { > eid-prefix = XXXXXXXXXXXXXX > interface = eth0 > 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 = 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 > } > > There is no firewall active ! > > As soon as I start > udo lispd -f /etc/lispd.conf > > I have following route entries > > stefan@lisp-router:~$ ip route > 0.0.0.0/1 dev lispTun0 proto static > default via X.X.157.254 dev eth0 metric 100 > X.X.156.0/23 dev eth0 proto kernel scope link src X.X.157.X > 128.0.0.0/1 dev lispTun0 proto static > > The lispTun0 is up and running And gets registered on the map-server > > But > > lispTun0 Link encap:UNSPEC Hardware Adresse > 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 > inet Adresse:XXXXXX P-z-P:XXXXXXX Maske:255.255.255.255 > UP PUNKTZUPUNKT RUNNING MTU:1450 Metrik:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 > Kollisionen:0 Sendewarteschlangenlänge:500 > RX-Bytes:0 (0.0 B) TX-Bytes:196 (196.0 B) > > Does not receive any packets ! > > I can ping lispTun0 from the localhost, but not from another ..... > As soon as I try to ping another IP, like > 141.1.1.1 > I get those debug messages > EBUG: Sent Map-Request packet for 141.1.1.1/32 > DEBUG: Sent Map-Request packet for 141.1.1.1/32 > DEBUG: Retransmiting Map Request for EID: 141.1.1.1 > DEBUG: Sent Map-Request packet for 141.1.1.1/32 > DEBUG: No Map Reply fot EID 141.1.1.1/32 after 2 retries. Removing map cache > entry ... > DEBUG-2: Deleting map cache EID entry 141.1.1.1/32 > DEBUG: No map cache retrieved for eid 141.1.1.1 > DEBUG-2: Added map cache entry for EID: 141.1.1.1/32 > DEBUG: Sent Map-Request packet for 141.1.1.1/32 > DEBUG: Sent Map-Request packet for 141.1.1.1/32 > DEBUG: Retransmiting Map Request for EID: 141.1.1.1 > DEBUG: Sent Map-Request packet for 141.1.1.1/32 > DEBUG: No Map Reply fot EID 141.1.1.1/32 after 2 retries. Removing map cache > entry ... > > And lispTun0 never receives any packet !! > > I guess I just missed some routing but I don't have any Idea what I could > have missed ..... > As soon as I shutdown lispd everything works again like expected ..... > Its reachable via its public IP and I can ping any address from localhost > > > Thanks for your help > > Stefan Sachse > > >
