Solved: Hamachi Install including 64-bit trick

[darmock]

Hi All

I have posted the latest addon for PIAF Version 1.2

This script will install hamachi onto your PIAF V 1.2 system and provide you with a secured VPN between multiple systems. If you have no idea what Hamachi is Google it. I have been using this for a while on my commercial installs with great success as it makes many systems in diverse geographic locations act like they are on the same local subnet.

Before the whiners start I realize Hamachi's continued support of the linux version is up in the air and I am beta testing an Open VPN version of the install-hamachi program so be patient.

The links on the scripts website will take a few days to be updated so you will have to refer to this post for the moment. This is a compiled install program so no source is available.

Please download the installation guide, read it and get the program download links from it.

The install guide is

http://www.pbxinaflash.org/ast14/docs/install-hamachi14-16.pdf

It is a combined guide for both Asterisk 1.4 and 1.6

There are 2 install programs however one for Asterisk 1.4 and one for Asterisk 1.6.

These programs will not work in PBX in a Flash 1.0 or 1.1 or any other distro.

Here is the install programs for those of you who don't need manuals

PBX in a Flash Version 1.2 running Asterisk 1.4

http://www.pbxinaflash.org/ast14/scripts/install-hamachi.x.gz

OR

PBX in a Flash Version 1.2 running Asterisk 1.6

http://www.pbxinaflash.org/ast16/scripts/install-hamachi16.x.gz




As always flames are ignored. The install manual is freshly written so I have not proofread it yet so I am sure someone else will

Best regards

Tom


Btw I am still working on the DUNDI wizard I conceived at the first OTTS session and hopefully will get it out soon. However you all needed to have a vpn installed to run it the way I envisaged.

 

[mruge]

Why wont they work with 1.1?

 

[wardmundy]

Stay tuned.

 

[dad311]

Very nice, had it running in less than five minutes. thx

 

[mruge]

Thanks Ward.

 

[darmock]

The install-hamachi program has now been posted to the website

http://www.pbxinaflash.org/piafscripts/Asterisk+1.4
http://www.pbxinaflash.org/piafscripts/Asterisk+1.6

Tom

 

[darmock]

Version 1.1 support

After much discussion with Ward I have ported the install-hamachi program back to PIAF 1.1 with the following caveats

1. This is a one time deal for this program alone.
2. I can provide no support for the 1.1 version
3. The status of the program under 1.1 is EXPERIMENTAL. I have no time to test it as extensively as I do for 1.2
4. That being said it seems to work fine under 1.1 but still requires further validation.

How do I get the program

wget http://pbxinaflash.org/scripts/install-hamachi11.x.gz

The directions for the 1.2 version will work just the same replace the name of the program in the documentation to install-hamachi11

If you try to run this program on other versions of PIAF bad things may happen!


Tom

 

[mruge]

Tom,

If there is no upgrade path to 1.2 from 1.1, how come everything that has been released or seems to be coming out is for 1.2 only?

Dont get me wrong, I am glad you decided to release this for 1.1, but what about the future?

I dont have any plans to upgrade to 1.2 as I use a hosted solution and it would be a pain to do such a upgrade.

One of the things I remember that PIAF always talks about is not having to do a full reinstall for updates.

Is you dont mind, could you or Ward please provide some insight on this?

Thank you,
Michael Ruge

 

[darmock]

The methodology by which things are done internally are quite different between 1.0 -1.1 and 1.2. In order to support 1.0-1.1 with new programs I would have to develop 3 separate versions of any product.

I am afraid that this would demand too much of my "free" time thus why I am concentrating on 1.2 only. I wish we were a fully funded corporation with unlimited resources and I was drawing some type of salary for my efforts but we are not.

The good news is that the 1.2 tree with all of our internal changes in place will support any number of new versions of PIAF. Thus, as long as the digium source allows it, what runs on the 1.2 tree (asterisk 1.4 or 1.6) should keep running and be accessible for a fairly long time. Even as we upgrade to PBX in a Flash 1.3 (when the next version of Centos comes out) the 1.2 programs will work (all depending on if all of the other software that goes into the distro still exists)

As for the future of 1.0 and 1.1 PIAF I assume there will come a time when using the update-source program will no longer work due to changes in the digium source code. But if your system works you do not need to upgrade, if a security advisory comes out then run update-source. We plan to provide access to the extra bits and pieces for 1.1 but no active development will take place on these programs.

What does this mean for PIAF 1.0 and 1.1 users.

