Hi,
I've looked at the pdf you sent. May you define further the following
fields :
- type (are there any fixed values?)
- nlinks : this field is used to tell how many fields there will be in
the variable length header. Right?
- next : semantic ?
- flags : bit X means ... ?
- Query Dst : IPv4 ?
Is this header used for the purpose of an improved source routing?
Can you send me a sample capture file?
thanx,
Sebastien Tandel
Nicola Arnoldi wrote:
> Here you will find informations for designing a dissector for the
> Roofnet Layer 2.5 routing protocol for wireless mesh network of
> http://pdos.csail.mit.edu/roofnet/.
>
> The Layer 2.5 works as follows.
>
> - Inside the MAC 802.11 frame a 1500 byte datagram is located.
>
> It consists of a 400 byte header and a 1100 byte data field. (see
> attachment for a pictorial representation)
>
>
> The 400-bytes header contains a lot of informations. Some of them are
> fixed, such as the protocol version and other stuff (160 bytes).
>
> The variable-length part of the header contains routing information of a
> multi-hop transmission. More specifically, those bytes contain the IP
> addresses of the hops involved in the route of the current datagram.
>
> So, 1100+400 bytes form the payload of Layer 2 MAC protocol.
>
> In the data field a standard UDP or TCP datagrams may be carried.
>
> I hope everything is clear.
>
> If you need a sample capture just tell me.
>
> Regards
>
> Nicola Arnoldi
>
>
> On ven, 2006-12-08 at 15:16 -0800, Stephen Fisher wrote:
>
>> On Thu, Dec 07, 2006 at 10:22:26AM +0100, Nicola Arnoldi wrote:
>>
>>
>>> If you're into wireless mesh networking stuff, you've probably heard
>>> about Roofnet, an MIT project with WMNs. Well, Roofnet introduces a
>>> 2.5 OSI Layer, with certain headers. Anyone designed a dissector for
>>> Roofnet or is anyone interested into it?
>>>
>>> If so, please contact me, I will be happy to provide the packet
>>> structure...
>>>
>> Feel free to send a link to the packet structure and a link to a sample
>> capture file to the list. Someone may have time to work on a dissector
>> for it. If you don't hear anything back, add it to the wish list (again
>> with the structure and a capture file) at
>> http://wiki.wireshark.org/WishList
>>
>>
>> Steve
>> _______________________________________________
>> Wireshark-dev mailing list
>> Wireshark-dev@xxxxxxxxxxxxx
>> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Wireshark-dev mailing list
>> Wireshark-dev@xxxxxxxxxxxxx
>> http://www.wireshark.org/mailman/listinfo/wireshark-dev
>>
