I'm not sure if i'm testing orangemesh (no google) or DFE.
See my DFE config below, it works.
There are a few bugs and i have some questions about DFE
With DFE I assumed that the "ROBIN gateway node" was going to be a master server and the settings we going to be pushed out the all the other nodes? On my test network i only have 2 nodes which i edited both nodes DFE config files. This would be a problem on a big network.
I had my orangemesh network working then switched back to the open-mesh dashboard. One node get stuck on batman and the other on OSLR. I tryed everything but short of a reflash i gave up. I went back to orangemesh and both nodes went back to batman.
Orangemesh network is working fine then you unplug the DSL router plug. The network keeps working, you can transfer files between computers. But the orangemesh status stops working. I left it for 15 minutes and it wouldn't update. I plugged the DSL router back in and waited 5 minutes and it started working again.
Good work guys. so close now
|Only registered users can see links on this forum!|
Register or Login on forum!
# /etc/DFE Dashboard Front End
# ROBIN - 2007 by Antonio Anselmi <a.anselmi-at-oltrelinux-dot-com>
# rename as /etc/DFE if you DO NOT want run the current settings as stored in /etc/config/general
# /etc/DFE (if present) is parsed by /etc/init.d/nodeclean and its values
# are exported to /etc/config/general.
# You have to know what are you doing
# name of the used dashboard
# default: DASHBOARD_IN_USE=open-mesh
# FQN or IP address of the server hosting the dashboard server
# default: DASHBOARD_URL=checkin.open-mesh.com
# 1 = dashboard resides on the wired LAN segment
# in this case DASHBOARD_URL must be the LAN IP address of the dashboard (!)
# 0 = dashboard is outside
# default: DASHBOARD_ON_LAN=0
# FQN or IP address of the server hosting the version file and the
# related upgrade tarball
# default for test version: FIRMWARES_URL=www.open-mesh.com/firmware/mr3201a/test/
# default for beta version: FIRMWARES_URL=www.open-mesh.com/firmware/mr3201a/
# The final "/" is mandatory
# FQN or IP address of the server hosting the custom.sh script
# default: CUSTOM_SH_URL=www.open-mesh.com/firmware/mr3201a/
# have fun