Nothing other than if you want a new feature or program it will only be offered for 1.2 and above systems. If you want this feature then you will have to scrub 1.0 - 1.1 and install 1.2 or higher. If you really need one of the new features for the older PIAF systems talk to Ward and have a checkbook ready.

As for upgrading that is not something I want to do or provide support for. Too much is at stake if something goes wrong.

As for not having to do a full reinstall I believe this was making reference to other distros that made you download a new ISO every time something new happened to the digium source.

As it stands you DO NOT have to do a full reinstall for updates from digium, This is true. A new feature being added is not an update-- sorry.

Tom

 

[TheShniz]

It could also be argued that because these bash scripts are compiled and not open, that it's further limiting those who really want to use PiaF but are unable to because someone doesn't support that 'version' of PiaF.

Best example:
Anyone remember when A2Billing first garnered popularity and the install scripts that floated about? Everytime A2Billing released an update, those previous scripts were simply edited... that's not possible here, not even within PiaF.

For this reason, I'd highly suggest that anyone really wanting Hamachi or whatever the script of the day is... it's better to reinvent the wheel, than create a dependency.

 

[darmock]

I guess it comes down to if you don't like what we are doing then do it yourself. I agree everyone should be a linux guru with at least 200 years of experience and everybody should write all of their own stuff and never rely on anybody else. Go for it you have my vote. The door is that way >>>>>>>>>


Tom

 

[KodaK]

I agree everyone should be a linux guru with at least 200 years of experience and everybody should write all of their own stuff and never rely on anybody else.

I've been sitting here trying to follow your logic for this argument and I just can't wrap my mind around what you're trying to say here.

A major tenant of FOSS is the ability to build on the works of others. If you don't want to participate in that process, that's fine, but some of us do, and enjoy doing so. Just because it's different from what you want to do doesn't make it wrong.

Go for it you have my vote. The door is that way >>>>>>>>>

Classy.

 

[darmock]

Thanks for your fine comments as always Kodak.

See the other thread for my response to your comments.


As always I appreciate everything you write and will give it due consideration. I hope you have a fine evening


Best regards

Tom

 

[darmock]

It could also be argued that because these bash scripts are compiled and not open, that it's further limiting those who really want to use PiaF but are unable to because someone doesn't support that 'version' of PiaF.

Best example:
Anyone remember when A2Billing first garnered popularity and the install scripts that floated about? Everytime A2Billing released an update, those previous scripts were simply edited... that's not possible here, not even within PiaF.

For this reason, I'd highly suggest that anyone really wanting Hamachi or whatever the script of the day is... it's better to reinvent the wheel, than create a dependency.

Hey So I am grumpy I would change my screen name to Grumpy but someone else already has it.

The Shinz I officially apologize.

You have the right to post whatever comments you want. I understand you don't like the way things are. I have posted extensively in the 40,000 downloads thread so that might be a good place to start reading

We all have bad days and lately they have been a doozy I think I will take Joe up on his offer and go sailing for a while.

You caught me on a bad day and that is my only excuse. I resolve not to read the forums anymore when I am grumpy or pissed off.

There you saw it here first Tom aka Darmock aka The Devil officially apologized!

Please come back and participate. I am sorry. Wish I could say it wont happen again but we are all only human.


Best regards

Tom

 

[TheShniz]

You know, after reading your initial reaction (when you made it) and as a connoisseur of fine motion pictures, I felt much like Albert in Hitch who just yelled at ‘the girl’, quit my job, and stormed out of the meeting only to have some ‘doctor’ tell me to just let it marinade for a second… and I’m glad for it. Instead of quickly saying something I might regret, I took the night off with the boys and it was very nice.

I have much thicker skin than that Tom, I’ve never thought you were the devil (unless you’re in green incognito), and I never was going to let the door slam on my way out (even if I had to use a proxy to connect). No, my limited contact with you has painted for me a different picture… although granted, your compiling of scripts has only recently surfaced with PiaF, and that has changed some perceptions.

As a side note:
I’ve not touched Linux since I was in High School, that is until A@H came about… and it’s been a learning experience ever since. My feelings on VPN’s in general are that they can be a bit finicky at times, but they’re by no means rocket science either, especially when we’re talking about a built package like Hamachi. As such, my post as it was intended was to express feelings of ‘you can do it’ and need not rely on binary bash which may not be available for use tomorrow (especially if we’re trying to VPN from a PBX to a file server). I can honestly say I didn’t really expect the outburst, and it’s okay to be human.

I understand you don't like the way things are.

No, that's not true... I don't like the way your scripting is compiled. As for things in general, I've been cautiously happy. You see, you're not the only one to be burned.

