I can't neither ping the Map-Server.. 
Anyway looks like the mapping request-reply mechanism doesn't work..


Ah, a theoretical unrelated question: after the mapping lookup in the map 
server, if a lisp mob client receives a reply, does it store it in a cache?

Daniele



On 15/mag/2013, at 14:06, Daniele wrote:

> Great, this was useful..
> 
> So now I am correctly registered (as you can see here) but I can't ping any 
> other EID, and I can't neither ping it from my other LISP site.
> 
> Again, thanks for the help.
> Daniele
> 
> 
> On 15/mag/2013, at 12:55, Albert López wrote:
> 
>> This information should be in the mail that Lori sent to you with the 
>> configuration information, key,...
>> You can check the map-server that you should use here. Search your EID and 
>> in the first column you will find the Map-Server that you should use. To get 
>> the ip of the assigned Map-Server you could use "host map-server" where 
>> map-server is the name appearing in the firs column plus rloc.lisp4.net. For 
>> instance: asp-mr-ms    -> asp-mr-ms.rloc.lisp4.net
>> 
>> Regards
>> 
>> Albert
>> 
>> On 05/15/2013 12:23 PM, Daniele wrote:
>>> Inside the lispd.config file I put this address as a map-server/resolver 
>>> address: 193.162.145.50, is that correct?
>>> 
>>> (I'll check out the lig command)
>>> 
>>> Kind regards
>>> Daniele
>>> 
>>>  
>>> On 15/mag/2013, at 12:15, Albert López wrote:
>>> 
>>>> May be the problem is a firewall. Try to check if you could get an answer 
>>>> using lig. For instance, you could check if you get answer to: lig -m 
>>>> 195.50.116.18 153.16.10.11
>>>> On the other side, you can use wireshark listening to eth0 to see if 
>>>> map-registers are sent and if you receive map-notify.
>>>> 
>>>> Regards
>>>> 
>>>> Albert
>>>> 
>>>> 
>>>> On 05/15/2013 11:10 AM, Daniele wrote:
>>>>> Thanks Albert for the reply, in this moment i temporarily disabled the 
>>>>> wifi interface to isolate the issue. This is the routing table now:
>>>>> 
>>>>> Kernel IP routing table
>>>>> Destination     Gateway         Genmask         Flags Metric Ref    Use 
>>>>> Iface
>>>>> 0.0.0.0         0.0.0.0         128.0.0.0       U     0      0        0 
>>>>> lispTun0
>>>>> 0.0.0.0         151.100.122.1   0.0.0.0         UG    100    0        0 
>>>>> eth0
>>>>> 128.0.0.0       0.0.0.0         128.0.0.0       U     0      0        0 
>>>>> lispTun0
>>>>> 151.100.122.0   0.0.0.0         255.255.255.0   U     0      0        0 
>>>>> eth0
>>>>> 169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 
>>>>> eth0
>>>>> 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 
>>>>> virbr0
>>>>> 
>>>>> Now it seems well configured, but i can't ping any EID, and checking in 
>>>>> the lispmon website i don't get any map reply from the London Map Server 
>>>>> looking for my /32 EID. That means I'm not registering..
>>>>> I can only ping my subnet, obviously, since it's directly connected to 
>>>>> eth0 interface.
>>>>> 
>>>>> Thanks 
>>>>> Daniele
>>>>> 
>>>>> 
>>>>> 
>>>>> On 15/mag/2013, at 10:06, Albert López wrote:
>>>>> 
>>>>>> Dear Daniele,
>>>>>> 
>>>>>> The interface you should use in the database-mapping structure of the 
>>>>>> configuration file is the one containing the locators. This interface 
>>>>>> should have a public IP address and a gateway assigned.
>>>>>> From the information you have provided, the interface eth0 doesn't have 
>>>>>> a default route assigned. You should assign a default route to the 
>>>>>> interface eth0 with a less priority metric than wlan0 (higher number). 
>>>>>> Let us know if this resolve the problem
>>>>>> 
>>>>>> Regards
>>>>>> 
>>>>>> Albert L.
>>>>>> 
>>>>>> On 05/14/2013 07:36 PM, Daniele wrote:
>>>>>>> 
>>>>>>> 
>>>>>>> What does 'ifconfig -a' show now?
>>>>>>> 
>>>>>>> -Lori
>>>>>>> 
>>>>>>> 
>>>>>>> Dear Lori, apparently the interfaces are correctly configured. This is 
>>>>>>> what ifconfig returns while lispd is running (I'd like to use the eth0 
>>>>>>> interface for LISP and the wireless interface to stay connected to the 
>>>>>>> internet):
>>>>>>> 
>>>>>>> eth0      Link encap:Ethernet  HWaddr 00:1d:ba:1c:ac:27  
>>>>>>>           inet addr:1 <my public IP>  Bcast:0.0.0.0  
>>>>>>> Mask:255.255.255.255
>>>>>>>           inet6 addr: fe80::21d:baff:fe1c:ac27/64 Scope:Link
>>>>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>>>>           RX packets:17974 errors:0 dropped:382 overruns:0 frame:0
>>>>>>>           TX packets:5260 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:3 txqueuelen:1000 
>>>>>>>           RX bytes:1757884 (1.7 MB)  TX bytes:228362 (228.3 KB)
>>>>>>>           Interrupt:16 
>>>>>>> 
>>>>>>> lispTun0  Link encap:UNSPEC  HWaddr 
>>>>>>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
>>>>>>>           inet addr: <my EID>  P-t-P:153.16.44.120  Mask:255.255.255.255
>>>>>>>           inet6 addr: 2610:d0:ffff:192::1/128 Scope:Global
>>>>>>>           UP POINTOPOINT RUNNING  MTU:1440  Metric:1
>>>>>>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>>>>           TX packets:2398 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:500 
>>>>>>>           RX bytes:0 (0.0 B)  TX bytes:168268 (168.2 KB)
>>>>>>> 
>>>>>>> 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:7135 errors:0 dropped:0 overruns:0 frame:0
>>>>>>>           TX packets:7135 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:0 
>>>>>>>           RX bytes:666361 (666.3 KB)  TX bytes:666361 (666.3 KB)
>>>>>>> 
>>>>>>> virbr0    Link encap:Ethernet  HWaddr c2:f8:64:5d:92:1d  
>>>>>>>           inet addr:192.168.122.1  Bcast:192.168.122.255  
>>>>>>> Mask:255.255.255.0
>>>>>>>           UP BROADCAST MULTICAST  MTU:1500  Metric:1
>>>>>>>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>>>>>>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:0 
>>>>>>>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>>>>>>> 
>>>>>>> wlan0     Link encap:Ethernet  HWaddr 00:16:ea:25:f1:70  
>>>>>>>           inet addr:10.0.1.31  Bcast:10.0.1.255  Mask:255.255.255.0
>>>>>>>           inet6 addr: fe80::216:eaff:fe25:f170/64 Scope:Link
>>>>>>>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>>>>>>           RX packets:7599 errors:0 dropped:0 overruns:0 frame:0
>>>>>>>           TX packets:6219 errors:0 dropped:0 overruns:0 carrier:0
>>>>>>>           collisions:0 txqueuelen:1000 
>>>>>>>           RX bytes:5640735 (5.6 MB)  TX bytes:1268953 (1.2 MB)
>>>>>>> 
>>>>>>> 
>>>>>>> Anyway i can't ping any other LISP site, my EID doesn't appear in the 
>>>>>>> London Map Server, and also my wifi connection stops working. I guess 
>>>>>>> it is due to some conflict in the routing table
>>>>>>> 
>>>>>>> Kernel IP routing table
>>>>>>> Destination     Gateway         Genmask         Flags Metric Ref    Use 
>>>>>>> Iface
>>>>>>> 0.0.0.0         0.0.0.0         128.0.0.0       U     0      0        0 
>>>>>>> lispTun0
>>>>>>> 0.0.0.0         10.0.1.1        0.0.0.0         UG    0      0        0 
>>>>>>> wlan0
>>>>>>> 10.0.1.0        0.0.0.0         255.255.255.0   U     2      0        0 
>>>>>>> wlan0
>>>>>>> 128.0.0.0       0.0.0.0         128.0.0.0       U     0      0        0 
>>>>>>> lispTun0
>>>>>>> 169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 
>>>>>>> wlan0
>>>>>>> 192.168.122.0   0.0.0.0         255.255.255.0   U     0      0        0 
>>>>>>> virbr0
>>>>>>> 
>>>>>>> 
>>>>>>> Can wifi and LISP interface live together? Do I have to modify manually 
>>>>>>> the routing table?
>>>>>>> 
>>>>>>> Thanks
>>>>>>> Daniele
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Contactus-linux mailing list
>>>>>>> [email protected]
>>>>>>> https://lispmob.org/mailman/listinfo/contactus-linux
>>>>>> 
>>>>>> 
>>>>> 
>>> 
>> 
> 

Reply via email to