ipv4 adress changed
Bug #1084234 reported by
Conrad van Onselen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Haguichi |
Fix Released
|
Wishlist
|
Stephen Brandt |
Bug Description
The 25.0.0.0 ipv4 address displayed by hamachi list does not correspond to the ipv4 one displayed in haguichi this is in 1.0.18 and logmein-
Changed in haguichi: | |
assignee: | nobody → Stephen Brandt (ztefn) |
status: | Incomplete → In Progress |
milestone: | none → 1.0.19 |
importance: | Undecided → Wishlist |
Changed in haguichi: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
As I wrote in the release notes [1], the "hamachi list" command cuts off many addresses since LogMeIn started using the new address space. Haguichi works around this issue by calling "hamachi peer" for every online member, which does output the complete addresses. This way Haguichi actually displays and uses the correct address. As a paying customer, maybe you can urge LogMeIn to fix the Linux client, to me they don't respond [2].
From one of your previous bug reports I know you have a rather large network list. Having Haguichi doing a "hamachi peer" command for every online member each update cycle (15 seconds by default, but you can change that in Preferences) might be a heavy toll on hamachi and slow it down, I'm not sure. It's certainly not a problem for Haguichi because the requests are all threaded.
The only way a member's address could change is when it's status changes, because the workaround doesn't work for offline members. Ping is an external process in the terminal, it shouldn't have any impact other than some additional network traffic.
[1] http:// www.haguichi. net/news/ release1018/ community. logmein. com/t5/ Hamachi/ Hamachi- for-Linux- cuts-off- long-addresses- in-quot- hamachi- list/td- p/87658
[2] http://