Hello Everyone!
I'm Spyros (hopefully)one of the gsoc students.
The project is to integrate information element syntax for various information in the packets and as a consequence implement backwards compatibility.
there is a number of ways to do this though and since it affects most of you (every info should be transmited in information element syntax) it would be good if you shared your opinions.
To get us started there is a wiki page http://www.open-mesh.org/wiki/batman-adv/BackwardsCompatibility which briefly explains the concept
Thank you, Spyros
To get us started there is a wiki page http://www.open-mesh.org/wiki/batman-adv/BackwardsCompatibility which briefly explains the concept
Hi Spyros
One thing i suggest you do is look and see what is already available in kernel and can be re-used for building and parsing TLVs. That might help decide which of BER, DER or PER to use.
Andrew
Hi Andrew
I googled bit and didnt find anything significant also I posted on kernel newbies mailing list and they couldnt help me.
SInce i'm completely new to kernel dev could you suggest a better way to look or a mailing list where I should ask?
On Fri, Apr 13, 2012 at 7:26 PM, Andrew Lunn andrew@lunn.ch wrote:
To get us started there is a wiki page http://www.open-mesh.org/wiki/batman-adv/BackwardsCompatibility which briefly explains the concept
Hi Spyros
One thing i suggest you do is look and see what is already available in kernel and can be re-used for building and parsing TLVs. That might help decide which of BER, DER or PER to use.
Andrew
On Sat, Apr 14, 2012 at 07:12:46PM +0300, NorthPole wrote:
Hi Andrew
I googled bit and didnt find anything significant also I posted on kernel newbies mailing list and they couldnt help me.
SInce i'm completely new to kernel dev could you suggest a better way to look or a mailing list where I should ask?
Hi Spyros
First off, this is supposed to be Summer of code, not Spring of code. So you have plenty of time.
I would probably look at this backwards around. You say on the wiki page that wifi uses TLVs. So look in the kernel code for 802.11 and see how IE are handled.
What other network protocols use TLVs? I know ATM signaling does, so maybe look at the ATM code. However, ATM signaling is quite complex, so maybe it is in user space?
What about protocols like Bluetooth? Frame relay? X.25, ISDN?
At the moment, you should just be getting an idea where are TLVs used in the kernel. Once you know that you can decide what to do next...
Maybe there is no code? Maybe there is lots of different implementations? Maybe there is lots of different implementations, but no generic code?
Maybe, it makes sense to have one generic library in the kernel and modify all the current code to use this library?
Andrew
b.a.t.m.a.n@lists.open-mesh.org
-
Andrew Lunn -
NorthPole