[Ns-developers] release update

[Tom Henderson]

Gustavo Carneiro wrote:
> 2009/5/23 Mathieu Lacage <mathieu.lacage at sophia.inria.fr>
> 
>> hi,
>>
>> It's been a while, and we are getting closer to our original target
>> release date of june 15th.
>>
>> Tom, Craig, and I had a phone conversation on wednesday to talk about
>> the status of the ipv4 rework. Tom plans to merge his ns-3-ip-routing
>> tree in ns-3-dev on monday. This tree appears to contain the crux of the
>> API changes we wanted with a couple of implementation issues to sort
>> out. Given the tight schedule, we agreed to aim for a 2-week
>> stabilization and bug fixing period after the merge, and then, to freeze
>> ns-3-dev around june 15th, hence, targeting june 21st or early july for
>> a final release.
>>
>> Current items still on the table for merging:
>>  - the tag rework: maybe it can make it after ip-routing is in
>>  - the virtual net device: gustavo, do you have interest in pushing
>> this forward with the name change (TapNetDevice) suggested by tom ?
> 
> 
> The name is OK with me.  I took the old code, renamed a few things, rebased
> against ns-3-dev, and added a bit more documentation.  Should be ready to
> merge.  The only thing missing is an example, I guess.
> 
>     http://code.nsnam.org/gjc/ns-3-tap-netdevice/
> 

Gustavo,
Although I suggested the name TapNetDevice, in reviewing this today, I 
noticed that it is really behaving like a Tun device instead of a Tap 
device (i.e. it is not adding an Ethernet header).

So, would you be amenable to naming it TunNetDevice instead?

I also thought that the example was a bit unusual because the 
TunNetDevice handler is creating a Udp socket to send the datagram out, 
instead of just a raw socket.  What do you think about changing it to a 
raw socket?

- Tom