Hi Andreas, For the map-cache, there is no default (at least not in the Linux implementation). That means that packets with no cache entry are dropped. This shouldn't be a problem, as with a correctly functioning mapping system you get a reply for any query. If the consulted IP address is not an EID, you would get a covering prefix as a negative map reply. The LISPmob implementation would then install a map-cache entry using the configured PETR(s) as the RLOC.
I recommend using lig to debug LISP mapping system related problems: https://github.com/LISPmob/lig It looks like the Map-Resolver I gave you does not reply to the non-LISP queries: lig -m 217.8.98.42 8.8.8.8 Send map-request to 217.8.98.42 for 8.8.8.8 ... Send map-request to 217.8.98.42 for 8.8.8.8 ... Send map-request to 217.8.98.42 for 8.8.8.8 ... *** No map-reply received *** I tried another European one, l3-london-mr-ms, with the same results. There is one in the US that seems to work: # lig -m isc-mr-ms.rloc.lisp4.net 8.8.8.8 Send map-request to isc-mr-ms.rloc.lisp4.net for 8.8.8.8 ... Received map-reply from 149.20.48.61 with rtt 0.18400 secs Mapping entry for EID '8.8.8.8': 0.0.0.0/3, via map-reply, record ttl: 13, not auth, not mobile Negative cache entry, action: forward-native You can take a look at the beta network topology http://www.lisp4.net/images/lisp-ddt.pdf and try to find a map resolver that is both close to you, and works. Same with the proxy-etr, you can choose it at will. The only thing you can't modify, is the map server. Hope this helps, -Lori On 11/24/12 15:10, Andreas Larsen wrote: > Hi I just received my EID and I can connect and I do get map entries but I > don't get a new default installed > > proto kernel scope link src 91.198.135.17 > root@ubuntu:/home/andreas# lispconf -x cache > Socket file descriptor: 3 > Cmd Length: 36 > nlh nlmsg_len: 52 > LISP IP Mapping Cache > > 153.16.22.198/32, uptime: 00:05:38, expires: 00:04:20, via map-reply > Locator State Priority/Weight Data In/Out > 91.198.135.17 Up 1/100 0/0 > > 2610:d0:1219:192::6/128, uptime: 00:05:38, expires: 00:04:20, via map-reply > Locator State Priority/Weight Data In/Out > 91.198.135.17 Up 1/100 0/0 > > ip route > > default dev lmn0 > default via 91.198.135.1 dev eth0 metric 101 realm 7 > 91.198.135.0/27 dev eth0 proto kernel scope link src 91.198.135.17 > > Is that due to the issue with the Beta network ? If you need transit I can > offer to help from my network if that is the issue ? > > Regards Andreas
