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: Tue, 31 Aug 2010 09:31:27 -0000
Reply-to: Bug 619332 <619332@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

As a matter of fact, broadcasting the I1 breaks the connection tracking
of hipfw on a forwarding node. It seems that hipfw gets the packets at
the input queue and drops it. IP forwarding still delivers the packet to
the responder. However, the R1 cannot be mapped to a correct I1 at the
forwarding node.

-- 
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.