Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
ns-3-users
Home
+ new post
About this group
Join this group
Message from discussion 802.11b
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Nicola Baldo  
View profile  
 More options Aug 6 2009, 6:43 am
From: Nicola Baldo <nba...@cttc.es>
Date: Thu, 6 Aug 2009 03:43:32 -0700 (PDT)
Local: Thurs, Aug 6 2009 6:43 am
Subject: Re: 802.11b
Print | View thread | Show original | Report this message | Find messages by this author
Hi,

On Aug 5, 4:39 am, cb <cbellett...@gmail.com> wrote:

> hello all,
> I'm trying to use the 802.11b as phy instead of the default 802.11a in
> an infrastructured wireless network. in order to do that, I just call
> YansWifiPhyHelper::SetStandard("Standard", StringValue("802.11b")) on
> the relevant object.

> unfortunately, nothing appears to work at all. looking at the pcap
> traces, associations to the AP are very problematic and with lots of
> retransmissions (though associations are at last successful), and
> packets are not delivered at all, since nobody answers the ARP
> requests of the sending node. I found the same behavior in my own code
> and in the third.cc example as well (once 802.11b is set up).

> any clues on why this happens? I couldn't find any.

I don't have the code at hand to check this, but I remember that some
time ago I faced a similar problem when modifying a simulation program
to make it run with 802.11b instead of 802.11a. The issue was that the
SetStandard command did not change the value for the ACK timeout
(which should be longer in 802.11b), and STA association failed
because of this. Well, I guess I should have filed a bug report for
this issue, but at the time the only 802.11b example program in ns3
was not working, so I ended up filing bug 642 instead (http://
www.nsnam.org/bugzilla/show_bug.cgi?id=642).
Since that bug was closed, if you could check whether examples/wifi-
clear-channel-cmu exhibits the same problem you are experiencing, and
post a bug report if positive, it would be great.

Regards,

Nicola


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2012 Google