Did you get it to work at all so far? Now the question is if the receiver inferred a wrong IP address from the Broadcast packet (received via UDP on Port 10500 as far as I know), thus sending the R1 to nirvana. In any other case, i.e. if tcpdump shows the R1 packet on the sender, the problem's probably not associated with the fall-back. Log files would be quite helpful in any case.
-- 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. _______________________________________________ Mailing list: https://launchpad.net/~hipl-core Post to : [email protected] Unsubscribe : https://launchpad.net/~hipl-core More help : https://help.launchpad.net/ListHelp
