haguichi detects ip adress of peer wrong if established direct connection with it

[Guria]

$ hamachi list
 * [nameofnet]
       084-696-369 nick-1 <hamachi-Ip1>
       084-699-140 nick-2 <hamachi-Ip2>
     * 096-100-801 nick-3 <hamachi-Ip3> direct UDP <real-ip:port>
Haguichi detects 3rd peer's:
 %A - Ip as "6.97.193 di"
 %N - nick of as "nick-3 5." (5. is first part of hamachi's ip)

[Stephen Brandt (ztefn)]

That's strange, can you please e-mail me the raw "hamachi list" output in a text file?

[Guria (guria)]

I'll sent as soon as I can. But now I haven't any direct connections established

[Stephen Brandt (ztefn)]

Thanks, I've received your e-mail. From the output it appears that the nickname column for that peer is 4 characters shorter than it should be. Maybe this is caused by the Russian characters in the nickname. You could ask the peer to change the nickname using ASCII characters only and see if that resolved the problem.

If this is indeed the case, I think we can say this is a bug in Hamachi itself. I could make the list parsing in Haguichi more forgiving using complex regular expressions instead of simple string splitting, but that would have a huge influence on performance.

[Stephen Brandt (ztefn)]

I've done some experiments and the performance doesn't seem to be a big issue after all. Especially since list updates are handled in a separate thread. Also, because only being able to use ASCII characters is quite annoying for non-Latin users, I intend to implement the regular expression based parsing in the coming release to avoid the issue.