Re: ipw2200-normal can't associate with ipw2200-ap

 


________________________________

	From: [email protected]
[mailto:[email protected]] On Behalf Of
Clement Yew
	Sent: Monday, March 10, 2008 9:14 PM
	To: [email protected]
	Subject: [Ipw2100-devel] ipw2200-normal can't associate with
ipw2200-ap
	
	
	Hi,
	
	I have a question to ask.
	
	I managed to deploy ipw2200-normal driver on one embedded board
(stareast), and ipw2200-ap on another.
	
	I'm trying to associate the first board with the 2nd (Access
Point). However, it can't. I manually set the ESSID and the MAC Address,
but it still can't associate.
	
	Therefore, I tried associating the station with a Linksys WiFi
router, and it managed to associate properly. Can ping.
	Then, I tried to connect to the 2nd board(ipw2200-ap) using a
normal laptop, and it also associated properly. Can ping.
	
	I'm wondering what's the problem when i tried to associate both
boards to each other? Some forum says that the AP didn't broadcast the
ESSID. But, when i perform a scan, the station could detect the AP.
	
	Could anyone please provide me with sum help? Really appreciate
it.
	
	 

We are not involved with the ipw2200-ap project and thus do not know the
current status. Can you capture the logs of the ipw2200 driver when you
try to associate? Perhaps we can find some hints in there about what is
going on. You can load the module with debugging enabled (modprobe
ipw2200 debug=0xffffffff) - check ipw2200.h for the specific debug flags
that may be useful in this case.
 
Reinette

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
ipw2100-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ipw2100-devel