Here is the firmware in the radio cards I am using. I get identical results / symptoms on all three cards w/ different firmware versions
I specify iwconfig netcs0 essid "MyNetESSID" and then it connects to an AP with essid "default" or "linksys" which is an AP my neighbor set up ( either a netgear or Linksys 802.11g router/AP ) Teletronix 100mW ( Zcomax 325H ) prism netcs0: NIC: id=0x800c v1.0.0 netcs0: PRI: id=0x15 v1.0.7 netcs0: STA: id=0x1f v1.3.6 Engenius 200mW netcs1: NIC: id=0x800c v1.0.0 netcs1: PRI: id=0x15 v1.1.0 netcs1: STA: id=0x1f v1.4.9 Demarctech 100mW netcs1: NIC: id=0x800c v1.0.0 netcs1: PRI: id=0x15 v1.1.0 netcs1: STA: id=0x1f v1.4.9 ----- Original Message ----- From: "wispdist" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, September 23, 2004 2:20 PM Subject: [leaf-wisp] bld 2546 - client / managed mode connects to AP regardless of ESSID > bld 2546 - client / managed mode connects to AP regardless of ESSID > > I have been running build 2546 for approx 6mos to a year and recently ( > within the last 3 months ) people have been installing new Linksys and > Netgear 802.11g routers in their offices. > > What happens is our units running wisp-dist build 2546 on a soekris or in a > PC ( both pcmcia and pci ) will connect to one of these routers instead of > to our APs. All of our APs are also running the same build of wisp-dist. > > I can change the essid on the client ( managed mode ) and it will continue > to authenticate and connect to these new APs. > > I tested this very scenario one year ago and all worked fine. > > enabling WEP does not help. > > If I do a "iwconfig" it will show an ESSID that is different than the one > set ( usually "default" ) > > If I manually do a "iwconfig netcs0 essid MyNetworkESSID" it will remain > connected to this AP and when I do a "iwconfig" it well show a different > essid. > > I cannot find a way to specify the BSSID on the managed side so it will > connect to our Access Points. The host_ap driver does not seem to support it > ( or maybe the wireless tools ... I don't know ). > > I cannot tell if these new Linksys and Netgear APs are answering and > accepting any client regardless of essid or if the wisp-dist has a bug in it > causing this to happen. > > Either way, our clients are being captured by these rogue APs which takes > them off of our network and takes them offline. > > Anyone else experience this ? Any ideas? > > Jeff Rhue > > CTO - WiLogic, Inc. > > 714-230-8487 > > [EMAIL PROTECTED] > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > leaf-wisp-dist mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php _______________________________________________ leaf-wisp-dist mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-wisp-dist
