<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.9">
</HEAD>
<BODY>
Still no joy.<BR>
<BR>
Once changing to ad-hoc mode it immediately grabs the AP correctly. But as soon as we change back to Managed mode, it returns to the searching/44:.44:44:44:44:44 mode again.<BR>
<BR>
We have tried it with multiple APs so something is awry..<BR>
KH<BR>
<BR>
On Wed, 2004-03-10 at 05:31, O.J.Schuring@telecom.tno.nl wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE><FONT COLOR="#737373"><I>Did u solve the problem yet?
I found out that it is in fact a association failure, as Pavel Roskin mentioned. This can be due to a mismatch in the channel number.
To change this, type do:
# iwconfig wlan0 channel 4
(wlan0 being your wireless device, and 4 being the channel the AP is working on.)
If u get an error, try switching to ad-hoc mode first, then set the channel nr. then go back to managed mode again.
# iwconfig wlan0 mode Ad-hoc
# iwconfig wlan0 channel 4
# iwconfig wlan0 mode Managed
> -----Original Message-----
> From: Kelly Hogan [mailto:kshogan@linora.com]
> Sent: maandag, 8 maart 2004 16:46
> To: Schuring, O.J.
> Cc: hostap@shmoo.com
> Subject: RE: Hostap AP to Hostap Managed 44:44:44:44:44:44
>
>
> Not using keying. Will try it. What was your iwconfig setting to
> change the key?
>
> On Mon, 2004-03-08 at 01:09, O.J.Schuring@telecom.tno.nl wrote:
> > KH,
> >
> > Do you use something like dynamic keying?
> >
> > I had the same problem using 802.1x. My solution was to set
> a key for the client. This is just a temporary key and can be
> something like '12234567890'
> >
> > Goog luck,
> >
> > Olof
> >
> > > -----Original Message-----
> > > From: Kelly Hogan [mailto:kshogan@linora.com]
> > > Sent: zondag, 7 maart 2004 6:33
> > > To: hostap@shmoo.com
> > > Subject: Hostap AP to Hostap Managed 44:44:44:44:44:44
> > >
> > >
> > > Hello,
> > >
> > > This must be a simple issue, but I am running hostap 0.1.3 on two
> > > machines, one it AP mode, then one in Managed mode.
> Using engenius
> > > 2511MP Plus cards in pci mode.
> > >
> > > The ap mode on the unit works well, but the client never
> seems to join
> > > the essid, just flipping channels like a hyperactive
> couch potato and
> > > staying at AP 44:44:44:44:44:44 Also noted that the bit
> > > rate goes to 2
> > > Mbps and that the interface is dropping packets.
> > >
> > > I have tried to iwconfig the ap mac with no joy. I did see
> > > some earlier
> > > emails about this as a problem, hostap to hostap, but no
> solutions.
> > >
> > > Any suggestions would be appreciated.
> > >
> > > firmware 1.7.4/1.1.0
> > >
> > > kernel 2.4.20-8
> > >
> > > wlan0 IEEE 802.11b ESSID:"wisp"
> > > Mode:Managed Frequency:2.467GHz Access Point:
> > > 44:44:44:44:44:44
> > > Bit Rate:2Mb/s Sensitivity=1/3
> > > Retry min limit:8 RTS thr:off Fragment thr:off
> > > Encryption key:off
> > > Power Management:off
> > > Link Quality:0/92 Signal level:-69 dBm Noise
> level:-90 dBm
> > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> > > Tx excessive retries:0 Invalid misc:45
> Missed beacon:0
> > >
> > >
> > > wlan0 Link encap:Ethernet HWaddr 00:02:6F:09:9F:DE
> > > inet addr:10.0.1.3 Bcast:10.0.1.255 Mask:255.255.255.0
> > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > > RX packets:0 errors:0 dropped:26 overruns:0 frame:0
> > > TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
> > > collisions:0 txqueuelen:100
> > > RX bytes:0 (0.0 b) TX bytes:2952 (2.8 Kb)
> > > Interrupt:11 Memory:f1cca000-f1ccb000
> > >
> > >
> > > Thanks,
> > > KH
> > >
> > >
> > > _______________________________________________
> > > HostAP mailing list
> > > HostAP@shmoo.com
> > > </FONT><A HREF="http://lists.shmoo.com/mailman/listinfo/hostap"><U>http://lists.shmoo.com/mailman/listinfo/hostap</U></A>
<FONT COLOR="#737373">> > >
> >
>
>
</I></FONT></PRE>
</BLOCKQUOTE>
</BODY>
</HTML>