ROBIN -  Open Source Mesh Network Forum Index ROBIN - Open Source Mesh Network
users community forum
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

for developers

 
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> OrangeMesh Dashboard
View previous topic :: View next topic  
Author Message
Ads






Posted: Sat Jun 24, 2017 12:48 pm    Post subject: Ads

Back to top
Antonio (isleman)
Site Admin
Site Admin


Joined: 10 Feb 2008
Posts: 2323
Location: Toscana, Italy

PostPosted: Wed Jun 10, 2009 3:01 pm    Post subject: for developers Reply with quote

Code:

ALL the parameters of robin can be changed by replies and right messages.
Obviously, all the available settings cannot be entered at dashboard, but
you can send them inside the replys in a transparent way.
For example: wifi default channel, changing the way olsrd floods the mesh
backbone, using static ARP entries, subnet of AP, subnet used by mesh,
madwifi parameters... and so on.
YOU HAVE TO KNOW WHAT ARE YOU DOING 'cos you risk to break your network!
Email me if you want more clarifications (tony.anselmi@gmail.com)


      -= r2XXX BRANCH - DASHBOARD NEW FEATURES =-


ability to set lan-block on per-AP basis
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SECTION:  #@#config iprules
OPTION:   filter.LAN_BLOCK  0|1 (default 0) needed directive to preserve old versions
OPTION:   filter.LAN_BLOCK2 0|1|101|102 (default 0)

  0 = no lan block
  1 = deny both APs traffic directed to LAN IPs
101 = deny only AP1 traffic directed to LAN IPs (AP2 traffic is allowed)
102 = deny only AP2 traffic directed to LAN IPs (AP1 traffic is allowed

dashboard has to send boths the two directives:
a) versions equal or lower than r2168 operate only with the directive
"filter.LAN_BLOCK" and cannot discriminate Ap1 and AP2

b) versions greather than r2168 will operate only with the new directive
"filter.LAN_BLOCK2"

e.g.

no lan-block:
   #@#config iprules
   filter.LAN_BLOCK  0
   filter.LAN_BLOCK2 0

full lan-block:
   #@#config iprules
   filter.LAN_BLOCK  1
   filter.LAN_BLOCK2 1


lower half block (deny AP1 and allow AP2)
   #@#config iprules
   filter.LAN_BLOCK  1
   filter.LAN_BLOCK2 101

upper half block (deny AP2 and allow AP1)
   #@#config iprules
   filter.LAN_BLOCK  1
   filter.LAN_BLOCK2 102


IEEE 802.11e WMM
^^^^^^^^^^^^^^^^
SECTION:  #@#config 80211e
OPTION:   general.enable <VALUE> (default 5)

0=disable EDCA parameter set
1=enable EDCA parameter set

e.g.
#@#config 80211e
general.enable 1


support to zero-lenght replies
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If nothing is changed then the dashboard can send a zero-lenght reply to
the nodes in order to save bandwidth.
When one node needs a full reply from the dashboard then it will set the
flag RR (Reply Request) in the checkin string, eg:
RR=1
otherwise it always send RR=0


ability to set the checkin frequency
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Nodes checkin at every 5 minutes, now you can change the chekin frequency
by sending the nodes the appropriate message inside the reply:

SECTION:  #@#config management
OPTION:   enable.update_rate 0|1 (default 0)
VALUE:    checkin frequency in minutes

eg, the message:

#@#config management
enable.update_rate 15

will force nodes to checkin every 15 minutes.

If you don't send this option then nodes will checkin using the default
value (every 5 minutes)


ability to set the upgrade window   
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You can define a upgrade time window where allow nodes to upgrade by sending
the nodes the appropriate message inside the reply:

SECTION:     #@#config management
OPTION:      enable.upgrade_f <VALUE FROM> (default 1)
OPTION:      enable.upgrade_t <VALUE TO> (default 23)
VALUE FROM:      start upgrade-window in hours
VALUE to:        end upgrade-window in hours

note:
<VALUE FROM> and <VALUE TO> are in range 0-23
dashboard has to validate the consistency of the interval 'cos nodes
don't check the above values

