[CUWiN-Dev] Re: google summer of code 2006

[John Atkinson]

At the summit David and I talked briefly about QoS being implemented
in CuWiN.  That is a big issue for the project in Ghana because
satellite bandwidth is expensive, though I can't assume it is
affecting other projects in quite the same way.

Because the CuWiN mesh NAT's at the Internet-connected node(s) (and I
think it has to for ease-of-use in adding a mesh to existing LAN's) it
is not possible to use many of the off-the-shelf shaping tools to
limit network abuse at the gateway.  And in the end each node should
have some idea of QoS to keep a mesh properly flowing.

So I propose a couple of ideas for QoS on CuWin that I believe
maintain the out-of-the-box, self-configuring ideal:
1. Allow nodes that offer services (Internet-connected) to have some
basic way of managing the pipes.  Possibly the iproute2 objects would
work; I don't know how well they are implemented in NetBSD.  The
front-end for m0n0wall, or other popular router apps, may serve as
good models to implement this to the GUI.
2. Prioritize H.323 and SIP across the board, at the kernel.


I just picked up some crappy headsets from Taiwan, and I'll do some
intranet voice apps over the mesh in the weeks to come.  I know IIT
proposed a SIP-Mesh project.  Did they ever publish anything viable to
cuwireless?  I found a ppt on the web, but it didn't have any
conclusions.

-John