[Ns-developers] 802.11 mobility/transmission bug

Michele Weigle mweigle at cs.odu.edu
Tue Mar 13 08:01:31 PDT 2007


I don't know who all this gets sent to, but I just added a tracker  
entry for a 802.11 bug that I came across on the ns-users list.

-Michele

Begin forwarded message:
> From: "SourceForge.net" <noreply at sourceforge.net>
> Date: March 13, 2007 10:46:26 AM EDT
> To: noreply at sourceforge.net
> Subject: [ nsnam-Bugs-1679890 ] 802.11 mobility/transmission bug
>
> Bugs item #1679890, was opened at 2007-03-13 10:46
> Message generated for change (Tracker Item Submitted) made by Item  
> Submitter
> You can respond by visiting:
> https://sourceforge.net/tracker/? 
> func=detail&atid=775392&aid=1679890&group_id=149743
>
> Please note that this message will contain a full copy of the  
> comment thread,
> including the initial issue submission, for this request,
> not just the latest update.
> Category: ns-2
> Group: None
> Status: Open
> Resolution: None
> Priority: 5
> Private: No
> Submitted By: Michele Weigle (mweigle)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: 802.11 mobility/transmission bug
>
> Initial Comment:
> I happened upon this email to the ns-users list from a while back  
> describing a problem with 802.11.
>
> http://mailman.isi.edu/pipermail/ns-users/2004-April/041344.html
>
> "In 2.27 (not 2.26), the nodes are sorted according to their  
> coordinates so that when an event happens at a particular node,  
> that node updates its current coordinates and re-positions itself  
> in the list.
>
> When a node sends something, the wireless channel looks at the  
> sorted list and only sends the packets to nodes within the  
> transmission/interference range.
>
> The problem is that the node's position is not updated unless there  
> is an event happening at that node.  Thus, if you have an isolated  
> node (A) moving into range with other nodes, unless that node (A)  
> sends some traffic, it won't receive any traffic from other nodes  
> in its new
> neighborhood."
>
> I recently checked and the code mentioned in the email is still the  
> same in ns-2.30.
>
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> https://sourceforge.net/tracker/? 
> func=detail&atid=775392&aid=1679890&group_id=149743



More information about the Ns-developers mailing list