Hi, Matt, please note the following, in a fresh start (LISPmob has not been connected to the beta-network in a while), there is no need to SMR any PITR. LISPmob defines a list PITRs just to force the refresh of PITR's map cache (if needed), not to notify them our presence. In the case we have been connected to the beta-network recently and we try to reconnect again, this PITR SMRing avoids bootup delay in the case we have miss some RLOC probing from the PITRs or our locator has changed.
Lisp-beta folks, can you check the behaviour Matt explains on the PS of his original mail? Maybe it's related to the problem we saw with Daniele two days ago? Thanks! On 23 May 2013 15:30, Teto <[email protected]> wrote: > Hi, > > I understand we define a list of proxy etr/itr so that lispmob sends > SMR at startup, notifying our presence to pitr & petr. Even though I > have a decent list of pitr (I think), there are still websites I need > to wait to be able to contact them and some I am not able to ping even > after a while though I can without lisp (for instance > ftp.fr.debian.org). > > When I ping a non-lisp site, I understand the reply will go through a > pitr advertising the whole 153.X block. Then the pitr interrogates a > MR to know if there is any rloc up for this prefix. It seems MR have > different answers . For instance my rloc is up for INL1/INL2/ london/ > Andrew partan / Equinix but not for apnic/ISC or Tele danmark or cisco > San jose (US) .So if a pitr interrogates one these last MR, I won't > ever get my reply back ?! > > I believe a workaround is to smr all PITR. Is there any comprhensive > list of PITR ? > > # List of PITRs to SMR on handover > proxy-itrs = { > lip6-xtr1.ipv6.lip6.fr, > 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 > } > ~ > > Regards > > Matt > > > Nb: Is there a more generic mailing list (not lispmob specific) > dealing with problems within the beta network. For isntance when I > registered to 195.50.116.18, the rloc registered was 0.0.0.0 whereas > it works with other MS. That information might be worth for someone > else. >
