Thanks for all the answers. Following the ddt link I've come up with a
list equal to the LISPmob default one so... well the lispmob team did
a good job ^^
@Alberto > while it's true in theory, in practice, if map resolvers
answer differently, SMR seems a good way to notify your rloc
"existence". I tried to ping those map resolvers which don't see my
RLOC online thinking they could glean it but it didn't work. Then I
modified lispmob so that it sends SMRs to the list of MR defined in my
lispd.conf (including those not seeing my rloc) but they don't react
to SMR, just sending records back :(
At first I didn't see the lispmob function "lispd_get_address" so I
recreated one which in the end looks much more versatile (because it
uses getaddrinfo, so you can pass it a hostname or an IPv4/v6) and I
use it to parse addresses in the config file.
int convert_to_lisp_addr_t_extended(char *addr_str, lisp_addr_t *addr,
int disable_name_resolution , int preferred_afi ). If there is
interest I can create a patch withtout my other modifications such as
this useful (but sadly GCC specific it seems so I don't think you
would include it upstream ?)
#define LISP_LOG(level, format, ...) lispd_log_msg( (level) , \
"%s:" format ,
__func__ ,## __VA_ARGS__ )
Matt
On Thu, May 23, 2013 at 9:15 PM, Darrel Lewis (darlewis)
<[email protected]> wrote:
>
> On May 23, 2013, at 9:41 AM, Alberto Rodriguez-Natal <[email protected]>
> wrote:
>
>> I believe a workaround is to smr all PITR. Is there any comprhensive
>> list of PITR ?
>
>
> the topology map on lisp4.net should be up to date.
>
> -Darrel
