On Fri, 2009-08-14 at 12:34 -0700, Michael wrote:
> Does this work with the latest dev release?  I get errors about "Could
> not find attribute ns3::YansWifiPhy::Standard."

> Thanks!
> Michael

> On Aug 12, 7:50 pm, Gary Pei <guangyu....@boeing.com> wrote:
> > I took a look at thethird.cc example for 802.11b. The problem is that
> > you have to set 802.11b standard for MAC as well to call correct
> > WifiMac::SetStandard (enum WifiPhyStandard standard) function.

> > So, here is correct way to use 802.11b forthird.cc

> > 87d86
> > <   phy.Set ("Standard", StringValue ("802.11b") );
> > 97,98c96
> > <     "ActiveProbing", BooleanValue (false),
> > <     "Standard", StringValue ("802.11b"));
> > --->     "ActiveProbing", BooleanValue (false));

> > 106,107c104
> > <     "BeaconInterval", TimeValue (Seconds (2.5)),
> > <     "Standard", StringValue ("802.11b"));

> > Gary

> > On Aug 7, 4:21 pm, Tom Henderson <t...@tomh.org> wrote:

> > > Nicola Baldo wrote:
> > > > 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 thethird.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.

> > > I filed a bug on this issue:http://www.nsnam.org/bugzilla/show_bug.cgi?id=655

> > > The answer may not be a trivial fix since this attribute is trying to
> > > set the values of other attributes.

> > > Tom- Hide quoted text -

> > - Show quoted text -