hipl-core team mailing list archive

Thread
Date

[Bug 619332] Re: Fall-back mechanism failure

To: hipl-core@xxxxxxxxxxxxxxxxxxx
From: Christof Mroz <619332@xxxxxxxxxxxxxxxxxx>
Date: Mon, 23 Aug 2010 16:12:27 -0000
Reply-to: Bug 619332 <619332@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

René: How is point 1) going to cause problems at the I1 receiver? Of course, the I1 sender must be prepared of getting multiple replies etc. but it's running HIPL anyway.
Concerning Point 2) you're right. IMHO it should be retained as an (default-off) option for small-scale testing purposes.

-- 
Fall-back mechanism failure
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.