Amahi Wiki - User contributions [en]

OpenVPN troubleshooting

2011-04-11T19:32:43Z

Shayneb: edited change-your-port instructions

Typical problems with the VPN:

* You cannot VPN into your network from your very own network (kinda duh)
* You cannot login two users simultaneously
* You cannot login to your network from another network with the exact same settings. You can probably reach your own HDA, but not other systems in the network, due to routing (the HDA has direct connection via the VPN tunnel).
* Check that you have port forwarded 1194 udp.

== Moving to TCP ==

If UDP is not working because of a shitty ISP (see list below). Then you will have to change from udp to tcp and change your port forwarding of 1194/udp to 1194/tcp.

== Client side: (Windows) ==

Right click the red A, click edit settings.
If you have a thing saying "HomeHDA > " then mouse over it and click edit settings. Change:

proto udp

to

proto tcp

== Blocked port 1194 ==
Sometimes port 1194 is blocked if you are behind a corporate firewall or someother firewall. The trick is then to use a port that is open. If you are not running https on your amahi, using port 443 is a good choice.

You can move to port 443 by changing the line: 
port 1194 
into 
port 443 
in your /etc/openvpn/amahi.conf file.

Of course you also need to tell the client side to use port 443!
Add the following line to your client's config file

remote <hda_username>.yourhda.com 443

If for some reason the DDNS (yourhda.com) is not working but your control panel is updating, then add this line at the top of the config file.

remote YOUR_IP_HERE <port>

Note: If you have a dynamic ip, then you will probably need to update this everyday. If you have a static ip then you are fine.

== Manually (Windows) ==

Edit this file manually or use:

Seven x64

C:\Program Files (x86)\HDAConnect\config\HomeHDA.opvn

Seven x86 or 32 bit (Also most other Windows versions)

C:\Program Files\HDAConnect\config\HomeHDA.opvn

Run notepad as admin and open the above file.

== Client Side (Linux/Mac) ==

Similarly, locate the configuration file and change

proto udp

to

proto tcp

== On the Server side ==

Edit this file:

/etc/openvpn/amahi.conf

Command:

sudo gedit /etc/openvpn/amahi.conf

or

sudo nano -w /etc/openvpn/amahi.conf

change "proto udp" to "proto tcp"

Restart both sides and you are now using openvpn over tcp.
And add your isp below.

== List of bad ISPs ==

Please add your isp if you need this work-around:

* Bell Canada
* Thames Valley Communications (Groton, CT)

==Client Reports "TLS handshake failed" and Does Not Connect==
This is usually caused by packet corruption that may happen for some users. 
Follow the tutorial on "[[Prevent_SSL_Handshake_Timeouts_In_OpenVPN|Prevent SSL Handshake Timeouts In OpenVPN]]" page to fix this.

[[Category: VPN]]

OpenVPN troubleshooting

2011-04-10T04:25:46Z

Shayneb:

Typical problems with the VPN:

* You cannot VPN into your network from your very own network (kinda duh)
* You cannot login two users simultaneously
* You cannot login to your network from another network with the exact same settings. You can probably reach your own HDA, but not other systems in the network, due to routing (the HDA has direct connection via the VPN tunnel).
* Check that you have port forwarded 1194 udp.

== Moving to TCP ==

If UDP is not working because of a shitty ISP (see list below). Then you will have to change from udp to tcp and change your port forwarding of 1194/udp to 1194/tcp.

== Client side: (Windows) ==

Right click the red A, click edit settings.
If you have a thing saying "HomeHDA > " then mouse over it and click edit settings. Change:

proto udp

to

proto tcp

== Blocked port 1194 ==
Sometimes if you are behind a corporate firewall or it so happens that port 1194 is blocked. The trick is then to use a port that is open. If you are not running https on your amahi, using port 443 is a good choice.

You can move to port 443 by changing the line: 
port 1194 
into 
port 443 
in your /etc/openvpn/amahi.conf file.

Of course you also need to tell the client side to use port 443!

proto tcp

If for some reason the DDNS (yourhda.com) is not working but your control panel is updating, then add this line at the top of the config file.

remote YOUR_IP_HERE

Note: If you have a dynamic ip, then you will probably need to update this everyday. If you have a static ip then you are fine.

== Manually (Windows) ==

Edit this file manually or use:

Seven x64

C:\Program Files (x86)\HDAConnect\config\HomeHDA.opvn

Seven x86 or 32 bit (Also most other Windows versions)

C:\Program Files\HDAConnect\config\HomeHDA.opvn

Run notepad as admin and open the above file.

== Client Side (Linux/Mac) ==

Similarly, locate the configuration file and change

proto udp

to

proto tcp

== On the Server side ==

Edit this file:

/etc/openvpn/amahi.conf

Command:

sudo gedit /etc/openvpn/amahi.conf

or

sudo nano -w /etc/openvpn/amahi.conf

change "proto udp" to "proto tcp"

Restart both sides and you are now using openvpn over tcp.
And add your isp below.

== List of bad ISPs ==

Please add your isp if you need this work-around:

* Bell Canada
* Thames Valley Communications (Groton, CT)

==Client Reports "TLS handshake failed" and Does Not Connect==
This is usually caused by packet corruption that may happen for some users. 
Follow the tutorial on "[[Prevent_SSL_Handshake_Timeouts_In_OpenVPN|Prevent SSL Handshake Timeouts In OpenVPN]]" page to fix this.

[[Category: VPN]]

Contribute code

2011-04-08T05:08:05Z

Shayneb:

This is a quick guide for contrinuting code, fixes or develop native apps on Amahi.

* Join the [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list]
* If it's your first time, grab a copy of the git repo

git clone git://git.amahi.org/amahi.git

* If not, pull any changes from the master repo

cd amahi (the root of the git tree)
git pull

* Get yourself familiar with the pieces, and ask questions!
* Make some changes to the code, then test them:
* e.g. for testing the platform:

cd platform/platform/html
./script/server

and access it at http://hda:3000
you will probably want to turn off
dhcp and dns if your server is on the same
network as your home HDA
* You can see your changes with two git tools: status and diff

git status

* The status gives you a list of what files were modified, added or removed. you can see changes in your area with:

git diff --cached

* When you know you want to modify a file, you add it to the changes to be committed, for example, say a README file:

git add README

* For the parts that are added and checked in, you can see the changes with

git diff

* This is what will be committed!

* Then actually commit your changes to your git repo:

git commit

* After that you can generate a patch to be sent upstream, e.g. for a patch of the latest commit.:

1. Go into the patch folder located in the root of the git tree.
2. git format-patch HEAD^..HEAD

NOTE: When creating the patch title(first line) please put it in YYMMDD-PATCHSEQUENCE#-long-patch-name.patch format. In the long name please include what module you are working on. AKA what application etc..

* This will generate a file called 0001-my-patch.mbox or similar (type ls -l 00*), which then you can email or pastebin it to someone to be committed upstream. You probably want to [[Configure Git]] to your liking first to display the email properly.

* Please note, once the patch is applied upstream, your name and email WILL be officially in the [http://git.amahi.org amahi git repo] as as contributor, which mean it's in the open and it's crawlable, so please use your PUBLIC name/email accordingly.

* For more details, ask in the [http://forums.amahi.org forums], [https://sourceforge.net/mailarchive/forum.php?forum_name=amahi-devel amahi-devel list], or come by the [http://talk.amahi.org IRC channel]