P.S.
You know, there’s always Sneezy, Sleepy, Dopey, Doc, Happy, and Bashful

 

[wifinetguy]

I've just installed this on my PIAF-64 box. However, when I enter the "hampiaf" command, I get this error:

hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory

However, when I enter "ls -l libgcc_s.so.1" it shows up:

lrwxrwxrwx 1 root root 28 May 28 05:12 /lib64/libgcc_s.so.1 -> libgcc_s-4.1.2-20070626.so.1

I looked at my other PIAF (32-bit) box and the same results show up for the libgcc_s.so.1 file when doing a "ls -l". It all works fine on the 32-bit box. I've tried rebooting my 64-bit box but still get the same errors.

Here's the install log for Hamachi on my 64-bit box:

=======================================================
install-hamachi - Begin Log 20080617 702
Released on Date 053108 Version 1.0.0
=======================================================
<<>>Begin Install Hamachi

Checking to see if hamachi is installed and running
Hamachi does not appear to be running now continuing with installation
<<>> Downloading Hamachi version hamachi-0.9.9.9-20-lnx

--07:03:03-- http://files.hamachi.cc/linux/hamachi-0.9.9.9-20-lnx.tar.gz
Resolving files.hamachi.cc... 72.5.76.16
Connecting to files.hamachi.cc|72.5.76.16|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 344866 (337K) [text/plain]
Saving to: `hamachi-0.9.9.9-20-lnx.tar.gz'

0K .......... .......... .......... .......... .......... 14% 101K 3s
50K .......... .......... .......... .......... .......... 29% 314K 2s
100K .......... .......... .......... .......... .......... 44% 282K 1s
150K .......... .......... .......... .......... .......... 59% 296K 1s
200K .......... .......... .......... .......... .......... 74% 346K 0s
250K .......... .......... .......... .......... .......... 89% 299K 0s
300K .......... .......... .......... ...... 100% 283K=1.4s

07:03:05 (234 KB/s) - `hamachi-0.9.9.9-20-lnx.tar.gz' saved [344866/344866]

Hamachi hamachi-0.9.9.9-20-lnx successfully downloaded
hamachi-0.9.9.9-20-lnx/
hamachi-0.9.9.9-20-lnx/Makefile
hamachi-0.9.9.9-20-lnx/LICENSE
hamachi-0.9.9.9-20-lnx/README
hamachi-0.9.9.9-20-lnx/LICENSE.tuncfg
hamachi-0.9.9.9-20-lnx/LICENSE.openssh
hamachi-0.9.9.9-20-lnx/LICENSE.openssl
hamachi-0.9.9.9-20-lnx/hamachi
hamachi-0.9.9.9-20-lnx/tuncfg/
hamachi-0.9.9.9-20-lnx/tuncfg/Makefile
hamachi-0.9.9.9-20-lnx/tuncfg/tuncfg.c
hamachi-0.9.9.9-20-lnx/tuncfg/tuncfg
hamachi-0.9.9.9-20-lnx/CHANGES
`hamachi-0.9.9.9-20-lnx' -> `hamachi'

Copying hamachi into /usr/bin ..
Creating hamachi-init symlink ..
Compiling tuncfg ..
Copying tuncfg into /sbin ..

Hamachi is installed. See README for what to do next.
hamachi-init: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
Successfully installed!
--07:03:13-- http://www.pbxinaflash-scripts.com/ast14/files/hampiaf.tgz
Resolving www.pbxinaflash-scripts.com... 208.109.181.149
Connecting to www.pbxinaflash-scripts.com|208.109.181.149|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 394 [application/x-tar]
Saving to: `hampiaf.tgz'

0K 100% 53.7M=0s

07:03:14 (53.7 MB/s) - `hampiaf.tgz' saved [394/394]

Custom PIAF - hamachi command downloaded! Now installing
hampiaf
removed `hampiaf.tgz'
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
hamachi: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: No such file or directory
=======================================================
install-hamachi - Finished Log 20080617 702
=======================================================

 

[darmock]

thanks wifinetguy. I will look into it. There have been a bunch of updates appearing thru yum as of late


Tom

 

[wifinetguy]

OK, thanks Tom. Also, of course in my post above I meant to specify that I did a "ls -l" command instead of the "ln -l" that I posted. I'll change the post so as not to cause any confusion for anyone.

 

[jroper]

Hi Wifinetguy

On a 64bit machine run:-

yum install libgcc.i386

Then run the hamachi install script again

Joe

 

[wifinetguy]

Thanks, Joe. Worked just fine.