Urgent >> Aironet 350 pci card on LInux

[Joel]

Dear James

I changed my configuration.

I m just doing

iwconfig eth2 mode Managed
iwconfig eth2 essid d2vwireless

thats it.
it starts working.
but after atleast 3 hrs it got disconnected from ap
it is not pinging the ap's ip address.

but after 15 to 20 mins it starts pinging..
dont know what the case it is..
has any one experienced this type of problem bfore?

any suggesstions or advice..
thanks,
Joel
--- "James F. Carter" <jimc at math.ucla.edu> wrote:
> On Fri, 13 Jun 2003 02:57:28 -0700 (PDT), Joel
> <joelsolanki at yahoo.com> 
> wrote:
> > First I use redhat. I can establish the link
> > correctly.
> > i have done the following commands.
> >
> > iwconfig eth2 mode managed  <==good
> > iwconfig eth2 nick test     <==good
> > iwconfig eth2 essid wireless <==good
> > iwconfig eth2 rate 1M       <==Omit this
> 
> I assume the access point really does have an ESSID
> of "wireless".  Don't 
> set either the rate or the frequency.  The frequency
> is set by the access 
> point (ultimately by you, when you configure the
> AP), and the firmware will 
> use the frequency for whichever AP it decides to
> use. The firmware is 
> usually pretty good at deciding the rate that it can
> make to work.
> 
> > After doing this commands in redhat My linux
> client
> > connects to accesspoint.
> > but it ping the accesspoint in 6 ms 10 ms
> sometimes it
> > goes to 1000 ms tooo.
> 
> Pings in the range 6 to 10 msec are normal.  On
> Ethernet, if a packet is 
> dropped it's gone forever, but on 802.11b the card
> or AP may miss a packet 
> on the aether, and will be aware of it through
> mandatory link-level acks, 
> and will actually retransmit the lost packet.  That
> could account for 
> occasional long ping times, or pauses in your
> applications.
> 
> > then after some time it stops pinging.
> 
> Sorry, I can't help you on that one.  What driver,
> and version, are you 
> using, plus, which firmware (with version) does the
> driver say are on the 
> card?  (Look in your syslog.)  Obsolete versions of
> the Orinoco driver, 
> with Intersil firmware, can provoke the card into a
> funny state where you 
> get tons of syslog messages and no packets sent.
> 
> > i cant get connect to accesspoint.
> > This is due to frequency problem.
> > how do i change the frequency of my card.????????
> 
> No it isn't.  You could change the frequency on the
> access point (but it 
> wouldn't cure your problem).  If in managed mode you
> set the frequency 
> explicitly, the card will start looking for an
> access point on that 
> frequency, find none, and will eventually go back to
> the frequency that the 
> AP is actually using.
> 
> In Ad-Hoc mode, the card elected as leader
> (generally the first to boot) 
> needs its frequency set explicitly, and the others
> will find and change to 
> it, but since a new election can come after any
> network glitch, it's good 
> practice to set the (same) frequency on every card
> in the Ad-Hoc cell.  But 
> since you have an AP, this doesn't apply to you.
> 
> You might want to have a look at this link:
>
http://www.math.ucla.edu/computing/user_support/hardware/wiresetup.html
> 
> -- 
> James F. Carter          Voice 310 825 2897    FAX
> 310 206 6673
> UCLA-Mathnet;  6115 MSA; 405 Hilgard Ave.; Los
> Angeles, CA, USA  90095-1555
> Email: jimc at math.ucla.edu   
> http://www.math.ucla.edu/~jimc (q.v. for PGP 
> key)
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com