From: jan@aims.ac.za
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] ipkg install batman over ssh: postinst fails
Date: Sun, 16 Nov 2008 17:41:59 +0200 [thread overview]
Message-ID: <20081116154159.GC26177@aims.ac.za> (raw)
Hi
I have a mesh running freifunk â.6.32 nodes.
I am using the recommended batman0.2 ipkg to test it next
to OLSR. (Is there no ipkg package and source for 0.3 or
the latest stable?)
When I did two nodes manually, I installed and set the network
migration, and saw some batman packets.
Then I went ahead and scripted an install on all the nodes (about 40).
It goes, with dropbear authorized_keys, for each node in $NEWIP:
# batman sources
scp root@${NEWIP}:/etc/ipkg.conf .
patch ipkg.conf < ipkg.conf.patch
scp ipkg.conf root@${NEWIP}:/etc/ipkg.conf
# update
ssh root@${NEWIP} ipkg update
#########################
## Admin > B.A.T.M.A.N ##
#########################
# Setup screen for migration of network (only shown once)
/usr/sbin/nvram set ff_bat_netmig=172.18/172.16
# B.A.T.M.A.N. on/off
/usr/sbin/nvram set ff_bat_start=1
# WLAN as eth1:bat on subnet/16
/usr/sbin/nvram set ff_bat_ran_on=1
/usr/sbin/nvram set ff_bat_ran_if=eth1:bat
/usr/sbin/nvram set ff_bat_ran_ip=172.16.174.97
/usr/sbin/nvram set ff_bat_ran_pf=16
# LAN as br0 on subnet/29
/usr/sbin/nvram set ff_bat_lan_on=1
/usr/sbin/nvram set ff_bat_lan_if=br0
/usr/sbin/nvram set ff_bat_lan_ip=192.168.174.97
/usr/sbin/nvram set ff_bat_lan_pf=29
# local internet-bandwidth: This is not internet gw
/usr/sbin/nvram set ff_bat_gw_uplink=0
# common used gateway: set no default route
/usr/sbin/nvram set ff_bat_gw_choose=0
# preferred gateway
# HNA
# Viz server
# Hello interval (1000ms)
# Deamon stakeout
# Stop OLSR
# Open firewall
/usr/sbin/nvram set ff_bat_fw=1
#
##########################
## Admin > B.A.T.M.A.N. ##
##########################
ssh root@${NEWIP} ipkg install batmand freifunk-batman
# Next line must be done with expect else nvram not found
# For now it will be done on reboot anyway
#ssh root@${NEWIP} /etc/init.d/S66batman restart
The nvram command is usually not in the path over an ssh like
that (not interactive, passing the command to ssh as an argument)
thus I use /usr/sbin/nvram. In two places this fail:
The freifunk-batman package:
Unpacking freifunk-batman...Done.
Configuring freifunk-batman...//usr/lib/ipkg/info/freifunk-batman.postinst: 10: nvram: not found
//usr/lib/ipkg/info/freifunk-batman.postinst: 10: nvram: not found
Done.
And the S66batman restart, which I did manually.
Now the batman runs, has all the nvram settings, though I didn't go through
the prompt for network migration via the web interface -- I did the script
above. But there are no batman neigbours or messages shown on the info/status
pages in the web interface. Even when I reinstalled freifunk-batman two nodes manually,
that is via interactive ssh, and there was no error, I am still getting no batman
neigbours shown.
Usually I do such cases with expect, there are several places
in my freifunk install / upgrade script where I do this).
The long term answer is clearly? a trx/bin image of our own.
In the meantime, do I have to reflash them, install batman manually
or with expect? Can I even do that or what happens when the web interface
is used to enter the network migration info, which is now not happening
on my nodes?
regards,
Jan
next reply other threads:[~2008-11-16 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 15:41 jan [this message]
2008-11-16 15:48 ` [B.A.T.M.A.N.] ipkg install batman over ssh: postinst fails Outback Dingo
2008-11-16 15:52 ` Jan Groenewald
2008-11-16 16:02 ` Outback Dingo
2008-11-16 16:12 ` Jan Groenewald
2008-11-16 16:15 ` Marek Lindner
2008-11-16 16:37 ` Jan Groenewald
2008-11-16 16:46 ` Marek Lindner
2008-11-16 16:53 ` [B.A.T.M.A.N.] ipkg install batman over ssh: postinst failsi Jan Groenewald
2008-11-16 17:05 ` Marek Lindner
2008-11-16 17:12 ` Jan Groenewald
2008-11-16 17:26 ` Marek Lindner
2008-11-17 9:44 ` Axel Neumann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081116154159.GC26177@aims.ac.za \
--to=jan@aims.ac.za \
--cc=b.a.t.m.a.n@open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox