mesh-extender-builder

84 views
Skip to first unread message

Claes Giljegard

unread,
Oct 2, 2014, 4:13:46 PM10/2/14
to serval-proje...@googlegroups.com
Hi,

I got two mr3020 and i am trying to follow the instructions on
When running the gather-image-files script i get errors when performing the git clone.
With this change it works:

$ git diff gather-image-files
diff --git a/gather-image-files b/gather-image-files
index 832bf80..39fe252 100755
--- a/gather-image-files
+++ b/gather-image-files
@@ -13,8 +13,8 @@ echo "Making source tarballs"
 mkdir -p ../www/software/source/files
 for p in mesh-extender-builder serval-dna batphone smac flash-rfd900 openwrt-packages app_servaldna s
 do
-   echo git clone g...@github.com:servalproject/${p}.git
-   git clone g...@github.com:servalproject/${p}.git
    echo tar zcf ../www/software/source/files/${p}.tgz
    tar zcf ../www/software/source/files/${p}.tgz ${p}
    rm -fr ${p}

I assume that you need to have ssh access to your git to be able to clone using the original script.

I will report back on any other findings i do.

/Claes

Paul Gardner-Stephen

unread,
Oct 2, 2014, 5:43:46 PM10/2/14
to serval-proje...@googlegroups.com
Hello,

Thanks. I have just fixed this, let me know how you go.

Paul.

--
You received this message because you are subscribed to the Google Groups "Serval Project Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.
To post to this group, send email to serval-proje...@googlegroups.com.
Visit this group at http://groups.google.com/group/serval-project-developers.
For more options, visit https://groups.google.com/d/optout.

Claes Giljegard

unread,
Oct 7, 2014, 2:51:51 PM10/7/14
to serval-proje...@googlegroups.com
Hi,

Flashing of the router and creation of usbmem works.
There is  a problem with the serval adaptations of openwrt. It looks like it is still an openwrt router without serval functionality.

Something is missing... so I start looking around...
I see that there is an upgrade dir created and it is tared to serval.up
It seems that this is supposed to be copied to the /dos partition on the usbmem but is not.
...and i find some code related to the wps button being presseed in /etc/hotplug.d/button/buttons that will run /serval/upgrade /dos/serval.up but /serval/upgrade is missing.
I found a scrip image-files/mesh-extender/upgrade. If i put it in /serval and run /serval/upgrade /dos/serval.up then it starts to upgrade and serval is started but no wifi.
Looking at /etc/config/wireless it seems to be disabled and openwrt default:

root@OpenWrt:~# cat /etc/config/wireless 
config wifi-device  radio0
option type     mac80211
option channel  11
option macaddr e8:94:f6:ba:b2:5c
option hwmode 11ng
option htmode HT20
list ht_capab SHORT-GI-20
list ht_capab SHORT-GI-40
list ht_capab RX-STBC1
list ht_capab DSSS_CCK-40
# REMOVE THIS LINE TO ENABLE WIFI:
option disabled 1

config wifi-iface
option device   radio0
option network  lan
option mode     ap
option ssid     OpenWrt
option encryption none

root@OpenWrt:~#

Something is missing... but what?
And the /dos/noroot file is not recreated on reboot. 

/Claes
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsub...@googlegroups.com.

Paul Gardner-Stephen

unread,
Oct 7, 2014, 4:09:59 PM10/7/14
to serval-proje...@googlegroups.com
Hello,

On Wed, Oct 8, 2014 at 5:21 AM, Claes Giljegard <cl...@giljegard.com> wrote:
Hi,

Flashing of the router and creation of usbmem works.
There is  a problem with the serval adaptations of openwrt. It looks like it is still an openwrt router without serval functionality.

Something is missing... so I start looking around...
I see that there is an upgrade dir created and it is tared to serval.up
It seems that this is supposed to be copied to the /dos partition on the usbmem but is not.
...and i find some code related to the wps button being presseed in /etc/hotplug.d/button/buttons that will run /serval/upgrade /dos/serval.up but /serval/upgrade is missing.

This file is created for upgrading an existing Mesh Extender.  It shouldn't be required when installing the first time.

It sounds like the populate-memory-stick isn't being run or is failing if you aren't ending up with /serval already pre-populated with at least the upgrade script.
 
