hipl-core team mailing list archive

Thread
Date

[Bug 619332] Re: Broadcast as fall-back mechanism when no HIT->IP

To: hipl-core@xxxxxxxxxxxxxxxxxxx
From: René Hummen <619332@xxxxxxxxxxxxxxxxxx>
Date: Wed, 25 Aug 2010 12:01:54 -0000
Reply-to: Bug 619332 <619332@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

@Christof:
(1) HIPL is just one of a few HIP implementations. Therefore, the receiver does not necessarily run HIPL.
(2) A default off option will exactly _not_ help beginners, who just install HIPL and want it to work out of the box.

@Miika:
I can't really follow why we need experimentation. hipd recognizes that it does not find a HIT->IP mapping and logs the error I mentioned above.

-- 
Broadcast as fall-back mechanism when no HIT->IP
https://bugs.launchpad.net/bugs/619332
You received this bug notification because you are a member of HIPL core
team, which is subscribed to HIPL.

Status in Host Identity Protocol for Linux: New

Bug description:
If the hip daemon can't resolve an address with hip_map_id_to_addr, it tries to broadcast an I1 message using standard interfaces.

This fallback mechanism is in my and Renes opinion useless and should be stripped out.

The cause of failing in my particular case was that I mounted /etc/hip/hosts with fuse and the fopen function failed to open it, even though hipd had root rights.