Hamachi and DINSA, Ministry of Defense?

[miketgw]

Im not really sure where else to post this...

I noticed in Peerblock there was a large amount of packet traffic being sent to 25.255.255.255 from my Hamachi IP (25.127.xxx.xxx)

This is mystifying to me, because 25.255.255.255 is registered with the UK Ministry of Defense.

I opened up Wireshark to see just what exactly was going on. Every 30 seconds my Dropbox LAN Sync packets were getting sent to the 25.255.255.255 address through my Hamachi IP. No idea whats going on there, and I posted on the Dropbox Bugs/Troubleshooting to see if they have any clues.

The other packets going through were NetBIOS packets. Its a little disconcerting to me that all that NetBIOS information was just sent to some random UK Ministry of Defense IP.

Why is this happening? Answers?

Should I put on my tinfoil hat and be worried about this, or this a perfectly logical explanation?

[czgeorge]

Not really an answer to your question, but your post made me check if it was Peerblock that has been keeping me from accessing anything over hamachi.... and it was.

Every ping to my 25.x.x.x network addresses is registering as DINSA as well. Going through and allowing them one by one as I attemp to ping.

I'm assuming DINSA used to own this IP block that Hamachi is now using.

[AKcomputerGuy]

I agree that this caught my attention this evening when I noticed Peerblock suddenly lighting up light a Christmas tree.  I use Peerblock, Hamachi, and Dropbox so I haven't decided what the cause for alarm is and am unsure if the British government is monitoring me because I recently watched a 20 year old BBC sitcom online from a less than scrupulous source.  I've put more time into this tonight than I care to admit, but I'm glad I at least stumbled upon this post.  I'm looking for any info that will confirm that Hamachi took over the IP block that used to be used by DINSA.

Cheers,

DB

[hawaiianon]

I've been noticing the same thing tonight. It's also seems to be using the same port as Dropbox.

Peerblock is picking up DINSA, Ministry of Defense coming form port 17500. 
Honestly, Can someone find out what's going on?

[Matchstick]

The problem appears to be that Logmein doesn't actually have it's own block opf IPv4 addresses to hand out so has effectively been squatting on addresses they don't own.

Previously there were using the 5.0.0.0-5.255.255.255 block but when when addresses started being assigned out to real network Logmein went looking for a new set of addresses, but bizarrely they appear to have decided to use 25.0.0.0-25.255.255.255 which belongs to the UK MOD.

I suspect the UK MOD aren't likely to take too kindly to this and considering they are nuclear armed, they could be pretty persuasive :)

Personally until Logmein can get access to an IPv4 netblock they actually have permission to use I'd only use Hamachi with IPv6 addresses.

[pz]

Hi,

you can find the official details here: http://b.logme.in/2012/11/07/changes-to-hamachi-on-november-19th/

[USPTO]

Wow. I just spent a week trying to figure out why my server wasn't able to ping (or do anything important) over Hamachi using IPv4. I was getting "General Failure" to ping responses. The 25.0.0.0 through 25.255.255.255 IP range is on the Bluetack level 1 blocklist.

[Sean_K]

It is also on the LogMeIn list.  I use it myself.  Get the LogMeIn list from iblocklist.com, and set it to allow within peerblock.