I found a scrip image-files/mesh-extender/upgrade. If i put it in /serval and run /serval/upgrade /dos/serval.up then it starts to upgrade and serval is started but no wifi.
Looking at /etc/config/wireless it seems to be disabled and openwrt default:

root@OpenWrt:~# cat /etc/config/wireless 
config wifi-device  radio0
option type     mac80211
option channel  11
option macaddr e8:94:f6:ba:b2:5c
option hwmode 11ng
option htmode HT20
list ht_capab SHORT-GI-20
list ht_capab SHORT-GI-40
list ht_capab RX-STBC1
list ht_capab DSSS_CCK-40
# REMOVE THIS LINE TO ENABLE WIFI:
option disabled 1

config wifi-iface
option device   radio0
option network  lan
option mode     ap
option ssid     OpenWrt
option encryption none

root@OpenWrt:~#

Hmm... This is strange, because I have used this to build the mesh extenders before and they worked, but looking now, there is no wireless file in image-files/etc/config/ which should be required.  Maybe there was some hangover file from a previous installation that allowed it to work.

Looking at the old mesh extender build process, it looks like the wireless file needs to be generated dynamically for each unit to get the mac address right.  I'll create and /etc/rc.d/S file that does this and commit it.
 
Something is missing... but what?
And the /dos/noroot file is not recreated on reboot. 

This should be created by the modified S50dropbear file.  See if /etc/rc.d/S50dropbear contains the line "touch /dos/noroot" and let me know what you find.  

I intend to do some more work on getting this firmware finally finished this week, and will be able to commit some time to ironing these wrinkles out, probably tomorrow.

Thanks again for providing the clear feedback.

Paul.


To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 7, 2014, 4:26:17 PM10/7/14
to serval-proje...@googlegroups.com
Hi,

The S50dropbear seems to not be modified.

root@OpenWrt:~# grep noroot /etc/rc.d/S50dropbear
root@OpenWrt:~#

The /serval is populated from the beginning but is does not seem to be used or activated.

I don't have any radio attached to the serial port of the MR3020, is that a problem?

/Claes
Hello,

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsubsc...@googlegroups.com.
To post to this group, send email to serval-proje...@googlegroups.com.
Visit this group at http://groups.google.com/group/serval-project-developers.
For more options, visit https://groups.google.com/d/optout.

Paul Gardner-Stephen

unread,
Oct 7, 2014, 5:39:18 PM10/7/14
to serval-proje...@googlegroups.com
Hello,

On Wed, Oct 8, 2014 at 6:56 AM, Claes Giljegard <cl...@giljegard.com> wrote:
Hi,

The S50dropbear seems to not be modified.

Did you run make_image first of all?  If so, can you try using the filesystem tools to take the image apart and confirm if S50dropbear is modified in there?  This will allow investigation without having to reflash the router all the time.
 
root@OpenWrt:~# grep noroot /etc/rc.d/S50dropbear
root@OpenWrt:~#

The /serval is populated from the beginning but is does not seem to be used or activated.

This probably suggests that the firmware image is missing some important files.
 
I don't have any radio attached to the serial port of the MR3020, is that a problem?

It shouldn't be, provided you are using the latest commits.

Paul.
 
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 8, 2014, 3:49:52 PM10/8/14
to serval-proje...@googlegroups.com
Hi,

I am using the latest commits and I redid the steps

1. make_image
2. gather-image-files
3. reflash-mesh-extender
4. populate-memory-stick

/dos/noroot is still there and i can ssh into the router. /serval is populated.
I was wrong about serval not being started... I see now that it is. Sorry about that.

claes@dellUbuntu:~/serval/mesh-extender-builder$ ssh ro...@192.168.1.1


