Amahi Wiki - User contributions [en]

VPNAndroid

2012-07-20T20:23:01Z

Smystaki: /* VPN Client - Android - HTC Android G1/Dream */

= VPN Client - Android - HTC Android G1/Dream =

'''NOTE:''' [https://play.google.com/store/apps/details?id=de.blinkt.openvpn&hl=en OpenVPN for Android] works with the certificates below for ICS 4.0 or greater without rooting your device. There is no additional configuration required to the HDA or your device (Tested on HTC One X and Samsung Tab 2 also on HTC One V).

This guide is written for a HTC Android G1/Dream phone rooted with Cyanongenmod 5.

[update March 24, 2011: Tested and works with Cyanogenmod 7.0, thus any CM7 compatible phone]

[update August 8, 2011: Tested and works with Cyanogenmod 7.1, thus any CM 7.1 compatible phone]

[update September 9, 2011: Tested and works with MIUI 1.9.2 on a HTC Droid Incredible 2, should work on any MIUI ROM]

In your Linux-based OS computer..

* Download the files here and save them in your /home/username/openvpn folder (where ''username'' is your main users name)(to download, right click > save as):
** [http://dl.amahi.org/vpn/AmahiHDAClient.crt AmahiHDAClient.crt]
** [http://dl.amahi.org/vpn/AmahiHDAClient.key AmahiHDAClient.key]
** [http://dl.amahi.org/vpn/ca-cert.crt ca-cert.crt]

Then, from the terminal run

{{Code|cd /home/username/openvpn
openssl pkcs12 -export -in AmahiHDAClient.crt -inkey AmahiHDAClient.key -certfile ca-cert.crt -name Amahi -out certs.p12}}

You will be asked for a export password for the certs.p12 file - enter amahi twice.

To automate this process, paste the code from [http://wiki.amahi.org/images/f/f9/Automate.script automate.script] in your favorite editor. Save it & run it with {{Code|sh <filename>}}

You should now have a certs.p12 file in your /home/username/openvpn folder, copy this certs.p12 file to the root of your sdcard on the Android phone.

Now on the Android phone..

<pre><nowiki>
Menu -> Settings -> Location & Security -> Install from SD card
</nowiki></pre>

This will show you certs.p12, select this and enter the password amahi, after it has extracted the certificates, you will be asked to name the certificate, enter Amahi.

Now on the Android phone

<pre><nowiki>
Menu -> Settings -> Wireless & networks -> VPN settings -> Add VPN -> Add OpenVPN VPN
</nowiki></pre>

VPN name = Amahi

Set VPN server = yourHDAnickname.yourhda.com

User authentication = Yes

Set CA certificate - Amahi

Set user certificate - Amahi

Menu -> Advanced -> LZO compression = Yes

Back

Menu -> Save

You should now see an Amahi entry, click on this to connect. It may ask you for the certificate access password. Then it may ask for your username and password that you use to loginon your HDA. You should see that you are connected, enjoy your VPN connection to your HDA server.

= VPN Client - Android 2.2 - DROID X (Verizon Wireless) =
Contact me in the forums if you need help setting this up. If you have a later version of Android such as Gingerbread (Android 2.3) then you can't use this tutorial for setting up openvpn. You can however use the openvpn configurations if your phone is already set up with openvpn.

[[User:Sag47|Sag47]] 00:51, 5 April 2011 (PDT)

This tutorial is not for the feeble minded. I tried writing it as best as I could to keep it a "How to VPN" article and not a "How to root my droid" topic.

The default Droid X from Verizon does not come with openvpn installed. It's a little annoying and you have to be a little tech savvy to get it working. I am outlining instructions here for how I connected my Droid X to my Amahi HDA.

Some prerequisites:
* Your phone must be rooted.
* I am running Android 2.2 so these instructions may become outdated. I also recommend you be running Android 2.2 Froyo on your Droid X
* You should have adb installed (or running a more advanced bash terminal on Android like Better Terminal Emulator Pro app)
* Install the following apps
** OpenVPN Installer
** OpenVPN Settings

Create a directory on your SDCARD called openvpn or if in the terminal /sdcard/openvpn.

Follow the general [[VPNLinux]] instructions but place all of the configurations and certificates in the openvpn folder on your sdcard.

Install openvpn using the "OpenVPN Installer" app and select /system/bin each time the app asks for a location to place a binary.

You can run one of the following commands to grab the mount point of your system folder. (Run commands through adb or in a terminal on your Droid)
<pre><nowiki>
df | grep system
cat /proc/mounts | grep system
cat /proc/mounts
</nowiki></pre>

My device is mounted on /dev/block/mmcblk1p21 so that is the device I am using in this tutorial. Download tun_alt.ko as recommended in [http://forum.xda-developers.com/showpost.php?p=11109394&postcount=25 this post]. Copy it to the root of your sdcard.

Now we install the kernel module. Run the following command sequence (through adb or a terminal on your Droid).
<pre><nowiki>
su
mount -o rw,remount /dev/block/mmcblk1p21 /system
mv /sdcard/tun_alt.ko /system/lib/modules/tun.ko
cd /system/lib/modules
chown root\: tun.ko
chmod 644 tun.ko

#now lets test it
insmod /system/lib/modules/tun.ko
</nowiki></pre>
If you don't see any output and the "OpenVPN Installer" app successfully installed openvpn then you should be set up.

Double check your configuration in /sdcard/openvpn. Once you know everything is good then run the "OpenVPN Settings" app. It should automatically detect your configuration.

Enable OpenVPN. Select your config to turn on the tunnel. Then you should see a prompt in your notification status prompting for a password. My Droid X connected to the network after that.

There's one final step. If you remember you manually ran the insmod /system/lib/modules/tun.ko command but when you reboot your phone the module will no longer be loaded.

Go into the settings for the "OpenVPN Settings" app and modify the TUN module settings.
* Set "Load module using" to insmod.
* Set "Path to tun module" to /system/lib/modules/tun.ko

Reboot your phone and test the configurations. It should be a one click process within the "OpenVPN Settings" app.

[[Category: VPN]]

DLNA

2012-03-26T21:17:52Z

Smystaki:

Working page for [http://www.amahi.org/apps/dlna Amahi DLNA], the Amahi port of [http://sourceforge.net/projects/minidlna/ MiniDLNA]. It makes your Amahi HDA the best media server for all your clients.

Note that Amahi has other media server apps available as well:
* [http://www.amahi.org/apps/mediatomb MediaTomb], which has transcoding on the fly for more compatibility
* [http://www.amahi.org/apps/ps3mediaserver PS3 Media Server] works well with the xbox360
* [http://www.amahi.org/apps/ushare UShare] works well with the xbox360

There is no list of '''Amahi Certified DLNA Players''' because most (99.999%) of clients will work. The client has to support the format of the file that the server is streaming. Not all clients support all the formats. Typically [http://www.divx.com/ DivX] format are widely supported, but newer formats like [http://www.matroska.org/ Matroska] may not be supported by some clients.

However, below is a very incomplete list of client devices. Feel free to add your client and what features it supports.

= Tips =

* You can configure its options in a text file in:

/var/hda/apps/dlna/amahi.conf

* It has some Tivo support
* It picks up new files added automatically (as opposed to uShare)
* Check the log file for the app at: /tmp/minidlna/minidlna.log


= Troubleshooting =

* If you have problems where DLNA cannot see some files, it may be due to some permissions issues. You can do this (change the path and USERNAME accordingly):
cd /var/hda/files/movies && chown -R USERNAME:users *
* If you installed too early, uninstall DLNA, uninstall RPM Fusion (Non-free) and RPM Fusion, in that order, refreshing each time the available apps page in your HDA.

* If you suddenly realize that ONLY a part of your library is delivered by your amahi-dlna server to your clients you (most probably) have add a file to the library that forces dlna daemon parser to crash. Check [http://forums.amahi.org/viewtopic.php?f=19&t=3816 this] out if this is the case.

= WD TV Live =

At the moment, with a [http://www.westerndigital.com/en/products/Products.asp?DriveID=735 WD TV Live] player, we can stream from .avi files to full 1080p content from this server.

With Matroska files it also supports subtitles in various languages and multiple audio tracks.

= PS3 =

Notes on working state with [http://www.playstation.com/ PS3].

Playing avi and mkv files (mostly with h.264 content) worked great! Video seems to be working nicely!

Playing of mp3-files has been no problem - worked fine.

= Xbox 360 =

Notes on working state with [http://www.xbox.com Xbox 360]:

* Install Amahi-dlna
* Turn on Xbox 360 and Navigate to My Xbox
* Scroll to the right until you see Music Library
* Hit "A" on your controller.
* Amahi should be one of your choices if amahi-dlna was installed correctly.

Repeat for Picture Library.

= O!Play Air =

Notes on working state with [http://www.asus.com/Search.aspx?SearchKey=o!play O!Play Air]

= Samsung TV with Media@ capability =

The TV will play all media (pictures, music, movies) over WLAN/LAN, in TVs like the [http://www.samsung.com/uk/consumer/learningresources/tv/mediasolution/introduction.html Samsung with Media@ features], no problem.

= Windows Media Center =

Windows 7 (Ultimate pre-release) Media Center will display pictures and play music. Video doesn't work.

= Windows Media Player 11 =

On Windows 7 the Windows Media Player 11 shows successfully the Amahi-Server. On Windows XP this doesn't work.

= VLC Media Player =

VLC Media Player will connect to DLNA on Mac & Linux.

On Linux you will need the [http://www.cybergarage.org/cgi-bin/twiki/view/Main/CyberLinkForJava CyberLink UPnP] plugin. If you manage to install it, please report back here!

On Mac you can click on File > Service discovery > Universal Plug'n'Play discovery.

= 4u2stream =

The client which is available at http://4u2stream.4u2sites.com works under windows xp.

= Moxi =

Music, video, and pictures all work perfectly on [http://moxi.com Moxi]. Go to Media Link on the Moxi menu, and Amahi shows up in the list of media servers, complete with a Penguin for the logo.

= TerraTec NOXON iRadio =

Working, no changes are needed, by default a server called Amahi appears in the list of the home menu.

= FAQs =

* Q: Does it support Matroska (.mkv) files?: Yes!
* Q: Can it stream .iso files?: Nope
* Q: Can it stream full DVDs: Nope, only the VOB files
* Q: Does it have support for album art and covers?: Yes!
* Q: Does it have support for subtitles?: Yes!
* Q: Does it transcode on the fly while streaming?: Nope
* Q: I added additional share locations into the config file but they do not appear!: try removing files.db under /tmp/minidlna/ and restarting the amahi-dlna service

=Playlists=

TBD

= App's screenshot and logo =

[[Image:dlna-sshot.jpg]]

[[Image:dlna-logo.jpg]]

[[Category:Apps]]

Browse and Netboot ISO images

2011-02-24T00:27:19Z

Smystaki:

== Overview ==

If you use Amahi to regularly download ISO images of operating systems and such like, this page is for you. It describes some tweaks that can be made to an Amahi setup to enable easy browsing and netbooting of ISO images, *without* having to mount each one and copy files. This is particularly handy, if you just want to try out the latest and greatest version of something.

Almost every command in this article needs to be executed with root privileges. Therefore, use "su" to become root before you begin, or prefix each command with sudo if you prefer.

== Part 1 - Making ISO images browsable ==

First, we're going to use the automounter together with /dev/loop to mount the ISO files on demand. Before we can go any further, ensure that you have the automounter installed:

{{Code|
Code=yum -y install autofs
}}

Next, create a suitable mount point. In this example, we're using /media/iso-fs
{{Code|
Code=mkdir -p /media/iso-fs
}}

Now create a file called /media/.iso-fs.map using your favourite editor with the following contents:
{{Text|
Text=#!/bin/bash
DIR_LIST=(/var/hda/files/torrents /home/*/Downloads)
iso=`find ${DIR_LIST[@]} -name $1.iso -type f`
echo "-fstype=iso9660 :$iso"
}}
This script will act as an executable mount map for the automounter, returning suitable mount point parameters if it finds an ISO file that matches the key passed to it.

...and ensure that this file is executable:
{{Code|
Code=chmod u+x /media/.iso-fs.map
}}

The final step is to create an entry in the master automount map. Edit /etc/auto.master and add the following line somewhere after the default /net entry:

{{Text|
Text=/media/iso-fs /media/.iso-fs.map ro,loop --timeout=5
}}

The last parameter is the time in seconds after which a mount point will be automatically unmounted. Now restart the automounter with:

{{Code|
Code=service autofs restart
}}

If all has gone well, then you should be able to browse any ISO image that you have in your torrents or downloads directories. In my case, I have ubuntu-10.10-desktop-i386.iso in my torrents directory, so I get:
{{Code|
Code=bash$ ls /media/iso-fs/ubuntu-10.10-desktop-i386/
autorun.inf dists md5sum.txt preseed usb-creator.exe
boot install pics README.diskdefines wubi.exe
casper isolinux pool ubuntu
}}

You can browse around the directories, copy files etc at leisure, and when you're done the automounter will release the loop device for reuse.

== Part 2 - Making ISO images bootable ==
First, we need to create some directories to hold the PXE menu structure and the script to generate it:
{{Code|
Code=cd /usr/share/amahi-netboot/tftp
mkdir iso-boot
mkdir iso-boot/conf
mkdir iso-boot/mnt
}}

Next you will need to download [[File:menu-gen.sh]] to generate the PXE boot menus. Save this script as iso-boot/menu-gen.sh and make it executable:

{{Code|
Code=chmod u+x iso-boot/menu-gen.sh
}}

menu-gen.sh contains a number of configuration variables at the top; you will need to edit HDA_IP to match the IP address of your HDA at the very least. The TIMEOUT variable also needs to match the automount timeout set in part one so that your machine doesn't run out of loop devices.

Now run the script to generate the menus based on the ISOs on your system and the distributions the script knows about:
{{Code|
Code=iso-boot/menu-gen.sh
}}
Note that the script will appear to run slowly as it waits for each ISO to time out before moving on to the next one.

The last stage in setting up the menus, we need to add an entry in pxelinux.cfg/default to link to the generated menus. Open pxelinux.cfg/default in your favourite editor and add:
{{Text|Text=
LABEL linux-boot
MENU LABEL Boot from ISO images
kernel menu.c32
append iso-boot/conf/boot.conf
}}

With the menus created, we just have two final steps to take. First, the kernel and initrd need to be available under the tftp directory structure. Fortunately, the automounter can take care of this for us; simply add the following additional to /etc/auto.master:

{{Text|
Text=/usr/share/amahi-netboot/tftp/iso-boot/mnt /media/.iso-fs.map ro,loop --timeout=5
}}
...and then restart the automounter:
{{Code|
Code=service autofs restart
}}

Secondly, we need to enable NFS and export the relevant directories. Assuming you have NFS installed and running, edit /etc/exports to add:
{{Text|
Text=/media 192.168.147.0/24(ro,crossmnt)
}}
And then issue service nfs restart to load the new export table.

== Known Issues ==
#The menu-gen.sh script doesn't currently work for some images, notably those based on the dracut system
#menu-gen.sh is a first attempt; it currently needs to be taught about new distributions and where to find the kernel and initrd image on each type of ISO. Suggestions and improvements to make it smarter greatly appreciated.
#Occasionally, if you don't shutdown the PXE booted system cleanly, the automounter is unable to release the mount point

Webapp aliases

2011-02-19T21:03:04Z

Smystaki:

{{WorkInProgress}}

To Do

Enable Outgoing Emails

2011-02-19T10:59:45Z

Smystaki:

Here's how to enable outgoing emails on your Amahi server.

Note: Make sure to use copy-paste to execute those commands. In particular, they contain back-ticks as the starting string delimiter, which can be hard to find on a keyboard!

[[Open Terminal as root|As '''root''' user]]:

{{code|Code=
SMTP_SERVER=your_isp_smtp_server
yum -y install sendmail-cf m4
cd /etc/mail
sed -ie "s/.*SMART_HOST.*/define(\`SMART_HOST', \`$SMTP_SERVER')dnl/" sendmail.mc
make
service sendmail restart}}

Make sure to replace ''your_isp_smtp_server'' on the first line with the hostname or IP address of your ISP SMTP server.

If you need to connect to the SMTP server using port 587 (TLS/STARTTLS), you'll need to do this too:
{{code|Code=
cd /etc/mail
sed -ie "s/$.*SMART_HOST.*$/\1\ndefine(\`RELAY_MAILER_ARGS', \`TCP \$h 587')dnl\ndefine(\`ESMTP_MAILER_ARGS', \`TCP \$h 587')dnl/" sendmail.mc
make
service sendmail restart
}}
If you want to use another port than 587, change that number in the above command (it's there twice), before executing it. If you already executed it, edit the sendmail.mc file, and search for 587 - it should appear there twice - change both.

If you need to provide a username and password to use the SMTP server, you'll need to do this too:

{{code|{{:Enable Outgoing Emails/somecode3}}}}
{{code|Code=
SMTP_SERVER=your_isp_smtp_server
USERNAME=your_smtp_username
PASSWORD=your_smtp_password
cd /etc/mail
chmod 600 access
echo "AuthInfo:$SMTP_SERVER \"U:$USERNAME\" \"P:$PASSWORD\" \"M:PLAIN\"" >> access
makemap -r hash access.db < access
sed -ie "s/.*confAUTH_MECHANISMS.*/define(\`confAUTH_MECHANISMS', \`EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl\nFEATURE(\`authinfo',\`hash \/etc\/mail\/access')dnl/" sendmail.mc
make
service sendmail restart
}}

Enable Outgoing Emails

2011-02-19T10:56:39Z

Smystaki:

Here's how to enable outgoing emails on your Amahi server.

Note: Make sure to use copy-paste to execute those commands. In particular, they contain back-ticks as the starting string delimiter, which can be hard to find on a keyboard!

[[Open Terminal as root|As '''root''' user]]:

{{code|Code=
SMTP_SERVER=your_isp_smtp_server
yum -y install sendmail-cf m4
cd /etc/mail
sed -ie "s/.*SMART_HOST.*/define(\`SMART_HOST', \`$SMTP_SERVER')dnl/" sendmail.mc
make
service sendmail restart}}

Make sure to replace ''your_isp_smtp_server'' on the first line with the hostname or IP address of your ISP SMTP server.

If you need to connect to the SMTP server using port 587 (TLS/STARTTLS), you'll need to do this too:


{{code|{{:Enable_Outgoing_Emails/somecode2}}}}

If you want to use another port than 587, change that number in the above command (it's there twice), before executing it. If you already executed it, edit the sendmail.mc file, and search for 587 - it should appear there twice - change both.

If you need to provide a username and password to use the SMTP server, you'll need to do this too:

{{code|{{:Enable Outgoing Emails/somecode3}}}}

Enable Outgoing Emails

2011-02-19T10:55:56Z

Smystaki:

Here's how to enable outgoing emails on your Amahi server.

Note: Make sure to use copy-paste to execute those commands. In particular, they contain back-ticks as the starting string delimiter, which can be hard to find on a keyboard!

[[Open Terminal as root|As '''root''' user]]:

{{code|{{:Enable_Outgoing_Emails/somecode}}}}
{{code|Code=
SMTP_SERVER=your_isp_smtp_server
yum -y install sendmail-cf m4
cd /etc/mail
sed -ie "s/.*SMART_HOST.*/define(\`SMART_HOST', \`$SMTP_SERVER')dnl/" sendmail.mc
make
service sendmail restart}}

Make sure to replace ''your_isp_smtp_server'' on the first line with the hostname or IP address of your ISP SMTP server.

If you need to connect to the SMTP server using port 587 (TLS/STARTTLS), you'll need to do this too:


{{code|{{:Enable_Outgoing_Emails/somecode2}}}}

If you want to use another port than 587, change that number in the above command (it's there twice), before executing it. If you already executed it, edit the sendmail.mc file, and search for 587 - it should appear there twice - change both.

If you need to provide a username and password to use the SMTP server, you'll need to do this too:

{{code|{{:Enable Outgoing Emails/somecode3}}}}

Map Shares in Windows

2011-02-16T13:41:01Z

Smystaki:

{{WorkInProgress}}







== Adding shares in Windows XP / Vista / Windows 7 : Map Network Drive ==

This article will explain how to simplify access to your Amahi network shares within Windows XP / Vista / Windows 7 by mapping the network shares as "drives" that can be seen from "(My)Computer" in Windows Explorer.

<strong>In Windows XP</strong><br /><br />
1. Go to "My Computer"<br />
2. Click "Tools" > "Map Network Drive"<br />
3. choose an un-used drive letter<br />

Note: It's a good idea to perhaps start with the end of the alphabet so as to not collide with drive letters when you plug in multiple external drives to your PC, which take up drive letters as well.

4. a. Click "Browse" and navigate to a share folder within your HDA. Select the folder to become a drive letter. <strong>OR..</strong><br />
4. b. in the address field, provide the location of the folder. For example: in my case, the location of my "Documents" shared folder is "\\hda\Docs". <br /><br />
Note: In Some cases the server's address may need to be more specific and include the domain you assigned. For example, my server's domain is "srvr.com", so a more specific address would be "\\hda.srvr.com\Docs".
Windows will not find/add the network location if it is not specific enough or properly addressed and that is how you will know how specific you must be when addressing the share.

<strong>In Windows Vista / Windows 7</strong><br /><br />
1. Click the "Logo/Start Menu" > "Computer"<br />
2. Click "Tools" > "Map Network Drive"<br />
(If you don't have the menu bar atop the window, you may need to add it manually: From the start menu, type "Folder Options", hit Enter; In the Folder Options windows, click the "View" tab; under "Advanced Settings" check the "Always show menus" option.)<br />
3. Proceed with steps 3 and 4 above, as with Windows XP.<br />

And that is all! Once you are done, the shares should show up as drive letters under (My)Computer and can be more fully accessed within Windows Explorer.
<br />

[Screenshots coming soon.]

Map Shares in Windows

2011-02-16T13:39:53Z

Smystaki:

== Adding shares in Windows XP / Vista / Windows 7 : Map Network Drive ==

This article will explain how to simplify access to your Amahi network shares within Windows XP / Vista / Windows 7 by mapping the network shares as "drives" that can be seen from "(My)Computer" in Windows Explorer.

<strong>In Windows XP</strong><br /><br />
1. Go to "My Computer"<br />
2. Click "Tools" > "Map Network Drive"<br />
3. choose an un-used drive letter<br />

Note: It's a good idea to perhaps start with the end of the alphabet so as to not collide with drive letters when you plug in multiple external drives to your PC, which take up drive letters as well.

4. a. Click "Browse" and navigate to a share folder within your HDA. Select the folder to become a drive letter. <strong>OR..</strong><br />
4. b. in the address field, provide the location of the folder. For example: in my case, the location of my "Documents" shared folder is "\\hda\Docs". <br /><br />
Note: In Some cases the server's address may need to be more specific and include the domain you assigned. For example, my server's domain is "srvr.com", so a more specific address would be "\\hda.srvr.com\Docs".
Windows will not find/add the network location if it is not specific enough or properly addressed and that is how you will know how specific you must be when addressing the share.

<strong>In Windows Vista / Windows 7</strong><br /><br />
1. Click the "Logo/Start Menu" > "Computer"<br />
2. Click "Tools" > "Map Network Drive"<br />
(If you don't have the menu bar atop the window, you may need to add it manually: From the start menu, type "Folder Options", hit Enter; In the Folder Options windows, click the "View" tab; under "Advanced Settings" check the "Always show menus" option.)<br />
3. Proceed with steps 3 and 4 above, as with Windows XP.<br />

And that is all! Once you are done, the shares should show up as drive letters under (My)Computer and can be more fully accessed within Windows Explorer.
<br />

[Screenshots coming soon.]

Map Shares in Windows

2011-02-16T13:36:37Z

Smystaki:

== Adding shares in Windows XP / Vista / Windows 7 : Map Network Drive ==

This article will explain how to simplify access to your Amahi network shares within Windows XP / Vista / Windows 7 by mapping the network shares as "drives" that can be seen from "(My)Computer" in Windows Explorer.

<strong>In Windows XP</strong><br /><br />
1. Go to "My Computer"<br />
2. Click "Tools" > "Map Network Drive"<br />
3. choose an un-used drive letter<br />

Note: It's a good idea to perhaps start with the end of the alphabet so as to not collide with drive letters when you plug in multiple external drives to your PC, which take up drive letters as well.

4. a. Click "Browse" and navigate to a share folder within your HDA. Select the folder to become a drive letter. <strong>OR..</strong><br />
4. b. in the address field, provide the location of the folder. For example: in my case, the location of my "Documents" shared folder is "\\hda\Docs". <br /><br />
Note: In Some cases the server's address may need to be more specific and include the domain you assigned. For example, my server's domain is "srvr.com", so a more specific address would be "\\hda.srvr.com\Docs".
Windows will not find/add the network location if it is not specific enough or properly addressed and that is how you will know how specific you must be when addressing the share.

<strong>In Windows Vista / Windows 7</strong><br /><br />
1. Click the "Logo/Start Menu" > "Computer"<br />
2. Click "Tools" > "Map Network Drive"<br />
(If you don't have the menu bar atop the window, you may need to add it manually: From the start menu, type "Folder Options", hit Enter; In the Folder Options windows, click the "View" tab; under "Advanced Settings" check the "Always show menus" option.)<br />
3. Proceed with steps 3 and 4 above, as with Windows XP.<br />

And that is all! Once you are done, the shares should show up as drive letters under (My)Computer and can be more fully accessed within Windows Explorer.
<br />

[Screenshots coming soon.]





[[Category:Platform]]




<noinclude>
[[Category:WikiModTools]]
</noinclude>

OpenVPN on iOS

2011-02-16T09:53:53Z

Smystaki:

From the original [http://forums.amahi.org/viewtopic.php?f=3&t=1508&start=0 iPhone VPN] thread in the forums:

For all of you out there that have an iPhone or any other mobile "idevice" And want VPN access I have found a way. The catch is, you have to have a jail broken device. If you do have a jail broken device and want the openvpn app on the phone you will want to check out www.guizmovpn.com it's about 4€. The evaluation period is a full week. But the price is worth it.

To configure the client you will need to follow the guide on www.guizmovpn.com The client info you will need to get from the wiki here http://wiki.amahi.org/index.php/VPNLinux

I have also created a full guide custom tailored to amahi vpn access.
It might seem like a little to much or a hassle but its really simple. It just takes the time to read. http://home.mchsi.com/~irish-link/GuizmOVPN.pdf

If you go to set it up and have issues please head over to the forum (liked at the top) and let me know if you need help. If you do end up setting it up, let me know how it works for you.
[[Category: VPN]]

OpenVPN clients

2011-02-16T09:53:16Z

Smystaki:

To connect to your network from the outside, you will need a VPN client installed on the computer from which you want to connect to your network.

We have clients For Windows, Mac and Linux:

* [[VPNWindows|Windows Client]]: customized for Amahi to be ultra-easy to use
* Mac clients: [[VPNMacTunnelBlick|TunnelBlick]] (open source) or [[VPNMacViscosity|Viscosity]] (pay client, very nice)
* [[VPNLinux|Linux]]: (in general) and [[VPN Ubuntu|Ubuntu via GUI]]
* [[VPNAndroid|Android]]: VPN access on the Android phones
* [[VPN Iphone|iPhone]]: VPN access on the iPhone/iPod/iPad

'''NOTE: ''' you cannot really connect to your network and test your VPN from *inside* your network

Also, the network from which you connect to your network '''cannot''' be identical because the VPN cannot route packets in that situation. E.g. if your network at home is 192.168.1.* and the network from which you are connecting is also configured at 192.168.1.*, it will not work.

[[Category: VPN]]

VPN Ubuntu

2011-02-16T09:52:23Z

Smystaki:

=Setting up the OpenVPN client Under Ubuntu 10.04 =

Installing on 10.04 is similar as below, however, there is a known issue in 10.04 where you put in the settings and after closing the dialogs, the edit dialog has all the certificate filenames replaced with directories from a folder and the custom port checkbox is now unchecked.

The suggestion for 10.04 is to try moving those files into a different folder. (e.g. to the Downloads folder). Another folder name, such as "VPN," should probably work fine. If that still doesn't work, try removing the connection and re-do the whole sequence, except point the dialog to the ones in that new folder.

=Setting up the OpenVPN client Under Ubuntu 9.10=

Not everyone feels comfortable working from the Linux CLI ('''C'''ommand '''L'''ine '''I'''nterface), and so the alternate set-up instructions for connecting to Amahi's OpenVPN service might seem a bit intimidating to some. Here is a step-by-step tutorial explaining how to get VPN ('''V'''irtual '''P'''rivate '''N'''etworking) running under a GUI ('''G'''raphical '''U'''ser '''I'''nterface) in Ubuntu 9.10, a distribution of Linux.

==Step #1: Install the OpenVPN Application==

Although you don't have to understand much about OpenVPN, the FOSS ('''F'''ree '''O'''pen '''S'''ource '''S'''oftware) program Amahi uses for secure connections from outside your Amahi HDA ('''H'''ome '''D'''igital '''A'''ssistant, the Amahi server you've set up), you ''do'' have to have the OpenVPN software installed on your Linux machine. In the case of Ubuntu 9.10 (and 9.04), this isn't installed by default, but, like most Linux '''distros''' (short for ''distributions,'' the “flavor” of Linux you've chosen), this is relatively straightforward and easy.

Pull down the '''Applications''' menu and choose '''Ubuntu Software Center'''. (This used to be called “Add/Remove” in previous versions of Ubuntu.)

[[File:Vpn-01.png|center|The location of the Ubuntu Software Center menu option]]

The Software Center dialog box appears, with the cursor blinking in the text input box.

[[File:Vpn-02.png|center|The Ubuntu Software Center]]

Type in the letters “'''VPN'''” (without the quotes, case doesn't matter). That quickly narrows down the options to programs related to VPN. Your sifted options will look something like this:

[[File:Vpn-03.png|center|Narrowing down the field to just VPN software]]

The program we're after is “'''VPN Connection Manager (OpenVPN)'''.” Highlight that by clicking on it, and note the arrow on the right-hand side of the highlighted line.

[[File:Vpn-04.png|center|Selecting the OpenVPN application from the list.]]

Click on the arrow. What appears is a brief description of the program and the option to install it:

[[File:Vpn-05.png|center|A description of the OpenVPN software to be installed, as well as the Install button.]]

Click the “Install” button. Does the installation happen right away? No, not until you authorize it; this is Linux, not a virus-prone operating system:

[[File:Vpn-06.png|center|Granting authorization for the install process...]]

Give it your user/administrator password and the installation will proceed:

[[File:Vpn-07.png|center|The install process]]

Most times, Ubuntu 9.10 will show a progress bar (with percentages) over on the right, but this time it didn't. Apparently, “your mileage may vary.” At least you know that when the “In Progress” message disappears that your OpenVPN software is installed. Close out of the Software Center and proceed to Step #2.

==Step #2: Actually Setting Up the VPN Connection==

Before we proceed, take note of several things:

[[File:Vpn-07b.png|right|How to right-click and "Save Link As..."|250px]]

#You must download the following three files, right-clicking on each file name, then left-clicking on '''Save File As...''' from the pop-up menu. Save each file in your '''/home/[username]''' folder (where "[username]" is your main log-in username):<br/>
## [http://dl.amahi.org/vpn/AmahiHDAClient.crt AmahiHDAClient.crt]
## [http://dl.amahi.org/vpn/AmahiHDAClient.key AmahiHDAClient.key]
## [http://dl.amahi.org/vpn/ca-cert.crt ca-cert.crt]
# The actual VPN connection must be made from OUTSIDE your home network. You can't test your VPN setup (which presumes, like “E.T.,” that you're trying to “home phone” from somewhere else) if you're still INSIDE your home network. In my case, I explained to my patient neighbors what I needed to do and got permission from them to connect to their Wi-Fi router. (It helped the situation that I've helped fix and de-louse their computer on numerous occaisions.) Thus I could test this while at home, but still be “away” as far as the network was concerned.

All right. You have the files on your hard drive, and you and your laptop are somewhere else (perhaps quaffing a latte at Starbucks or increasing your cholesterol at McDonalds) and you're ready to set up your VPN connection. Here are the steps:

Left-click the wireless connection display up near the date and time in the upper right-hand corner of the screen. When you left-click, you should see the nearby wireless routers and an option you didn't notice before:

[[File:Vpn-08.png|center|Locating the VPN Configuration option on the wireless-connection menu]]

From the “'''VPN Connections'''” option, open the sub-menu and choose “'''Configure VPN...'''” That brings you to a tabbed dialog box with the VPN tab already chosen. Click on the “'''Add'''” button.

[[File:Vpn-09.png|center|The Network Connections dialog box, with the VPN tab "on top."]]

Now you'll choose a '''VPN Connection''' type. If the only VPN software installed on your system is Open VPN, this is the only option you have. Click on the “'''Create'''” button:

[[File:Vpn-10.png|center|Choosing a VPN connection type]]

We'll be working with the following dialog box in the next few screenshots. When first presented it looks like this:

[[File:Vpn-11.png|center|The VPN Connection profile dialog as it first appears]]

Give your VPN a '''Connection Name'''. Being Mr. Unoriginality, I chose “hda,” but if you're the creative type, knock yourself out. Now let's change the Authentication Type. We'll choose “'''Password with Certificates (TLS)''',” as shown below:

[[File:Vpn-12.png|center|Choosing an Authentication Type]]

Your Amahi name forms the first part of your Gateway name: '''[Amahiname].yourhda.com'''.

Now provide your hda username and user password. If there's more than one computer user at home, there are probably more than one of these. (This is NOT your overall Amahi.org account name and password.)

I've used HariSeldon in this example and, by checking “Display Passwords” below, I've demonstrated that you don't have to “type in dark” when it comes to your password.

[[File:Vpn-13.png|center|Adding the Gateway, Username, and Password]]

Now we're going to make use of those .KEY and .CRT files you downloaded earlier. Using the example below (and assuming you know how to use the “file” button on each line to navigate to the location of the file needed), you fill in “User Certificate” and “CA Certificate” and “Private Key” as shown below:

[[File:Vpn-14.png|center|Adding the Gateway, Username, and Password]]

Now we need to change one more setting by clicking on the “'''Advanced'''” button, which will bring up the following dialog box. Check (or “tick” as my English friends say) the box which says “'''Use LZO data compression.'''” (No, I don't have a clue what LZO is; just check the box!)

[[File:Vpn-15.png|center|OpenVPN Advanced Options dialog box]]

A click on “'''OK'''” will return us to the main Edit dialog box...

[[File:Vpn-16.png|center|Click Apply to save the VPN profile]]

...where we will click the “Apply” button to save this VPN profile. That will return us to another familiar screen:

[[File:Vpn-17.png|center|The VPN profile is now saved. Click on the Close button to finish the configuration.]]

Note that your profile has been saved by the name you chose. Now click the “'''Close'''” button.

==Step #3: Connecting Via OpenVPN==

Take a deep breath. Assuming you've followed the above instructions carefully (and assuming I haven't left out any steps), you're ready to connect back to your Amahi server via OpenVPN. Here's how.

Once again, left-click on the wireless-connection icon in the upper screen panel. As before, choose “'''VPN Connections''',” but this time when the sub-menu flies out, you'll see the name of the VPN profile you created. Click on that.

[[File:Vpn-18.png|center|Launching an OpenVPN connection to your Amahi server.]]

If this is the first time you attempted using this connection, Ubuntu will seek your permission to add the security information in your VPN connection profile into its “keyring” (the place Ubuntu stores your other passwords). Click “'''Always Allow'''.”

[[File:Vpn-19.png|center|Allowing the OpenVPN application to access the Ubuntu keyring.]]

If you look carefully at the wireless-connection icon in the upper panel, you'll see a sort of “spinning doughnut” that pops up a small padlock on every revolution. That means that OpenVPN is attempting to make the secure VPN connection. Be patient.

[[File:Vpn-20.png|center|Activity in the wireless-connection icon area.]]

And note that once in a while, the attempt may time out and you'll see something like the following pop-up message:

[[File:Vpn-21.png|center|“VPN Connection Failed” message.]]

(Note the Spinning Doughnut to the left of the sound/volume icon, above.) If at first you don't succeed, try, try again.

Note that when you DO connect, your wireless-connection icon will change subtly, showing a padlock over your signal-strength “antenna”:

[[File:Vpn-22.png|center|The VPN connection “padlock” in the wireless-connection icon.]]

If you hover your cursor over that same icon, a pop-out will also give you a confirmation message:

[[File:Vpn-23.png|center|A “word balloon” confirmation of the VPN connection]]

Of course, the “proof of the pudding” is whether or not you can pull up your Amahi server in a browser window by typing “'''http://hda/'''”:

[[File:Vpn-24.png|center|The Amahi server dashboard page – via your VPN connection!|800px]]

Once you see that, you ''know'' you're in. Congratulations!

To disconnect your VPN session, left-click your wireless-connection icon. Choose “VPN Connections” as before, but this time choose “Disconnect VPN.” That's it – your secure session is terminated.

[[File:Vpn-25.png|center|Disconnecting the VPN session]]

If this doesn't work for you, posting questions in the [http://forums.amahi.org Amahi forums]
[[Category: VPN]]

OpenVPN troubleshooting

2011-02-16T09:51:09Z

Smystaki:

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 tcp to udp 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

== Blocked port 1194 ==
Sometimes if you are behind a corporate firewall or so it 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:<br>
port 1194<br>
into<br>
port 443<br>
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, the 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

==Client reports "TLS handshake failed" & does not connect==
This is usually caused by packet corruption that may happen for some users.<br>
Follow the tutorial on "[[Prevent_SSL_Handshake_Timeouts_In_OpenVPN]]" page to fix this.

[[Category: VPN]]

Hosting a website

2011-02-14T00:01:21Z

Smystaki:

*To access the HDA itself from outside the network using VPN, check out the [[Adito]] application, available to install through the HDA. Adito enables you to access the HDA, and all applications and folders, using just your free username.yourhda.com webaddress.

So you want to run a web server in your Amahi server and make it visible from the web outside your home.

<div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;">
'''NOTICE: making anything visible outside your network can open security issues, so you are doing this at your own risk. Some apps are more secure than others, but there is nothing ultimately secure. Best is to use the [[VPN]] to login back home."
</div>

== Requirements ==
For the purposes of this guide you need either of the following:

* [[VNC]] access to your HDA if headless
** ''Terminal is available under Applications -> System Tools -> Terminal''
* [http://www.amahi.org/apps/ajaxterm Ajaxterm] if headless and no VNC
* A monitor if you are not headless

To host your own web site you need the following:

* Forward a port to your HDA ip address, either for plain insecure http: 80, for https, 443 (advanced users can use other ports). Some routers call this or require a "virtual server"
* Chose a domain name that you own (or your free username.yourhda.com that comes with Amahi). This is how the app will be accessed outside
* Chose the app you want to make accessible outside, let's say, '''yourwebappname'''

== Hosting a single Webapp ==

What you need to do in a terminal (as root) is find the apps conf file then edit the conf file for the app:
{{Code|
Code=su
[enter password]
ls /etc/httpd/conf.d
}}
Find your app .conf file. It will look like 10##-yourwebappname.conf
{{Code|
Code=nano /etc/httpd/conf.d/10##-'''yourwebappname'''.conf
}}

Your conf file should look something like this at the top of the page:
{{Text|
<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
}}
Add this (immediately after the ServerName directive):
{{Text|
ServerAlias username.yourhda.com
}}
So it looks like this:
{{Text|
<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
ServerAlias username.yourhda.com
}}
You can add more server aliases if you want to access the app under those names (for example: ServerAlias myphotos.DomainName.com). Once you are satisfied with the server aliases, you may save and quit nano by following these steps in Windows:

ctrl X
At the prompt, type "y" to save
At the prompt, hit "Enter" to save the file

Restart the server using:
{{Code|
service httpd reload
}}
And you are done, enjoy your website.

== Hosting multiple Webapps ==

''If you wish to have access to multiple webapps, described below is one way to accomplish this:''

# obtain a domain name (i.e., via godaddy.com) --for example yourdomain.com
# for each web app you wish to have access to, establish a CNAME or subdomain--for example something.yourdomain.com---and point it to username.yourhda.com (for example see http://help.godaddy.com/article/679 )
# edit the webapp .conf file (see above) to match the CNAME/subdomain you just established by adding ServerAlias something.yourdomain.com
# don't forget to restart the server each time you edit a .conf file.

:#For example, you could create the subdomain/CNAME: address.yourdomain.com for the AddressBook webapp---point that subdomain to: username.yourhda.com---in the AddressBook .conf file add: ServerAlias address.yourdomain.com---restart the server---you are done, enjoy using multiple webapps!

== Hosting a Website ==

''Prerequisites'': The first order of business is to make sure that your domain name is pointing to your server's IP address. Each website is different, but GoDaddy goes like this:
:* Go to your GoDaddy's ''My Account'' page. Under Dashboard, click yourdomain.com
:** Point your cursor at the Nameserver icon, click ''Set Nameservers''
::: [[File:Nameserverlink.jpg|caption]]
:** Select ''I want to '''forward''' my domains'' and click OK
::: [[File:forwarddomainname.jpg|frameless|caption]]
:* Now go back to your account homepage, and instead of clicking yourdomain.com, check it and click ''View in Domain Manager''
:** Click yourdomain.com
:** Scroll down to '''DNS Manager''' and click ''Launch''
:::[[File:DNSmanagger.jpg|frameless|caption]]
:** Under '''A(Host)''' edit the IP Address(es) to reflect the IP Address of your server. Hit enter and then ''Save Zone File'' when that option appears.
:::[[File:ahostpointsto.jpg|frameless|caption]]
:* The effects should appear within one hour

''Hosting'': Hosting a website on your HDA server is basically the same as hosting a webapp, so if we are able to do the previous guides on hosting a webapp(s) the rest will be a cinch.

We will create the website by creating a webapp. This is a lot easier than it sounds, so don't give up just yet!
# Got your HDA page (http://hda or http://hda.yourhda.com), click ''Setup'' and go to ''Settings''.
## Make sure your ''Advanced Settings'' option is checked (if not, check and click OK past the warning)
# Go to ''Apps'' and then ''Webapps''
# At the very bottom, click ''New Web App'' and type in a name like Website
:This is where your webpage will reside in, you can name this anything you'd like. This is not the title of your website or webpage. Website will be used as the name for this guide
:::[[File:newebapp.jpg|frameless|caption]]
# Do everything as told under the "Hosting a single Webapp" heading above, but of course our app is called Website.
:''Hint:'' Instead of using user.yourhda.com for your ServerAlias, go ahead and use yourdomain.com ('''without the www.''') if you have one from, for example, GoDaddy.
# To easily access your website files, we will make the webapp folder a share by doing the following:
:* In your HDA Dashboard, click ''Setup'' and then ''Shares''
:* Click ''New Share'' at the very bottom
:* We will name our share Website
:** Notice that the path is automatically filled out for us. This is not the path that will be used, so the path that will be typed in will be ''/var/hda/web-apps/Website/''
:::[[File:newshare.jpg|frameless|caption]]
:* Click ''Create this Share'', now the folder will be available from your normal \\hda spot.
:** You can test your new website by creating an index.html (put something simple, like "hi", as a text) in the html folder in your Website share folder, and then going to yourdomain.com

And we are finished. To create your website on Fedora, we can use Bluefish program.
: yum install bluefish
If we would like to use Windows, we can use any program to make the website. Just drag and drop into the share, and under the folders as needed.

== FAQ ==

* Q: Do i need to do anything for <code>username.yourhda.com</code> to work?
No. That comes free and automatically set up with your Amahi HDA

* Q: What if i want to do it for a .html or .php file?
You can do this by creating a Webapp of your own. In the apps tab,
select Webapps and create a new one.
What you do is, create a web app, and put the files into the root
directory of the webap, something like this directory:

/var/hda/web-apps/'''yourwebappname'''/html

this directory belongs to apache. you will have to change the
ownership to your user (recommended) or otherwise add things as root.
* Q: How do I change the ownership?
You can do this by going to the command screen:

su -
{password}
chown {user} /var/hda/web-apps/

Hosting a website

2011-02-14T00:00:41Z

Smystaki:

Hosting a website

2011-02-13T23:58:21Z

Smystaki:

*To access the HDA itself from outside the network using VPN, check out the [[Adito]] application, available to install through the HDA. Adito enables you to access the HDA, and all applications and folders, using just your free username.yourhda.com webaddress.

So you want to run a web server in your Amahi server and make it visible from the web outside your home.

<div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;">
'''NOTICE: making anything visible outside your network can open security issues, so you are doing this at your own risk. Some apps are more secure than others, but there is nothing ultimately secure. Best is to use the [[VPN]] to login back home."
</div>

== Requirements ==
For the purposes of this guide you need either of the following:

* [[VNC]] access to your HDA if headless
** ''Terminal is available under Applications -> System Tools -> Terminal''
* [http://www.amahi.org/apps/ajaxterm Ajaxterm] if headless and no VNC
* A monitor if you are not headless

To host your own web site you need the following:

* Forward a port to your HDA ip address, either for plain insecure http: 80, for https, 443 (advanced users can use other ports). Some routers call this or require a "virtual server"
* Chose a domain name that you own (or your free username.yourhda.com that comes with Amahi). This is how the app will be accessed outside
* Chose the app you want to make accessible outside, let's say, '''yourwebappname'''

== Hosting a single Webapp ==

What you need to do in a terminal (as root) is find the apps conf file then edit the conf file for the app:
{{Code|
Code=su
[enter password]
ls /etc/httpd/conf.d
}}
Find your app .conf file. It will look like 10##-yourwebappname.conf
{{Code|
Code=nano /etc/httpd/conf.d/10##-'''yourwebappname'''.conf
}}

Your conf file should look something like this at the top of the page:
{{Text|
<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
}}
Add this (immediately after the ServerName directive):
{{Text|
ServerAlias username.yourhda.com
}}
So it looks like this:

<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
ServerAlias username.yourhda.com

You can add more server aliases if you want to access the app under those names (for example: ServerAlias myphotos.DomainName.com). Once you are satisfied with the server aliases, you may save and quit nano by following these steps in Windows:

ctrl X
At the prompt, type "y" to save
At the prompt, hit "Enter" to save the file

Restart the server using:

service httpd reload

And you are done, enjoy your website.

== Hosting multiple Webapps ==

''If you wish to have access to multiple webapps, described below is one way to accomplish this:''

# obtain a domain name (i.e., via godaddy.com) --for example yourdomain.com
# for each web app you wish to have access to, establish a CNAME or subdomain--for example something.yourdomain.com---and point it to username.yourhda.com (for example see http://help.godaddy.com/article/679 )
# edit the webapp .conf file (see above) to match the CNAME/subdomain you just established by adding ServerAlias something.yourdomain.com
# don't forget to restart the server each time you edit a .conf file.

:#For example, you could create the subdomain/CNAME: address.yourdomain.com for the AddressBook webapp---point that subdomain to: username.yourhda.com---in the AddressBook .conf file add: ServerAlias address.yourdomain.com---restart the server---you are done, enjoy using multiple webapps!

== Hosting a Website ==

''Prerequisites'': The first order of business is to make sure that your domain name is pointing to your server's IP address. Each website is different, but GoDaddy goes like this:
:* Go to your GoDaddy's ''My Account'' page. Under Dashboard, click yourdomain.com
:** Point your cursor at the Nameserver icon, click ''Set Nameservers''
::: [[File:Nameserverlink.jpg|caption]]
:** Select ''I want to '''forward''' my domains'' and click OK
::: [[File:forwarddomainname.jpg|frameless|caption]]
:* Now go back to your account homepage, and instead of clicking yourdomain.com, check it and click ''View in Domain Manager''
:** Click yourdomain.com
:** Scroll down to '''DNS Manager''' and click ''Launch''
:::[[File:DNSmanagger.jpg|frameless|caption]]
:** Under '''A(Host)''' edit the IP Address(es) to reflect the IP Address of your server. Hit enter and then ''Save Zone File'' when that option appears.
:::[[File:ahostpointsto.jpg|frameless|caption]]
:* The effects should appear within one hour

''Hosting'': Hosting a website on your HDA server is basically the same as hosting a webapp, so if we are able to do the previous guides on hosting a webapp(s) the rest will be a cinch.

We will create the website by creating a webapp. This is a lot easier than it sounds, so don't give up just yet!
# Got your HDA page (http://hda or http://hda.yourhda.com), click ''Setup'' and go to ''Settings''.
## Make sure your ''Advanced Settings'' option is checked (if not, check and click OK past the warning)
# Go to ''Apps'' and then ''Webapps''
# At the very bottom, click ''New Web App'' and type in a name like Website
:This is where your webpage will reside in, you can name this anything you'd like. This is not the title of your website or webpage. Website will be used as the name for this guide
:::[[File:newebapp.jpg|frameless|caption]]
# Do everything as told under the "Hosting a single Webapp" heading above, but of course our app is called Website.
:''Hint:'' Instead of using user.yourhda.com for your ServerAlias, go ahead and use yourdomain.com ('''without the www.''') if you have one from, for example, GoDaddy.
# To easily access your website files, we will make the webapp folder a share by doing the following:
:* In your HDA Dashboard, click ''Setup'' and then ''Shares''
:* Click ''New Share'' at the very bottom
:* We will name our share Website
:** Notice that the path is automatically filled out for us. This is not the path that will be used, so the path that will be typed in will be ''/var/hda/web-apps/Website/''
:::[[File:newshare.jpg|frameless|caption]]
:* Click ''Create this Share'', now the folder will be available from your normal \\hda spot.
:** You can test your new website by creating an index.html (put something simple, like "hi", as a text) in the html folder in your Website share folder, and then going to yourdomain.com

And we are finished. To create your website on Fedora, we can use Bluefish program.
: yum install bluefish
If we would like to use Windows, we can use any program to make the website. Just drag and drop into the share, and under the folders as needed.

== FAQ ==

* Q: Do i need to do anything for <code>username.yourhda.com</code> to work?
No. That comes free and automatically set up with your Amahi HDA

* Q: What if i want to do it for a .html or .php file?
You can do this by creating a Webapp of your own. In the apps tab,
select Webapps and create a new one.
What you do is, create a web app, and put the files into the root
directory of the webap, something like this directory:

/var/hda/web-apps/'''yourwebappname'''/html

this directory belongs to apache. you will have to change the
ownership to your user (recommended) or otherwise add things as root.
* Q: How do I change the ownership?
You can do this by going to the command screen:

su -
{password}
chown {user} /var/hda/web-apps/

Template:Code

2011-02-13T23:53:17Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#777; background-color:#dfd;text-align:left"|{{{lang|{{{2|bash}}}}}} code
|-
|{{#tag:syntaxhighlight|{{{Code|{{{1}}}}}}|lang={{{lang|{{{2|bash}}}}}}|enclose=none}}
|}

Template:Code

2011-02-13T23:51:39Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#777; background-color:#dfd;text-align:left"|{{{lang}}} code
|-
|{{#tag:syntaxhighlight|{{{Code|{{{1}}}}}}|lang={{{lang|{{{2|bash}}}}}}|enclose=none}}
|}

Template:Code

2011-02-13T23:49:12Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#777; background-color:#dfd;text-align:left"|{{{2}}} code
|-
|{{#tag:syntaxhighlight|{{{Code|{{{1}}}}}}|lang={{{lang|{{{2|bash}}}}}}|enclose=none}}
|}

Hosting a website

2011-02-13T23:47:28Z

Smystaki:

*To access the HDA itself from outside the network using VPN, check out the [[Adito]] application, available to install through the HDA. Adito enables you to access the HDA, and all applications and folders, using just your free username.yourhda.com webaddress.

So you want to run a web server in your Amahi server and make it visible from the web outside your home.

<div style="border: 1px solid #B66; padding: .5em 1em; color: #000; background-color: #FEE; margin: 3px 3px 1em 3px;">
'''NOTICE: making anything visible outside your network can open security issues, so you are doing this at your own risk. Some apps are more secure than others, but there is nothing ultimately secure. Best is to use the [[VPN]] to login back home."
</div>

== Requirements ==
For the purposes of this guide you need either of the following:

* [[VNC]] access to your HDA if headless
** ''Terminal is available under Applications -> System Tools -> Terminal''
* [http://www.amahi.org/apps/ajaxterm Ajaxterm] if headless and no VNC
* A monitor if you are not headless

To host your own web site you need the following:

* Forward a port to your HDA ip address, either for plain insecure http: 80, for https, 443 (advanced users can use other ports). Some routers call this or require a "virtual server"
* Chose a domain name that you own (or your free username.yourhda.com that comes with Amahi). This is how the app will be accessed outside
* Chose the app you want to make accessible outside, let's say, '''yourwebappname'''

== Hosting a single Webapp ==

What you need to do in a terminal (as root) is find the apps conf file then edit the conf file for the app:
{{Code|
Code=su
[enter password]
ls /etc/httpd/conf.d
}}
Find your app .conf file. It will look like 10##-yourwebappname.conf

nano /etc/httpd/conf.d/10##-'''yourwebappname'''.conf

Your conf file should look something like this at the top of the page:

<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan

Add this (immediately after the ServerName directive):

ServerAlias username.yourhda.com

So it looks like this:

<VirtualHost *:80>

ServerName app
ServerAlias app.YourDomain.lan
ServerAlias username.yourhda.com

You can add more server aliases if you want to access the app under those names (for example: ServerAlias myphotos.DomainName.com). Once you are satisfied with the server aliases, you may save and quit nano by following these steps in Windows:

ctrl X
At the prompt, type "y" to save
At the prompt, hit "Enter" to save the file

Restart the server using:

service httpd reload

And you are done, enjoy your website.

== Hosting multiple Webapps ==

''If you wish to have access to multiple webapps, described below is one way to accomplish this:''

# obtain a domain name (i.e., via godaddy.com) --for example yourdomain.com
# for each web app you wish to have access to, establish a CNAME or subdomain--for example something.yourdomain.com---and point it to username.yourhda.com (for example see http://help.godaddy.com/article/679 )
# edit the webapp .conf file (see above) to match the CNAME/subdomain you just established by adding ServerAlias something.yourdomain.com
# don't forget to restart the server each time you edit a .conf file.

:#For example, you could create the subdomain/CNAME: address.yourdomain.com for the AddressBook webapp---point that subdomain to: username.yourhda.com---in the AddressBook .conf file add: ServerAlias address.yourdomain.com---restart the server---you are done, enjoy using multiple webapps!

== Hosting a Website ==

''Prerequisites'': The first order of business is to make sure that your domain name is pointing to your server's IP address. Each website is different, but GoDaddy goes like this:
:* Go to your GoDaddy's ''My Account'' page. Under Dashboard, click yourdomain.com
:** Point your cursor at the Nameserver icon, click ''Set Nameservers''
::: [[File:Nameserverlink.jpg|caption]]
:** Select ''I want to '''forward''' my domains'' and click OK
::: [[File:forwarddomainname.jpg|frameless|caption]]
:* Now go back to your account homepage, and instead of clicking yourdomain.com, check it and click ''View in Domain Manager''
:** Click yourdomain.com
:** Scroll down to '''DNS Manager''' and click ''Launch''
:::[[File:DNSmanagger.jpg|frameless|caption]]
:** Under '''A(Host)''' edit the IP Address(es) to reflect the IP Address of your server. Hit enter and then ''Save Zone File'' when that option appears.
:::[[File:ahostpointsto.jpg|frameless|caption]]
:* The effects should appear within one hour

''Hosting'': Hosting a website on your HDA server is basically the same as hosting a webapp, so if we are able to do the previous guides on hosting a webapp(s) the rest will be a cinch.

We will create the website by creating a webapp. This is a lot easier than it sounds, so don't give up just yet!
# Got your HDA page (http://hda or http://hda.yourhda.com), click ''Setup'' and go to ''Settings''.
## Make sure your ''Advanced Settings'' option is checked (if not, check and click OK past the warning)
# Go to ''Apps'' and then ''Webapps''
# At the very bottom, click ''New Web App'' and type in a name like Website
:This is where your webpage will reside in, you can name this anything you'd like. This is not the title of your website or webpage. Website will be used as the name for this guide
:::[[File:newebapp.jpg|frameless|caption]]
# Do everything as told under the "Hosting a single Webapp" heading above, but of course our app is called Website.
:''Hint:'' Instead of using user.yourhda.com for your ServerAlias, go ahead and use yourdomain.com ('''without the www.''') if you have one from, for example, GoDaddy.
# To easily access your website files, we will make the webapp folder a share by doing the following:
:* In your HDA Dashboard, click ''Setup'' and then ''Shares''
:* Click ''New Share'' at the very bottom
:* We will name our share Website
:** Notice that the path is automatically filled out for us. This is not the path that will be used, so the path that will be typed in will be ''/var/hda/web-apps/Website/''
:::[[File:newshare.jpg|frameless|caption]]
:* Click ''Create this Share'', now the folder will be available from your normal \\hda spot.
:** You can test your new website by creating an index.html (put something simple, like "hi", as a text) in the html folder in your Website share folder, and then going to yourdomain.com

And we are finished. To create your website on Fedora, we can use Bluefish program.
: yum install bluefish
If we would like to use Windows, we can use any program to make the website. Just drag and drop into the share, and under the folders as needed.

== FAQ ==

* Q: Do i need to do anything for <code>username.yourhda.com</code> to work?
No. That comes free and automatically set up with your Amahi HDA

* Q: What if i want to do it for a .html or .php file?
You can do this by creating a Webapp of your own. In the apps tab,
select Webapps and create a new one.
What you do is, create a web app, and put the files into the root
directory of the webap, something like this directory:

/var/hda/web-apps/'''yourwebappname'''/html

this directory belongs to apache. you will have to change the
ownership to your user (recommended) or otherwise add things as root.
* Q: How do I change the ownership?
You can do this by going to the command screen:

su -
{password}
chown {user} /var/hda/web-apps/

Template:F14A6OK

2011-02-06T21:55:23Z

Smystaki: Created page with "{| align=center style="background:#EAF2F8; border: 1px solid #aaa; padding: .2em;width: 95%;" !rowspan="2" style="text-align:center"|link= ! width=..."

{| align=center style="background:#EAF2F8; border: 1px solid #aaa; padding: .2em;width: 95%;"
!rowspan="2" style="text-align:center"|[[Image:F14release.png|100px|link=]]
! width=75% style="text-align:center;font-size:large;font-weight: bold" | '''Has Been Tested by AMAHI TEAM'''
!rowspan="2" style="text-align:center"|[[Image:Amahi_Logo.jpg|130px|link=]]
|-
!style="text-align:center; font-size:small;font-weight: normal"|And Is Fully compatible
|}

[[Category:F14_Amahi6_OK]]

File:Amahi Logo.jpg

2011-02-06T21:35:44Z

Smystaki:

Template talk:Code

2011-02-06T02:43:35Z

Smystaki:

----

= Code Formatting =

To add formatting to code, we have a little [[Template:Code|code template]] that can be used like this:

{|style="width: 99%; border-width: 1px; border-style: solid; border-color: #aaa"
! Description
! width=40% | You type
! width=40% | You get
|-
|boxed code
|
<pre>
{{Code|
Code = bash$ ls -l
total 696
...
bash$
}}
</pre>
|
{|
{{Code|
Code = bash$ ls -l
total 696
...
bash$
}}
|}
|}

lang parameter is optional default = bash.

<pre>
{{Code|
Code = bash$ ls -l
total 696
...
bash$
}}
</pre>

Code Parameter name is optional. You have to use in case there are wiki symbols involeved
If you type
<pre>
{{Code|irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
</pre>
you get
{{Code|irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
But
<pre>
{{Code|Code= irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
</pre>
{{Code|Code= irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}

If you type
<pre>
{{Code|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}
</pre>
you get
{{Code|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}

BUT
<pre>
{{Code|lang=JavaScript|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}
</pre>

{{Code|lang=JavaScript|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}

{| class="wikitable" style="float:left"
!Code||Language
|-
|<code>abap</code>||ABAP
|-
|<code>actionscript</code>||ActionScript
|-
|<code>ada</code>||Ada (programming language)
|-
|<code>apache</code>||Apache HTTP Server
|-
|<code>applescript</code>||AppleScript
|-
|<code>asm</code>||Assembly language
|-
|<code>asp</code>||Active Server Pages
|-
|<code>autoit</code>||AutoIt
|-
|<code>bash</code>||Bash (Unix shell)
|-
|<code>basic4gl</code>||Basic4GL
|-
|<code>bf</code>||Brainfuck
|-
|<code>blitzbasic</code>||Blitz BASIC
|-
|<code>bnf</code>||Backus-Naur Form
|-
|<code>c</code>||C (programming language)
|-
|<code>c_mac</code>||C (Mac)
|-
|<code>caddcl</code>||Dialog Control Language
|-
|<code>cadlisp</code>||AutoLISP
|-
|<code>cfdg</code>||CFDG
|-
|<code>cfm</code>||ColdFusion Markup Language
|-
|<code>cil</code>||Common Intermediate Language
|-
|<code>cobol</code>||COBOL
|-
|<code>cpp-qt</code>||Qt (toolkit)
|-
|<code>cpp</code>||C++
|-
|<code>csharp</code>||C Sharp (programming language)
|-
|<code>css</code>||Cascading Style Sheets
|-
|<code>d</code>||D (programming language)
|-
|<code>delphi</code>||Delphi programming language
|-
|<code>diff</code>||diff
|-
|<code>div</code>||DIV
|-
|<code>dos</code>||DOS batch file
|-
|<code>dot</code>||DOT language
|-
|<code>eiffel</code>||Eiffel (programming language)
|-
|<code>fortran</code>||Fortran
|-
|<code>freebasic</code>||FreeBASIC
|-
|<code>genero</code>||Genero
|-
|<code>gettext</code>||GNU gettext
|-
|<code>glsl</code>||GLSL
|-
|<code>gml</code>||Game Maker Language
|-
|<code>gnuplot</code>||Gnuplot
|-
|<code>groovy</code>||Groovy (programming language)
|-
|<code>haskell</code>||Haskell (programming language)
|-
|<code>hq9plus</code>||HQ9+
|-
|<code>html4strict</code>||HTML
|-
|<code>idl</code>||Universal Network Objects
|-
|<code>ini</code>||INI file
|-
|<code>inno</code>||Inno Setup
|-
|<code>intercal</code>||INTERCAL
|-
|<code>io</code>||Io (programming language)
|-
|<code>java</code>||Java (programming language)
|-
|<code>java5</code>||Java (programming language)
|-
|<code>javascript</code>||JavaScript
|-
|<code>kixtart</code>||KiXtart
|-
|<code>klonec</code>||Klone C
|-
|<code>klonecpp</code>||Klone C++
|-
|<code>latex</code>||LaTeX
|-
|<code>lisp</code>||Lisp (programming language)
|-
|<code>lolcode</code>||LOLCODE
|-
|<code>lotusscript</code>||LotusScript
|-
|<code>lua</code>||Lua (programming language)
|}
{| class="wikitable" style="float:left"
!Code||Language
|-
|<code>m68k</code>||Motorola 68000
|-
|<code>make</code>||Make(software)
|-
|<code>matlab</code>||MATLAB
|-
|<code>mirc</code>||mIRC scripting language
|-
|<code>mxml</code>||MXML
|-
|<code>mpasm</code>||PIC microcontroller
|-
|<code>mysql</code>||MySQL
|-
|<code>nsis</code>||Nullsoft Scriptable Install System
|-
|<code>objc</code>||Objective-C
|-
|<code>ocaml-brief</code>||Objective Caml
|-
|<code>ocaml</code>||Objective Caml
|-
|<code>oobas</code>||StarOffice Basic
|-
|<code>oracle8</code>||PL/SQL
|-
|<code>oracle11</code>||PL/SQL
|-
|<code>pascal</code>||Pascal (programming language)
|-
|<code>per</code>||per
|-
|<code>perl</code>||Perl
|-
|<code>php-brief</code>||PHP
|-
|<code>php</code>||PHP
|-
|<code>pixelbender</code>||Adobe Pixel Bender
|-
|<code>plsql</code>||PL/SQL
|-
|<code>povray</code>||POV-Ray
|-
|<code>powershell</code>||Windows PowerShell
|-
|<code>progress</code>||OpenEdge Advanced Business Language
|-
|<code>prolog</code>||Prolog
|-
|<code>providex</code>||ProvideX
|-
|<code>python</code>||Python (programming language)
|-
|<code>qbasic</code>||QBasic
|-
|<code>rails</code>||Ruby on Rails
|-
|<code>reg</code>||Windows Registry
|-
|<code>robots</code>||Robots Exclusion Standard
|-
|<code>ruby</code>||Ruby (programming language)
|-
|<code>rsplus</code>||R (programming language)
|-
|<code>sas</code>||SAS System
|-
|<code>scala</code>||Scala )
|-
|<code>scheme</code>||Scheme (programming language)
|-
|<code>scilab</code>||Scilab
|-
|<code>sdlbasic</code>||SdlBasic
|-
|<code>smalltalk</code>||Smalltalk
|-
|<code>smarty</code>||Smarty
|-
|<code>sql</code>||SQL
|-
|<code>tcl</code>||Tcl
|-
|<code>teraterm</code>||TeraTerm
|-
|<code>text</code>||Plain text
|-
|<code>thinbasic</code>||thinBasic
|-
|<code>tsql</code>||Transact-SQL
|-
|<code>typoscript</code>||TYPO3
|-
|<code>vb</code>||Visual Basic
|-
|<code>vbnet</code>||Visual Basic .NET
|-
|<code>verilog</code>||Verilog
|-
|<code>vhdl</code>||VHSIC Hardware Description Language
|-
|<code>vim</code>||Vimscript
|-
|<code>visualfoxpro</code>||Visual FoxPro
|-
|<code>visualprolog</code>||Visual_Prolog
|-
|<code>whitespace</code>||Whitespace programming language)
|-
|<code>winbatch</code>||Winbatch
|-
|<code>xml</code>||XML
|-
|<code>xorg_conf</code>||Xorg.conf
|-
|<code>xpp</code>||Microsoft Dynamics AX
|-
|<code>z80</code>||Zilog Z80
|}

[[Category:Help]]

Template:Code

2011-02-06T02:39:37Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#777; background-color:#dfd;text-align:left"|code
|-
|{{#tag:syntaxhighlight|{{{Code|{{{1}}}}}}|lang={{{lang|{{{2|bash}}}}}}|enclose=none}}
|}

ZNC

2011-02-06T02:35:52Z

Smystaki: /* mIRC */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|lang=Bash|Code=yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|lang=Bash|Code=service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|Code=Listener4 = +26244}}
* Restart ZNC:
{{Code|lang=Bash|Code=service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:

{{Code|lang=mirc|Code=/server -m <yourHdaIp> -p 26244 -g gZNC -w <username>:<password> -d ZNC}}


=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can enter the following in your browsers address bar:
{{Link|Link=irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}<br />
or
{{Link|Link=irc://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />
or SSL
{{Link|Link=ircs://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''. <br />

{| style="color:black; background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

ZNC

2011-02-06T02:35:21Z

Smystaki: /* mIRC */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|lang=Bash|Code=yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|lang=Bash|Code=service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|Code=Listener4 = +26244}}
* Restart ZNC:
{{Code|lang=Bash|Code=service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
<nowiki>/server -m <yourHdaIp> -p 26244 -g gZNC -w <username>:<password> -d ZNC</nowiki>
{{Code|lang=mirc|Code=/server -m <yourHdaIp> -p 26244 -g gZNC -w <username>:<password> -d ZNC}}


=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can enter the following in your browsers address bar:
{{Link|Link=irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}<br />
or
{{Link|Link=irc://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />
or SSL
{{Link|Link=ircs://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''. <br />

{| style="color:black; background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

Template talk:Link

2011-02-06T02:32:42Z

Smystaki:

----

= Formated Link =

To add formatting to code, we have a little [[Template:Code|code template]] that can be used like this:

{|style="width: 99%; border-width: 1px; border-style: solid; border-color: #aaa"
! Description
! width=40% | You type
! width=40% | You get
|-
|boxed link
|
<pre>
{{Link|Link = irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
</pre>
|
{|
{{Link|Link = irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
|}
|}

[[Category:Help]]

Template:Link

2011-02-06T02:31:19Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#006; background-color:#f9c;text-align:left"|Link
|-
|{{#tag:syntaxhighlight|{{{Link|{{{1}}}}}}|lang=html4strict|enclose=none}}
|}

Template talk:Text

2011-02-06T02:27:10Z

Smystaki: Replaced content with "{{Text| bash$ ls -l total 696 ... bash$ }}"

Template:Text

2011-02-06T02:26:04Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#777; background-color:#fc0;text-align:left"|Text
|-
|{{#tag:syntaxhighlight|{{{Text|{{{1}}}}}}|lang=Text|enclose=none}}
|}

Template:Text

2011-02-06T02:23:55Z

Smystaki:

Template talk:Text

2011-02-06T02:23:07Z

Smystaki: Created page with "{{Text|Ολες οι συνεισφορές στο Amahi θεωρούνται ότι δημοσιεύονται σύμφωνα με την Attribution-Noncommercial-No Derivative..."

{{Text|Ολες οι συνεισφορές στο Amahi θεωρούνται ότι δημοσιεύονται σύμφωνα με την Attribution-Noncommercial-No Derivative Works 3.0 (Βλ. Amahi:Copyrights για λεπτομέρειες). Αν δεν επιθυμείτε τα κείμενά σας να τα επεξεργαστούν κατά την κρίση τους άλλοι χρήστες και να τα διαδώσουν κατά βούληση, παρακαλούμε να μην τα αναρτήσετε σε αυτό το χώρο. Ό,τι συνεισφέρετε στο χώρο αυτό σε κείμενα, διαγράμματα, στοιχεία ή εικόνες πρέπει να είναι δικά σας έργα ή να ανήκουν στο δημόσιο τομέα (public domain) ή να προέρχονται από ελεύθερες ή ανοιχτές πηγές με ρητή άδεια αναδημοσίευσης.}}

Template:Text

2011-02-06T02:20:57Z

Smystaki:

Template:Text

2011-02-06T02:20:32Z

Smystaki: Created page with "{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa" !style="color:#777; background-color:#fc0;text-align:left"|Text |- |{{..."

Template talk:Code

2011-02-06T01:50:45Z

Smystaki:

----

= Code Formatting =

To add formatting to code, we have a little [[Template:Code|code template]] that can be used like this:

{|style="width: 99%; border-width: 1px; border-style: solid; border-color: #aaa"
! Description
! width=40% | You type
! width=40% | You get
|-
|boxed code
|
<pre>
{{Code|lang = Bash |
Code = bash$ ls -l
total 696
...
bash$
}}
</pre>
|
{|
{{Code|lang = Bash |
Code = bash$ ls -l
total 696
...
bash$
}}
|}
|}

lang parameter is optional default = text.

<pre>
{{Code|
Code = bash$ ls -l
total 696
...
bash$
}}
</pre>

Code Parameter name is optional. You have to use in case there are wiki symbols involeved
If you type
<pre>
{{Code|irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
</pre>
you get
{{Code|irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
But
<pre>
{{Code|Code= irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}
</pre>
{{Code|Code= irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}

If you type
<pre>
{{Code|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}
</pre>
you get
{{Code|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}

BUT
<pre>
{{Code|lang=JavaScript|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}
</pre>

{{Code|lang=JavaScript|
Code= jQuery(document).ready(function(){
jQuery("#slider").easySlider({
auto: true,
continuous: true,
controlsShow: false,
prevText: '',
nextText: '',
pause: 3000
});
});}}

{| class="wikitable" style="float:left"
!Code||Language
|-
|<code>abap</code>||[[:en:ABAP|ABAP]]
|-
|<code>actionscript</code>||[[:en:ActionScript|ActionScript]]
|-
|<code>ada</code>||[[:en:Ada (programming language)|Ada]]
|-
|<code>apache</code>||[[:en:Apache HTTP Server|Apache Configuration]]
|-
|<code>applescript</code>||[[:en:AppleScript|AppleScript]]
|-
|<code>asm</code>||[[:en:Assembly language|ASM]]
|-
|<code>asp</code>||[[:en:Active Server Pages|Active Server Pages (ASP)]]
|-
|<code>autoit</code>||[[:en:AutoIt|AutoIt]]
|-
|<code>bash</code>||[[:en:Bash (Unix shell)|Bash]]
|-
|<code>basic4gl</code>||[[:en:Basic4GL|Basic4GL]]
|-
|<code>bf</code>||[[:en:Brainfuck|Brainfuck]]
|-
|<code>blitzbasic</code>||[[:en:Blitz BASIC|Blitz BASIC]]
|-
|<code>bnf</code>||[[:en:Backus-Naur Form|Backus-Naur Form]]
|-
|<code>c</code>||[[:en:C (programming language)|C]]
|-
|<code>c_mac</code>||C (Mac)
|-
|<code>caddcl</code>||[[:en:Dialog Control Language|AutoCAD DCL]]
|-
|<code>cadlisp</code>||[[:en:AutoLISP|AutoLISP]]
|-
|<code>cfdg</code>||CFDG
|-
|<code>cfm</code>||[[:en:ColdFusion_Markup_Language|ColdFusion Markup Language]]
|-
|<code>cil</code>||[[:en:Common_Intermediate_Language|Common Intermediate Language (CIL)]]
|-
|<code>cobol</code>||[[:en:COBOL|COBOL]]
|-
|<code>cpp-qt</code>||[[:en:Qt (toolkit)|C++ (Qt toolkit)]]
|-
|<code>cpp</code>||[[:en:C++|C++]]
|-
|<code>csharp</code>||[[:en:C Sharp (programming language)|C#]]
|-
|<code>css</code>||[[:en:Cascading Style Sheets|Cascading Style Sheets (CSS)]]
|-
|<code>d</code>||[[:en:D (programming language)|D]]
|-
|<code>delphi</code>||[[:en:Delphi programming language|Delphi]]
|-
|<code>diff</code>||[[:en:diff|Diff]]
|-
|<code>div</code>||DIV
|-
|<code>dos</code>||[[:en:DOS batch file|DOS batch file]]
|-
|<code>dot</code>||[[:en:DOT language|DOT]]
|-
|<code>eiffel</code>||[[:en:Eiffel (programming language)|Eiffel]]
|-
|<code>fortran</code>||[[:en:Fortran|Fortran]]
|-
|<code>freebasic</code>||[[:en:FreeBASIC|FreeBASIC]]
|-
|<code>genero</code>||Genero
|-
|<code>gettext</code>||[[:en:GNU_gettext|GNU internationalization (i18n) library]]
|-
|<code>glsl</code>||[[:en:GLSL|OpenGL Shading Language (GLSL)]]
|-
|<code>gml</code>||[[:en:Game Maker Language|Game Maker Language (GML)]]
|-
|<code>gnuplot</code>||[[:en:Gnuplot|gnuplot]]
|-
|<code>groovy</code>||[[:en:Groovy (programming language)|Groovy]]
|-
|<code>haskell</code>||[[:en:Haskell (programming language)|Haskell]]
|-
|<code>hq9plus</code>||HQ9+
|-
|<code>html4strict</code>||[[:en:HTML|HTML]]
|-
|<code>idl</code>||[[:en:Universal Network Objects|Uno IDL]]
|-
|<code>ini</code>||[[:en:INI file|INI]]
|-
|<code>inno</code>||[[:en:Inno Setup|Inno]]
|-
|<code>intercal</code>||[[:en:INTERCAL|INTERCAL]]
|-
|<code>io</code>||[[:en:Io (programming language)|Io]]
|-
|<code>java</code>||[[:en:Java (programming language)|Java]]
|-
|<code>java5</code>||[[:en:Java (programming language)|Java(TM) 2 Platform Standard Edition 5.0 ]]
|-
|<code>javascript</code>||[[:en:JavaScript|JavaScript]]
|-
|<code>kixtart</code>||[[:en:KiXtart|KiXtart]]
|-
|<code>klonec</code>||Klone C
|-
|<code>klonecpp</code>||Klone C++
|-
|<code>latex</code>||[[:en:LaTeX|LaTeX]]
|-
|<code>lisp</code>||[[:en:Lisp (programming language)|Lisp]]
|-
|<code>lolcode</code>||[[:en:LOLCODE|LOLCODE]]
|-
|<code>lotusscript</code>||[[:en:LotusScript|LotusScript]]
|-
|<code>lua</code>||[[:en:Lua (programming language)|Lua]]
|}
{| class="wikitable" style="float:left"
!Code||Language
|-
|<code>m68k</code>||[[:en:Motorola 68000|Motorola 68000 Assembler]]
|-
|<code>make</code>||[[:en:Make_(software)|make]]
|-
|<code>matlab</code>||[[:en:MATLAB|MATLAB M]]
|-
|<code>mirc</code>||[[:en:mIRC scripting language|mIRC scripting language]]
|-
|<code>mxml</code>||[[:en:MXML|MXML]]
|-
|<code>mpasm</code>||[[:en:PIC microcontroller|Microchip Assembler]]
|-
|<code>mysql</code>||[[:en:MySQL|MySQL]]
|-
|<code>nsis</code>||[[:en:Nullsoft Scriptable Install System|Nullsoft Scriptable Install System (NSIS)]]
|-
|<code>objc</code>||[[:en:Objective-C|Objective-C]]
|-
|<code>ocaml-brief</code>||[[:en:Objective Caml|OCaml]]
|-
|<code>ocaml</code>||[[:en:Objective Caml|OCaml]]
|-
|<code>oobas</code>||[[:en:StarOffice Basic|OpenOffice.org Basic]]
|-
|<code>oracle8</code>||[[:en:PL/SQL|Oracle 8 SQL]]
|-
|<code>oracle11</code>||[[:en:PL/SQL|Oracle 11 SQL]]
|-
|<code>pascal</code>||[[:en:Pascal (programming language)|Pascal]]
|-
|<code>per</code>||per
|-
|<code>perl</code>||[[:en:Perl|Perl]]
|-
|<code>php-brief</code>||[[:en:PHP|PHP]]
|-
|<code>php</code>||[[:en:PHP|PHP]]
|-
|<code>pixelbender</code>||[[:en:Adobe_Pixel_Bender|Pixel Bender]]
|-
|<code>plsql</code>||[[:en:PL/SQL|PL/SQL]]
|-
|<code>povray</code>||[[:en:POV-Ray|Persistence of Vision Raytracer]]
|-
|<code>powershell</code>||[[:en:Windows_PowerShell|Windows PowerShell]]
|-
|<code>progress</code>||[[:en:OpenEdge_Advanced_Business_Language|OpenEdge Advanced Business Language]]
|-
|<code>prolog</code>||[[:en:Prolog|Prolog]]
|-
|<code>providex</code>||[[:en:ProvideX|ProvideX]]
|-
|<code>python</code>||[[:en:Python (programming language)|Python]]
|-
|<code>qbasic</code>||[[:en:QBasic|QBasic/QuickBASIC]]
|-
|<code>rails</code>||[[:en:Ruby on Rails|Rails]]
|-
|<code>reg</code>||[[:en:Windows Registry|Windows Registry]]
|-
|<code>robots</code>||[[:en:Robots Exclusion Standard|robots.txt]]
|-
|<code>ruby</code>||[[:en:Ruby (programming language)|Ruby]]
|-
|<code>rsplus</code>||[[:en:R (programming language)|R/S+]]
|-
|<code>sas</code>||[[:en:SAS System|SAS]]
|-
|<code>scala</code>||[[:en:Scala_(programming_language)|Scala]]
|-
|<code>scheme</code>||[[:en:Scheme (programming language)|Scheme]]
|-
|<code>scilab</code>||[[:en:Scilab|Scilab]]
|-
|<code>sdlbasic</code>||[[:en:SdlBasic|SdlBasic]]
|-
|<code>smalltalk</code>||[[:en:Smalltalk|Smalltalk]]
|-
|<code>smarty</code>||[[:en:Smarty|Smarty]]
|-
|<code>sql</code>||[[:en:SQL|SQL]]
|-
|<code>tcl</code>||[[:en:Tcl|Tcl]]
|-
|<code>teraterm</code>||[[:en:TeraTerm|Tera Term]]
|-
|<code>text</code>||[[:en:Plain text|Plain text]]
|-
|<code>thinbasic</code>||[[:en:thinBasic|thinBasic]]
|-
|<code>tsql</code>||[[:en:Transact-SQL|Transact-SQL]]
|-
|<code>typoscript</code>||[[:en:TYPO3|TypoScript]]
|-
|<code>vb</code>||[[:en:Visual Basic|Visual Basic]]
|-
|<code>vbnet</code>||[[:en:Visual Basic .NET|Visual Basic .NET]]
|-
|<code>verilog</code>||[[:en:Verilog|Verilog]]
|-
|<code>vhdl</code>||[[:en:VHSIC Hardware Description Language|VHDL]]
|-
|<code>vim</code>||[[:en:Vimscript|Vimscript]]
|-
|<code>visualfoxpro</code>||[[:en:Visual FoxPro|Visual FoxPro]]
|-
|<code>visualprolog</code>||[[:en:Visual_Prolog|Visual Prolog]]
|-
|<code>whitespace</code>||[[:en:Whitespace_(programming_language)|Whitespace]]
|-
|<code>winbatch</code>||[[:en:Winbatch|Winbatch]]
|-
|<code>xml</code>||[[:en:XML|XML]]
|-
|<code>xorg_conf</code>||[[:en:Xorg.conf|Xorg.conf]]
|-
|<code>xpp</code>||[[:en:Microsoft_Dynamics_AX|X++]]
|-
|<code>z80</code>||[[:en:Zilog Z80|ZiLOG Z80 Assembler]]
|}

[[Category:Help]]

ZNC

2011-02-06T01:47:52Z

Smystaki: /* SSL Configuration */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|lang=Bash|Code=yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|lang=Bash|Code=service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|Code=Listener4 = +26244}}
* Restart ZNC:
{{Code|lang=Bash|Code=service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
<nowiki>/server -m <yourHdaIp> -p 26244 -g gZNC -w <username>:<password> -d ZNC</nowiki>


=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can write the following in your browsers address bar:
{{Link|Link=irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}<br />
or
{{Link|Link=irc://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />
or SSL
{{Link|Link=ircs://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''. <br />

{| style="color:black; background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

Template talk:Code

2011-02-06T01:44:34Z

Smystaki:

Template talk:Code

2011-02-06T01:42:03Z

Smystaki: /* Code Formatting */

ZNC

2011-02-06T01:24:52Z

Smystaki: /* SSL Configuration */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|Lang=Bash|Code=yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|Lang=Bash|Code=service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|Code=Listener4 = +26244}}
* Restart ZNC:
{{Code|service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
<nowiki>/server -m <yourHdaIp> -p 26244 -g gZNC -w <username>:<password> -d ZNC</nowiki>


=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can write the following in your browsers address bar:
{{Link|Link=irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}<br />
or
{{Link|Link=irc://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />
or SSL
{{Link|Link=ircs://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''. <br />

{| style="color:black; background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

ZNC

2011-02-06T01:14:18Z

Smystaki: /* Chatzilla (FireFox Add-on) */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|<nowiki>Listener4 = +26244</nowiki>}}
* Restart ZNC:
{{Code|service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
<nowiki>/server -m <yourHdaIp> -p 26244 -g gZNC -w <username>:<password> -d ZNC</nowiki>


=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can write the following in your browsers address bar:
{{Link|Link=irc://<YouHdaIp>:26244/<channel>/?pass=<ZncUser>:<ZncUserPass>}}<br />
or
{{Link|Link=irc://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />
or SSL
{{Link|Link=ircs://<YourHdaIp>:26244/,needpass?pass=<ZncUser>:<ZncUserPass>}}<br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''. <br />

{| style="color:black; background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

Template talk:Code

2011-02-06T01:10:09Z

Smystaki:

Template:Code

2011-02-06T01:06:17Z

Smystaki:

{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa"
!style="color:#777; background-color:#dfd;text-align:left"|code
|-
|{{#tag:syntaxhighlight|{{{Code|{{{1}}}}}}|lang={{{lang|{{{2|text}}}}}}|enclose=none}}
|}

Template talk:Link

2011-02-06T01:03:41Z

Smystaki: /* Code Formatting */

Template:Link

2011-02-06T00:53:30Z

Smystaki:

Template talk:Link

2011-02-06T00:33:11Z

Smystaki: Created page with "---- = Code Formatting = To add formatting to code, we have a little code template that can be used like this: <!-- <pre> {{Code|bash$ ls -l total 696 ... bas..."

Template:Link

2011-02-06T00:29:50Z

Smystaki: Created page with "{|style="width: 99%; border-collapse: collapse; border-width: 1px; border-style: solid; border-color: #aaa" !style="color:#006; background-color:#f9c;text-align:left"|Link |- |{{..."

ZNC

2011-02-06T00:09:36Z

Smystaki: /* Chatzilla (FireFox Add-on) */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|<nowiki>Listener4 = +26244</nowiki>}}
* Restart ZNC:
{{Code|service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
{{Code|/server -m <ipaddress_of_hda> -p 26244 -g gZNC -w <username>:<password> -d ZNC}}

<table cellspacing="0" border="1">
<tr>
<th>Option</th>
<th>Description</th>
</tr>
<tr>
<td><ipaddress_of_hda></td>
<td>The ip address of the HDA where you installed ZNC</td>
</tr>
<tr>
<td><username></td>
<td>Username that's configured to connect to a channel</td>
</tr>
<tr>
<td><password></td>
<td>Password for the username that's configured to connect to a channel</td>
</tr>
</table><br />

=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can write the following in your browsers address bar:

<nowiki>irc://192.168.1.10:26244/amahi/?pass=ZncUser:ZncPass</nowiki><br />
OR
<nowiki>irc://<YourHdaIp>:<ZncPort>/,needpass?pass=<ZncUser>:<ZncUserPass></nowiki><br />

Case you use secure shell
<nowiki>ircs://<YourHdaIp>:<ZncPort>/,needpass?pass=<ZncUser>:<ZncUserPass></nowiki><br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''.

{| style="color:black background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

ZNC

2011-02-06T00:08:46Z

Smystaki: /* Chatzilla (FireFox Add-on) */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|<nowiki>Listener4 = +26244</nowiki>}}
* Restart ZNC:
{{Code|service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
{{Code|/server -m <ipaddress_of_hda> -p 26244 -g gZNC -w <username>:<password> -d ZNC}}

<table cellspacing="0" border="1">
<tr>
<th>Option</th>
<th>Description</th>
</tr>
<tr>
<td><ipaddress_of_hda></td>
<td>The ip address of the HDA where you installed ZNC</td>
</tr>
<tr>
<td><username></td>
<td>Username that's configured to connect to a channel</td>
</tr>
<tr>
<td><password></td>
<td>Password for the username that's configured to connect to a channel</td>
</tr>
</table><br />

=== Chatzilla (FireFox Add-on) ===
After installation of Chatzilla Add-on you can write the following in your browsers address bar:

<nowiki>irc://192.168.1.10:26244/amahi/?pass=ZncUser:ZncPass</nowiki><br />
OR
<nowiki>irc://<YourHdaIp>:<ZncPort>/,needpass?pass=<ZncUser>:<ZncUserPass></nowiki><br />

Case you use secure shell
<nowiki>ircs://<YourHdaIp>:<ZncPort>/,needpass?pass=<ZncUser>:<ZncUserPass></nowiki><br />

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''.

{| style="color:black background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).

ZNC

2011-02-05T23:33:11Z

Smystaki: /* Chatzilla (FireFox Add-on) */

[[Category: Apps]]
[http://www.amahi.org/apps/znc ZNC] is an IRC bounce with many advanced features such as a built-in web interface, persistent connection (detaching), multiple users, per channel playback buffer, SSL, IPv6, transparent DCC bouncing, and c++ module support, to name a few.

== About ZNC in Amahi ==
* Currently '''BETA''' in Amahi.
* The application makes use of your HDA first admin user. To log in to the web interface, enter that user name and the password is ''admin''. You can change the password once logged in to anything you desire.
* Once the application is installed, you are automatically connected to the IRC for the server '''irc.freenode.net'''. This setting can be turned off via the web interface if you do not want to autoconnect when ZNC is started.
* ZNC appears in the '''Servers''' tab so you can stop, start, and restart as needed.

== SSL Configuration ==
To enable SSL support, some manual configuration must be done.

* As '''root''' user, install one dependency:
{{Code|yum -y install mod_ssl}}

* Change the line in '''''/etc/httpd/conf.d/####-znc.conf''''' to read (replace #### with the number in your file name):
{{Code|RedirectPermanent / <nowiki>https://znc:26244</nowiki>}}
* Restart the web server:
{{Code|service httpd restart}}
* Modify the line in '''''/home/username/.znc/config/znc.conf''''' to read:
{{Code|<nowiki>Listener4 = +26244</nowiki>}}
* Restart ZNC:
{{Code|service znc restart}}
* Access the web console via '''<nowiki>https://znc:26244</nowiki>'''
* All connections with IRC clients will be SSL. When you add new servers, ensure you precede the port number with a '''+'''. The default server on install is already set for SSL communication.

'''NOTE:''' See [http://en.znc.in/wiki/Configuration ZNC Configuration] for more guidance on customization.

== IRC Client Setup ==
=== mIRC ===
When using the mIRC client you will need to connect to ZNC using the following command:
{{Code|/server -m <ipaddress_of_hda> -p 26244 -g gZNC -w <username>:<password> -d ZNC}}

<table cellspacing="0" border="1">
<tr>
<th>Option</th>
<th>Description</th>
</tr>
<tr>
<td><ipaddress_of_hda></td>
<td>The ip address of the HDA where you installed ZNC</td>
</tr>
<tr>
<td><username></td>
<td>Username that's configured to connect to a channel</td>
</tr>
<tr>
<td><password></td>
<td>Password for the username that's configured to connect to a channel</td>
</tr>
</table><br />

=== Chatzilla (FireFox Add-on) ===

Coming soon...
After installation of Chatzilla Add-on you can write the following in your browsers adress bar

{{Code|<nowiki>irc://192.168.1.10:26244/amahi/?pass=ZncUser:ZncPass</nowiki>}}

== Client Commands ==
Commands are given to ZNC by messaging the virtual user *status. Likewise, modules are communicated to by messaging *modname as well. Alternatively you can use ''/znc command'' instead of ''/msg *status command'' and ''/znc *module command'' instead of ''/msg *module command''.

{| style="color:black background-color:#ffffcc;" cellpadding="1" cellspacing="0" border="1"
! '''Command'''
! '''Arguments'''
! '''Description'''
|+
|-
| Version
|
| Prints which version of znc this is
|-
| ListDCCs
|
| List all active DCCs
|-
| ListMods
|
| List all loaded modules
|-
| ListAvailMods
|
| List all available modules
|-
| ListChans
|
| List all channels
|-
| ListNicks
| <#chan>
| List all nicks on a channel
|-
| ListServers
|
| List all servers
|-
| AddServer
| <host> [[+]port] [pass]
| Add a server to the list
|-
| RemServer
| <host>
| Remove a server from the list
|-
| Enablechan
| <#chan>
| Enable the channel
|-
| Detach
| <#chan>
| Detach from the channel
|-
| Topics
|
| Show topics in all channels
|-
| PlayBuffer
| <#chan>
| Play back the buffer for a given channel
|-
| ClearBuffer
| <#chan>
| Clear the buffer for a given channel
|-
| ClearAllChannelBuffers
|
| Clear the channel buffers
|-
| SetBuffer
| <#chan> [linecount]
| Set the buffer count for a channel
|-
| SetVHost
| <vhost (ip preferred)>
| Set the VHost for this connection
|-
| ClearVHost
|
| Clear the VHost for this connection
|-
| Jump
|
| Jump to the next server in the list
|-
| Disconnect
|
| Disconnect from IRC
|-
| Connect
|
| Reconnect to IRC
|-
| Send
| <nick> <file>
| Send a shell file to a nick on IRC
|-
| Get
| <file>
| Send a shell file to yourself
|-
| LoadMod
| <module>
| Load a module
|-
| UnloadMod
| <module>
| Unload a module
|-
| ReloadMod
| <module>
| Reload a module
|-
| ShowMOTD
|
| Show the message of the day
|-
| SetMOTD
| <Message>
| Set the message of the day
|-
| AddMOTD
| <Message>
| Append <Message> to MOTD
|-
| ClearMOTD
|
| Clear the MOTD
|-
| Rehash
|
| Reload znc.conf from disk
|-
| SaveConfig
|
| Save the current settings to disk
|-
| ListUsers
|
| List all users/clients connected to znc
|-
| ListClients
| [User]
| List all clients connected to your znc user
|-
| Traffic
|
| Show basic traffic stats for all znc users
|-
| Uptime
|
| Show how long ZNC is already running
|-
| Broadcast
| [message]
| Broadcast a message to all users
|-
| Shutdown
| [message]
| Shutdown znc completely
|-
| Restart
| [message]
| Restarts znc
|}

'''NOTE:''' Go [http://en.znc.in/wiki/Modules here] for guidance on how to use ZNC modules.

== Troubleshooting ==
=== ZNC can't connect to server (No route to host) ===
If ZNC can't connect to a IRC server with the message:
Attempting to connect to [chat.freenode.net +7000] ...
Disconnected from IRC (No route to host). Reconnecting...
You could try using the IP address of the server you are trying to connect to. For '''''chat.freenode.net''''' this IP is:
'''''140.211.166.3'''''
* Go to your [http://znc:26244 ZNC webadmin page]
* Login using your username and password
* Click on "Your Settings"
* Edit the server name in the '''''Servers:''''' text box.
ZNC will pickup this new server name the next time trying to connect (wait a minute or so).