Topic: Problem for people that could not access deckbox.org
Hello,
We have today found out about an issue that has been a problem since our server move 4 months ago.
We have sometimes received reports that some users cannot access the site anymore, and we've always thought it to be a DNS problem that goes away in time. That however was false.
The problems (which persist for some people until now) are caused by the Hamachi VPN software, which blocks IP addresses from the 5.x.x.x block, of which deckbox is a part of since our server move.
The issue is addressed officially on their forums here, workarounds are listed as well: http://community.logmein.com/t5/Hamachi td-p/83996 . If you have hamachi installed, please try those workarounds, or as a last resort, try uninstalling it.
If you know of people who can still have problems accessing deckbox from some machines, please pass them this link.
Sorry for the problems caused, let us know if the workarounds work. We're as always available for assistance here or via support@deckbox.org.
P.S. For the IT/network guys amongst you, I'm quoting below an explanation from another source:
http://superuser.com/questions/461825/c
m-osx-lion
You have a route for the 5.0.0.0/8 network there leading to the ham0 interface.
This is the hamachi interface. When Hamachi started their service, they chose the 5.0.0.0/8 network as their pool of addresses to avoid conflicting with any existing ranges. However, hamachi were never allocated this range.
In the past couple of months, RIPE (who are responsible for this range) have started selling blocks in the 5/8 network. This was inevitable with the quickly depleting numbers of ipv4 addresses, yet hamachi are still using this block.
If you want to access services in this range, then you will need to uninstall hamachi - or at least disable it while accessing those blocks. You could also manually delete the route each time.
The real fix will be for hamachi to purchase a block that they are entitled to use, or to switch to ipv6.