robin r2 branch

[Antonio]

Hi all,

I want notice you about r2 branch svn development which - at present -
is mostly based on APs node functions.

Working with mesh parameters in /etc/config/mesh it will be possible
to have three possible modes for gateway nodes:

*normal gateway*
with four sub-choices:
- one AP open and a second WPA-PSK protected AP (per default)
- two APs both WPA-PSK protected (different keys)
- only one open AP
- only one WPA-PSK protected AP
(running only 1 WPA-PSK AP we get much more than 3MB free RAM on a
16MB board)

*pure gateway*
with no APs

(more than 4 free RAM on a 16MB board)

*air gateway* (experimental, not yet in svn)
gets Internet connection by associating with an external "master" AP
(no wired to upstream DSL router!) air gateway has no APs but a
STA_VAP on top of ath1

The choices:
- one AP open and a second WPA-PSK protected AP (per default)
- two APs both WPA-PSK protected (different keys)
- only one open AP
- only one WPA-PSK protected AP
are also possible for repeater nodes and not only for gateway nodes.

In case of no APs a repeater node will act as a most performant "pure
forwarder" node. This node can better bridge two mesh clouds than a
simple node
does.

Hope you like it and greetings from Italy

Antonio

[Ian Salmon]

Interesting Antonio.....need to digest!!

For our personal network in UK 1 open AP is probably fine as long as we can
have space for some form of mac authentication

Trust Italy is warmer than we are for Christmas in the UK!

Ian

[ne0e0n]

Hi Antonio,

very interesting developments that give much extra flexibility,
thanks.

What would be very useful is the addition of coovachilli so that each
node can use a radius server (eg hotcakes) for user AAA.

Do you have any plans to include chilli into firmware or alternatively
isit possible to use ipkg to add coovachilli to existing build?

regards,

Guy