eg, the message:

#@#config management
enable.upgrade_f 2
enable.upgrade_f 6

will force the nodes to check for upgrades from 02AM to 06AM

If you don't send this option then nodes will upgrade using the default
upgrade-window (1-23)


ability to activate the shaper (experimental)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"shaper" allow priorization of video/voice traffic. You can enable/disable
the shaper by sending the appropriate message inside the reply:

SECTION:  #@#config management
OPTION:   enable.shaper 0|1|2 (default 0)

0=disable shaper (default)
1=enable openwrt qos-scripts
2=enable wondershaper


delayed boot (satellite uplink)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
SECTION:    #@#config management
OPTION:     enable.wake_slowly <seconds> (default 0)

#@#config management
enable.wake_slowly 200


ability to logging to a remote log server (experimental)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You can log clients activity to a remote log server by enabling the logging
option sending the appropriate message inside the reply:

SECTION:   #@#config iprules
OPTION:   filter.enable_log 1|0 (default 0)
OPTION:   filter.log_server <remote log server IP>

#@#config iprules
filter.enable_log 1
filter.log_server aaa.bbb.ccc.ddd


scheduled reboot
^^^^^^^^^^^^^^^^
SECTION:    #@#config management
OPTION:     enable.force_reboot "COMMAND_STRING" (default: never)

COMMAND_STRING may contain:

a) the sigle word "never"
means never reboot

b) two-fileds separated by "@" character
and has the following format:

<frequency of reboot>@<hour of the day>

the field <frequency> may be:
w   weekly
m   monthly
24     once every 24h
48   once every 48h

the field <hour> is a number beteween 0 and 23

Examples:

#@#config management
enable.force_reboot w@01    <- reboot every sunday at 01 AM

#@#config management
enable.force_reboot 24@12 <- reboot every day at noon


strict-mesh (block alien nodes)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
prevent meshing with nodes which don't belong to the same
netowrk name of the node.
requires that dashboard sends the list of the registered nodes

SECTION:    #@#config management
OPTION:     enable.strict_mesh 0|1 (default 0)

0=disable strict-mesh
1=enable strict-mesh

tips & hints
------------
Genaral names such as SSIDs, node name,... must be sent translating "space"
as "*". Nodes will perform the opposite translation.
For example, of you want send the SSID:
'my humble net'
you must send that string as:
'my*humble*net'

Back to top
View user's profile Send private message Send e-mail Visit poster's website
shasan
Moderator
Moderator


Joined: 16 Feb 2008
Posts: 178
Location: Chapel Hill, NC

PostPosted: Thu Jun 11, 2009 4:55 pm    Post subject: Reply with quote

Thanks Antonio, this is an immense help.

_________________

Only registered users can see links on this forum!
Register or Login on forum!


unc-chapel hill, class of 2010
Back to top
View user's profile Send private message Send e-mail Visit poster's website
foxtroop11
Service Provider
Service Provider


Joined: 22 Mar 2009
Posts: 1168
Location: Ansbach, Germany and sometimes the States

PostPosted: Fri Jun 12, 2009 6:50 am    Post subject: Reply with quote

Quote:
ability to logging to a remote log server (experimental)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You can log clients activity to a remote log server by enabling the logging
option sending the appropriate message inside the reply:

SECTION: #@#config iprules
OPTION: filter.enable_log 1|0 (default 0)
OPTION: filter.log_server <remote log server IP>

#@#config iprules
filter.enable_log 1
filter.log_server aaa.bbb.ccc.ddd


Any extra info on this? Is this only logging the info on the node or when it says "client" does that mean the actual users on that node? I would like to setup a test of this but not sure what format or procedure needs to be done on the server.

Would it be something like this?

Only registered users can see links on this forum!
Register or Login on forum!

Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    ROBIN - Open Source Mesh Network Forum Index -> OrangeMesh Dashboard All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
c d
e



Powered by phpBB © 2001, 2005 phpBB Group

Abuse - Report Abuse - TOS & Privacy.
Powered by forumup.it free forum, create your free forum! Created by Hyarbor & Qooqoa
Confirmed

Page generation time: 0.239