Making the VoCore easier to connect to

After you get basic connectivity to your VoCore there are a couple of things you can do to make it a bit easier to work with on a daily basis. I work in Linux so my advice is oriented to the Linux/Unix way of doing things. Since modern apple systems are based on Unix there are parallels to the linux way, but I am not familiar with the details. If you work in on a Microsoft system you are on your own, PuTTY is a popular way to connect from Windows but it is very limited in some areas.

I work in a ssh session quite a bit and transfer files to the VoCore with scp so I set up ssh to log in without using a password. To do this you need a public key, either rsa or dsa. You may already have one, to see just run ls ~/.ssh in a terminal session. If you see either id_dsa.pub or id_rsa.pub you already have a key. If not you need to use ssh-keygen to set one up.

To allow connecting without the password nonsense you just run
scp ~/.ssh/id_rsa.pub root@your VoCore's IP:/etc/dropbear/authorized_keys
you will need to use your password one last time, from now on either ssh or scp will connect using your key for authorization.

Now that this is set up, using the VoCore’s IP is a pain as well, both having to type it and also because it may change from time to time. To avoid this I use avahi. In a ssh session on the VoCore you need a couple of packages:

opkg update
opkg install dbus avahi-daemon

If the opkg update returns an error then you need to set up a working opkg.conf. The openwrt snapshots have changed the layout of their package repository so you need something like this to access it:
src/gz base http://downloads.openwrt.org/snapshots/trunk/ramips/generic/packages/base
src/gz luci http://downloads.openwrt.org/snapshots/trunk/ramips/generic/packages/luci
src/gz management http://downloads.openwrt.org/snapshots/trunk/ramips/generic/packages/management
src/gz packages http://downloads.openwrt.org/snapshots/trunk/ramips/generic/packages/packages
src/gz routing http://downloads.openwrt.org/snapshots/trunk/ramips/generic/packages/routing
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay

If you want to use my repository which mimics the original VoCore image you need this:
src/gz chaos_calmer_packages http://noblepepper.com/wp/wp-content/vocore-1.0b/packages
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay

For some reason the dbus/avahi configuration is not installed by the packages, you will need to get it like this:
cd /etc/dbus-1/system.d/
mv avahi-dbus.conf avahi-dbus.conf.orig
wget http://noblepepper.com/wp/wp-content/vocore-1.0a/avahi-dbus.conf
cd -

Now you need to enable and start the daemons like this:
/etc/init.d/dbus enable
/etc/init.d/dbus start
/etc/init.d/avahi-daemon enable
/etc/init.d/avahi-daemon start

Now you can use a name for your vocore instead of the IP, it is just the VoCore’s hostname followed by .local. You can see your hostname with
uci show system.@system[0].hostname
Which for me is VoCore, with some images it is OpenWrt. Now I connect to my VoCore like this:
ssh vocore.local

Since I am using linux I can also find the luci interface by entering vocore.local in my browser address bar, this should work out of the box for Apple users as well. If you are using windows you will need to install support for this, I believe the appropriate software is Bonjour

You should also go to System->System in luci and set the time zone to your location so the time is correct.