hipl-core team mailing list archive

[René Hummen <619332@xxxxxxxxxxxxxxxxxx>]

I would remove broadcasting for 3 reasons:

1) Broadcasting I1s is not specified and thus only supported by HIPL. As
such there's no interoperability with other implementations, which could
lead to situations where HIPL <-> HIPL just works, whereas combinations
don't. This can also be confusing for beginners in a heterogenous
scenario.

2) Broadcasts are not routed beyond local network boundaries. Hence, it
only provide a failover mechanism for very simple network topologies.

3) Instead of trying to broadcast, we should give an explanation why the
connection could not be established. A reference to a FAQ (that we would
need in such a case) would be a nice starting point for beginners to
track down their problem. I.e. "No HIT to IP mapping found for the
requested connection. Please refer to FAQ #12345 for further
information."

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