BusyBox v1.19.4 (2013-03-14 11:28:31 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.

Serval Project Mesh Extender Firmware 0.01
Based on OpenWRT 12.09.

EXPERIMENTAL SOFTWARE.
root@OpenWrt:~# ls -l /dos
-rwxr-xr-x    1 root     root           146 Oct  8  2014 noroot
root@OpenWrt:~# ls -l /serval
drwxr-xr-x    2 1000     1000          4096 Oct  8  2014 bin
-rw-r--r--    1 1000     1000             4 Mar 23  2013 debian-binary
drwxr-xr-x    3 1000     1000          4096 Mar 23  2013 etc
drwxr-xr-x    4 1000     1000          4096 Oct  8  2014 lib
drwxr-xr-x    3 1000     1000          4096 Mar 23  2013 libexec
drwx------    2 root     root         16384 Oct  8  2014 lost+found
drwxr-xr-x    2 1000     1000          4096 Mar 23  2013 sbin
-rwxrwxr-x    1 1000     1000       2041776 Oct  8  2014 servald
drwxr-xr-x    4 1000     1000          4096 Mar 23  2013 share
drwxrwxr-x    4 1000     1000          4096 Sep  5  2014 www
root@OpenWrt:~# grep noroot /etc/rc.d/S50dropbear 
root@OpenWrt:~# ps
  PID USER       VSZ STAT COMMAND
    1 root      1496 S    init
    2 root         0 SW   [kthreadd]
    3 root         0 SW   [ksoftirqd/0]
    4 root         0 SW   [kworker/0:0]
    5 root         0 SW   [kworker/u:0]
    6 root         0 SW<  [khelper]
    7 root         0 SW   [kworker/u:1]
   63 root         0 SW   [sync_supers]
   65 root         0 SW   [bdi-default]
   67 root         0 SW<  [kblockd]
   96 root         0 SW   [kswapd0]
  144 root         0 SW   [fsnotify_mark]
  173 root         0 SW<  [ath79-spi]
  184 root         0 SW   [mtdblock0]
  189 root         0 SW   [mtdblock1]
  194 root         0 SW   [mtdblock2]
  199 root         0 SW   [mtdblock3]
  204 root         0 SW   [mtdblock4]
  209 root         0 SW   [mtdblock5]
  250 root         0 SW   [kworker/0:1]
  444 root         0 SWN  [jffs2_gcd_mtd3]
  461 root      1536 S    {rcS} /bin/sh /etc/init.d/rcS S boot
  463 root      1496 R    logger -s -p 6 -t sysinit
  493 root         0 SW<  [cfg80211]
  502 root         0 SW   [khubd]
  558 root         0 SW   [scsi_eh_0]
  559 root         0 SW   [usb-storage]
  590 root      1508 S    /sbin/syslogd -C16
  592 root      1488 S    /sbin/klogd
  594 root       864 S    /sbin/hotplug2 --override --persistent --set-rules-file /etc/hotplug2.rules --set-coldplug-cmd /sbin/udev
  600 root       868 S    /sbin/ubusd
  604 root      1520 S    /sbin/netifd
  754 root      1500 S    /sbin/watchdog -t 5 /dev/watchdog
 1019 root         0 SW   [jbd2/sda2-8]
 1020 root         0 SW<  [ext4-dio-unwrit]
 1022 root         0 SW   [jbd2/sda3-8]
 1023 root         0 SW<  [ext4-dio-unwrit]
 1024 root      1496 S    {runservald} /bin/sh /etc/serval/runservald
 1081 root      1152 S    /usr/sbin/dropbear -P /var/run/dropbear.1.pid -p 22
 1195 root         0 SW   [flush-8:0]
 1315 root      1496 R    ps
 1403 nobody     944 S    dnsmasq -i br-lan -a 192.168.1.1 --except-interface=lo --bind-interfaces --address=/#/192.168.1.1 -h -b -
 1434 root      1500 S    /usr/sbin/ntpd -n -p 0.openwrt.pool.ntp.org -p 1.openwrt.pool.ntp.org -p 2.openwrt.pool.ntp.org -p 3.open
31203 root      1220 R    /usr/sbin/dropbear -P /var/run/dropbear.1.pid -p 22
31387 root      1504 S    -ash
root@OpenWrt:~#

In the image-files in the buildcatalogue I find a modified S50dropbear

claes@dellUbuntu:~/serval/mesh-extender-builder$ grep noroot image-files/etc/rc.d/S50dropbear 
# Only run dropbear if there does not exist a file /dos/noroot
# If starting, create the file, so that removing noroot only allows
        [ -e /dos/noroot ] && return 1
        touch /dos/noroot
        echo "Remove this file to enable SSH login to the mesh extender as root:root." >/dos/noroot
        echo "This file is recreated on each reboot, so is effective for one boot only." >>/dos/noroot
claes@dellUbuntu:~/serval/mesh-extender-builder$

In the log of make_image i see
--
Copying extra files
Removing symlink /home/claes/serval/mesh-extender-builder/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486/build_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/./etc/fstab
cp -fpR ../image-files/* /home/claes/serval/mesh-extender-builder/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486/build_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/
make[2]: Leaving directory `/home/claes/serval/mesh-extender-builder/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486'
make package_postinst
make[2]: Entering directory `/home/claes/serval/mesh-extender-builder/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486'
--

looking in 
--
$ ls -l /home/claes/serval/mesh-extender-builder/OpenWrt-ImageBuilder-ar71xx_generic-for-linux-i486/build_dir/target-mips_r2_uClibc-0.9.33.2/root-ar71xx/./etc/rc.d/
total 12
lrwxrwxrwx 1 claes claes  18 Oct  8 18:09 K50dropbear -> ../init.d/dropbear
lrwxrwxrwx 1 claes claes  17 Oct  8 18:09 K90network -> ../init.d/network
lrwxrwxrwx 1 claes claes  14 Oct  8 18:09 K98boot -> ../init.d/boot
lrwxrwxrwx 1 claes claes  16 Oct  8 18:09 K99umount -> ../init.d/umount
lrwxrwxrwx 1 claes claes  19 Oct  8 18:09 S05defconfig -> ../init.d/defconfig
lrwxrwxrwx 1 claes claes  14 Oct  8 18:09 S10boot -> ../init.d/boot
lrwxrwxrwx 1 claes claes  14 Oct  8 18:09 S11ubus -> ../init.d/ubus
lrwxrwxrwx 1 claes claes  17 Oct  8 18:09 S20network -> ../init.d/network
lrwxrwxrwx 1 claes claes  13 Oct  8 18:09 S39usb -> ../init.d/usb
lrwxrwxrwx 1 claes claes  18 Oct  8 18:09 S45firewall -> ../init.d/firewall
-rwxrwxr-x 1 claes claes 136 Sep  5 18:47 S47mountstuff
-rwxrwxr-x 1 claes claes 605 Sep  5 18:47 S49servald
lrwxrwxrwx 1 claes claes  14 Oct  8 18:09 S50cron -> ../init.d/cron
lrwxrwxrwx 1 claes claes  18 Oct  8 18:09 S50dropbear -> ../init.d/dropbear
lrwxrwxrwx 1 claes claes  16 Oct  8 18:09 S50telnet -> ../init.d/telnet
lrwxrwxrwx 1 claes claes  17 Oct  8 18:09 S60dnsmasq -> ../init.d/dnsmasq
-rwxrwxr-x 1 claes claes 967 Sep  5 18:47 S94captiveportal
lrwxrwxrwx 1 claes claes  14 Oct  8 18:09 S95done -> ../init.d/done
lrwxrwxrwx 1 claes claes  13 Oct  8 18:09 S96led -> ../init.d/led
lrwxrwxrwx 1 claes claes  18 Oct  8 18:09 S97watchdog -> ../init.d/watchdog
lrwxrwxrwx 1 claes claes  17 Oct  8 18:09 S98sysntpd -> ../init.d/sysntpd
lrwxrwxrwx 1 claes claes  16 Oct  8 18:09 S99sysctl -> ../init.d/sysctl
--
we can see that S50dropbear is a link pointing to a nonexisting file.
I think the link should be removed in the same way as fstab before the copy is done.

I have not been able to extract the contents of openwrt-ar71xx-generic-tl-mr3020-v1-squashfs-factory.bin...
How is that done?

/Claes

Paul Gardner-Stephen

unread,
Oct 8, 2014, 4:45:14 PM10/8/14
to serval-proje...@googlegroups.com
Hello,

Thanks for the update. 
The S50dropbear file problem should probably be fixed by putting the file in /etc/init.d/.  I have just made a commit to do exactly that.

I'll take a better look at all this when I get into the lab today. 

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 9, 2014, 4:10:05 PM10/9/14
to serval-proje...@googlegroups.com
Hi,

Thanks. Now the noroot file works as expected.

I tried to copy a wireless from the old mesh-extender.
It did not work.
I get
root@OpenWrt:/etc/init.d# ./network start
PHY for wifi device radio0 not found
'radio1' is disabled

I'll try to debug that during the weekend.

/Claes

Paul Gardner-Stephen

unread,
Oct 9, 2014, 4:41:08 PM10/9/14
to serval-proje...@googlegroups.com
Hello,

Ah, glad to hear noroot is working now.  The wireless file needs to have the correct mac address in it for it to work.  I hope to attack this today.  Else look at the hold mesh-extender repository and the 2.* file there that probes the mesh extender for its mac address and generates the wireless file automatically from that.  My plan is to pull that logic out into an /etc/rc.d file on the image, and have it generate the wireless file automatically on first boot.  It may not happen today, however, as I have a mountain of paperwork to attack.

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 10, 2014, 1:38:05 AM10/10/14
to serval-proje...@googlegroups.com
Hi,
No need to hurry. I am just playing with it.
/Claes

Claes Giljegard

unread,
Oct 11, 2014, 4:03:09 PM10/11/14
to serval-proje...@googlegroups.com
Hi,

I think I have something that may work now.

These two files should go into image-files

root@OpenWrt:~# cat /etc/config/wireless.template 

config wifi-device radio0
      option type       mac80211
      option channel    11
      option hwmode     11ng
      option htmode HT20
option macaddr MACADDRESS_HERE
        option path 'platform/ar933x_wmac'
  list ht_capab SHORT-GI-20
  list ht_capab SHORT-GI-40
  list ht_capab RX-STBC1
        list ht_capab DSSS_CCK-40
                                                                                     
config wifi-iface mesh                                
        option device   radio0
        option ssid     mesh.servalproject.org        
        option network  mesh                          
        option mode     adhoc
        option bssid    02:ca:ff:dd:ca:ce             
        option bgscan   0                             
                                                                                                                                                                                           
config wifi-iface public                      
        option device     radio0
        option network    public              
        option mode       ap                  
        option isolate    0                   
        option ssid       public.servalproject.org
        option hidden     0                       
        option encryption none

root@OpenWrt:~# cat /etc/rc.d/S15wireless 
#!/bin/sh
sed 's|MACADDRESS_HERE|'`cat /sys/class/ieee80211/phy0/macaddress`'|' < /etc/config/wireless.template > /etc/config/wireless
root@OpenWrt:~#

I took the wireless from the old mesh-extender files.
The router will create an ap now but my phone does not want to connect to it...

/Claes

Claes Giljegard

unread,
Oct 11, 2014, 4:30:21 PM10/11/14
to serval-proje...@googlegroups.com
Hi,

Something is not correct with the serval config file...

root@OpenWrt:~# /serval/servald status
INFO: Local date/time: 1970-01-01 00:15:31 +0000
INFO: Serval DNA version: UNKNOWN-VERSION
WARN: conf_schema.h:430:cf_opt_config_rhizome()  /etc/serval/serval.conf:20: configuration option "rhizome.external_blobs" not supported
WARN: 00:15:31.524 conf.c:233:reload_and_parse()  config file /etc/serval/serval.conf loaded despite defects -- contains unsupported element
pidfile:/var/run/serval/servald.pid
status:stopped
root@OpenWrt:~#

/Claes

Claes Giljegard

unread,
Oct 13, 2014, 1:08:43 AM10/13/14
to serval-proje...@googlegroups.com
Hi,

I think the network file needs modification too.

/Claes

Paul Gardner-Stephen

unread,
Oct 13, 2014, 1:46:06 AM10/13/14
to serval-proje...@googlegroups.com
Hello,

Thanks for your work on this.  I'll pull the wireless scripts in and take a look at the network file.  You are right that the serval.conf file needs updating.  I'll chat with the guys here about that.

Paul.

--

Paul Gardner-Stephen

unread,
Oct 13, 2014, 2:22:55 AM10/13/14
to serval-proje...@googlegroups.com
Hello,

serval.conf should be fine now.

Let me know how you go.

Meanwhile, I'll try to take a look at the network configuration file.

Paul.

Claes Giljegard

unread,
Oct 13, 2014, 4:01:07 PM10/13/14
to serval-proje...@googlegroups.com
Hi,

Wireless and serval.conf is ok now.
/serval/servald status gives errors due to missing directories.
If i add two lines to /etc/rc.d/S49servald they go away.
--
  # Start servald
  export SERVALINSTANCE_PATH=/etc/serval
  mkdir -p $SERVALINSTANCE_PATH
  mkdir -p /var/run/serval
  mkdir -p /serval-var/log
          
  mount -a
--
But still servald status is stopped.
Maybe that will sort itself out when network is fixed.

/Claes

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsub...@googlegroups.com.

Paul Gardner-Stephen

unread,
Oct 13, 2014, 5:21:28 PM10/13/14
to serval-proje...@googlegroups.com
Hello,

We need to change the SERVALINSTANCE_PATH to point to somewhere on /serval-var so that it doesn't fill or wear out the internal flash.

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Paul Gardner-Stephen

unread,
Oct 18, 2014, 12:08:14 PM10/18/14
to serval-proje...@googlegroups.com
Hello,

I have added these lines, and also a first cut at creating the /etc/config/network file.
I don't have a mesh extender here to test on, so if you would like to test it that would be great. Otherwise I will try it when I get into the lab on Monday.

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 19, 2014, 3:37:45 PM10/19/14
to serval-proje...@googlegroups.com
Hi,

Great!
I pulled your changes, made a new build and installed on the router and populated the usbstick.
It is possible to to connect to public.servalproject.org.
I notice that serval is stopped and i manage to start it.
--
root@Serval-MeshExtender-0:~# /serval/servald status
pidfile:/var/run/serval/servald.pid
status:stopped
root@Serval-MeshExtender-0:~# /serval/servald start
INFO: 00:02:44.783 Local date/time: 1970-01-01 00:02:44 +0000
INFO: 00:02:44.783 Serval DNA version: UNKNOWN-VERSION
INFO: 00:02:44.783 instance.c:211:create_serval_instance_dir()  mkdir `/var/cache` (mode 0700)
INFO: 00:02:44.798 instance.c:211:create_serval_instance_dir()  mkdir `/var/cache/serval` (mode 0700)
INFO: 00:02:44.799 instance.c:219:create_serval_instance_dir()  mkdir `/var/log/serval` (mode 0700)
INFO: 00:02:44.800 instance.c:221:create_serval_instance_dir()  mkdir `/tmp/serval` (mode 0700)
INFO: 00:02:44.800 instance.c:223:create_serval_instance_dir()  mkdir `/var/run/serval/proc` (mode 0755)
INFO: 00:02:44.801 commandline.c:858:app_server_start()  Starting background server without exec
pidfile:/var/run/serval/servald.pid
pid:1493
http_port:4111
root@Serval-MeshExtender-0:~# /serval/servald status
pidfile:/var/run/serval/servald.pid
status:running
pid:1493
http_port:4111
root@Serval-MeshExtender-0:~#
--
Now it is possible to send text messages between two phones running serval using  the public ap.
I also managed to share the serval apk
One of my phones is a htc dream and it is rooted. Serval can do mesh on it but it will not connect to the mr3020.
I don't know why yet.

In the status printout above there is something about unknown DNA version.
What is that used for?
and I don't have a long range radio attached. I hope that does not disturb servald.

/Claes
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-developers+unsubsc...@googlegroups.com.
To post to this group, send email to serval-proje...@googlegroups.com.
Visit this group at http://groups.google.com/group/serval-project-developers.
For more options, visit https://groups.google.com/d/optout.

Paul Gardner-Stephen

unread,
Oct 19, 2014, 4:50:38 PM10/19/14
to serval-proje...@googlegroups.com
Hello,

Glad that these changes have worked.  Can you confirm that the network file contains what we expect?

The "UNKNOWN VERSION" thing is because I built the servald outside of a git repository, and so the normal mechanism for including the git commmit id in the binary doesn't work.

Nice to know that someone else still has some HTC Dreams (we have a few here in the lab as well). It is quite odd that they won't connect to the MR3020 as a Wi-Fi client.

I'll look at why servald isn't starting on boot when I get into the lab.  It shouldn't matter that you don't have an RFD900 or similar attached, but do note that there will be a few seconds delay as the RFD900 flashing script works out that there is no RFD900 attached.  It is possible that the script waits a long time, which is causing the symptom.  I'll look into this.

After fixing this, I think we must just about be at the point of being able to declare the new firmware working, unless you are aware of any other show-stoppers.  Again, it has been very helpful to have someone else replicating this as we go along to confirm that it can be done.

Paul.


To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 20, 2014, 3:24:29 PM10/20/14
to serval-proje...@googlegroups.com
Hi,

My HTC dream connects ok if i choose wi-fi and select the public ap. If i choose 'ad hoc mesh' it says 'no peers' and it will not send text messages to the other phone. How do i tell which ap or channel it is using? I assume it should be the mesh ap...

I also noticed that 
mkdir -p /serval-var/log
in S49servald is not creating the log dir.
Can it be that it is created but then the partition from the usbmem is mounted on top of it and makes it disapear?

Is servald creating any logs?
I have not been able to find any...

My other phone is a samsung galaxy nexus which does not support meshing. Will two mr3020 mesh over 2.4Ghz or only over 900Mhz?

I have verified speech, text and sharing the serval.apk from nexus to dream both running serval_0.92-RC5 over the public ap of the mr3020.
If you have verified the meshing functionality I don't know of any other stopping issues.

I have been following serval for a long time (the log on the dream says Dec 2011) and I am happy to be able to help.

/Claes

Paul Gardner-Stephen

unread,
Oct 21, 2014, 7:04:37 AM10/21/14
to serval-proje...@googlegroups.com
Hello,

On Tue, Oct 21, 2014 at 5:54 AM, Claes Giljegard <cl...@giljegard.com> wrote:
Hi,

My HTC dream connects ok if i choose wi-fi and select the public ap. If i choose 'ad hoc mesh' it says 'no peers' and it will not send text messages to the other phone. How do i tell which ap or channel it is using? I assume it should be the mesh ap...

To be honest, we haven't test adhoc mode with the phones and mesh extenders for a while, as this is not expected to be the most common use case. Let's get the mesh extender firmware settled for AP mode, and then come back and revisit this.  
 
I also noticed that 
mkdir -p /serval-var/log
in S49servald is not creating the log dir.
Can it be that it is created but then the partition from the usbmem is mounted on top of it and makes it disapear?

This shouldn't be a problem, as S47mountstuff should finish first.
 

Is servald creating any logs?
I have not been able to find any...

We have logging disabled by default to save wear on the flash storage.
 
My other phone is a samsung galaxy nexus which does not support meshing. Will two mr3020 mesh over 2.4Ghz or only over 900Mhz?

The mr3020s will mesh over both 2.4GHz and 900MHz, assuming you have an RFD900 for the 900MHz link.
 
I have verified speech, text and sharing the serval.apk from nexus to dream both running serval_0.92-RC5 over the public ap of the mr3020.
If you have verified the meshing functionality I don't know of any other stopping issues.

Super.
 
I have been following serval for a long time (the log on the dream says Dec 2011) and I am happy to be able to help.

:) Thanks -- the help of volunteers like yourself is tremendous.

I finally have a chance to try the changes out on a mesh extender here, so I plan to test the changes we have made here, and try to work out why servald doesn't start, or alternatively confirm that it does on the unit here.  I am testing on a unit with no RFD900, so it should be a close match to your test environment.

Paul.
 
To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 21, 2014, 4:15:29 PM10/21/14
to serval-proje...@googlegroups.com
Hi,

Today I flashed my other mr3020 to see if I could get them to connect.
I started serval manually on both of them.
I do scan and peer count but it keeps returning 0 peers.
I think there may be something wrong with the mesh part of the wireless config file.

Is it possible to enable trace on servald or is it built into the binary?

/Claes

Paul Gardner-Stephen

unread,
Oct 21, 2014, 5:22:35 PM10/21/14
to serval-proje...@googlegroups.com
Hello,

Ok, I'll take a look when I come into the lab.

A simple test would be from one of the mesh extenders to try to ping the other, or similarly to telnet to port 4110 on the other. servald runs a HTTP server on that port.

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.

Claes Giljegard

unread,
Oct 22, 2014, 2:48:21 PM10/22/14
to serval-proje...@googlegroups.com
Hi,

Ok, the mesh is working. I can ping and ssh from one to the other.

/Claes

Paul Gardner-Stephen

unread,
Oct 22, 2014, 4:36:40 PM10/22/14
to serval-proje...@googlegroups.com
Hello,

Ok, so to clarify, it is the servald's not talking between the devices, whereas the actual ad hoc wifi seems to be fine.  Yesterday got somewhat hijacked, but I did make some small progress and will aim for more today.

Paul.

To unsubscribe from this group and stop receiving emails from it, send an email to serval-project-dev...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages