good to hear that your setup works now, however batmand-alpha can not be the
culprit. If batmand-alpha wouldn't be able to find its neighbors the MPs would
not be able to talk to each other. You should upgrade the version in your
router to batmand-alpha, the old version will crash as soon as you begin to
announce Internet gateways from a batmand-alpha. There can be more unexpected
problems.
However there seems to be one mistake in your configuration:
> > Getting wrt54gl configure and ready
> > -----------------------------------
...
> > edit /etc/config/wireless
...
> > # REMOVE THIS LINE TO ENABLE WIFI:
> > option disabled 0
Maybe you didn't remove the line "option disabled 0" during your previous
installation?
Cheers,
Elektra
--
You received this message because you are subscribed to the Google Groups "village-telco-dev" group.
To post to this group, send email to village-...@googlegroups.com.
To unsubscribe from this group, send email to village-telco-...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/village-telco-dev?hl=en.
> Thanks a bunch. If I understand correctly "option disabled 0" simply enable
> the wireless. Sure I will remove it from config file. Since I'm using
> kamikaze 8.09.2 on wrt54gl, which version of batman-alpha that I should
> use? Is this the correct one:
> http://downloads.open-mesh.net/batman/development/binaries/misc/batmand_0.4
> -alpha-current_mipsel-kk-elf-32-lsb-dynamic.ipk
to be honest I'm not sure. If you use a version that includes "-lsb-dynamic"
in the name, the program needs a certain version of dynamic shared libraries
from uclibc - thats the C library it is linked against. If the uclibc version
doesn't match it won't start.
I know that the versions in http://downloads.open-
mesh.org/batman/development/binaries/wrt-freifunk/ work with the Freifunk
firmware, but these are based on the old OpenWRT Whiterussian version, not
Kamikaze. The version of uclibc might have changed over the time.
Try http://downloads.open-mesh.org/batman/development/binaries/wrt-
freifunk/batmand_0.4-alpha-current_mipsel-wr-elf-32-lsb-dynamic.ipk first - if
this version starts, it is fine. If the uclibc version doesn't match it won't
start or crash immediately. In that case, uninstall it:
opkg remove batmand
If the dynamic version doesn't work for you, use:
http://downloads.open-mesh.org/batman/development/binaries/mipsel-
kamikaze/batmand_0.4-alpha-rv1534_mipsel-kk-elf-32-lsb-static.tgz
This version is statically compiled, so it is independend from shared
libraries. Note you have to unpack and install it by hand.
copy it to /tmp
(cd /tmp, wget http://downloads.open-
mesh.org/batman/development/binaries/mipsel-kamikaze/batmand_0.4-alpha-
rv1534_mipsel-kk-elf-32-lsb-static.tgz)
tar xvzf batmand_0.4-alpha-rv1534_mipsel-kk-elf-32-lsb-static.tgz
mv batmand*** /usr/bin/batmand
Cheers,
Elektra
Cheers,
Elektra
thats all fine. The first warning doesn't make sense since the current
development "alpha version" works really well, I don't know of current
problems.
You can skip the option --disable-client-nat on the mesh gateway node, the
option is superfluous. You may want to add it to the batmand configuration of
the MPs (gateway clients) in the mesh, if they provide Internet uplink
functionality for computers connected to their LAN port. This option allows to
act them as uplink without the need to do NAT there.
Cheers,
Elektra