From owner-freebsd-mobile Sat Feb 23 7: 2:20 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from ip68-2-87-144.ph.ph.cox.net (ip68-2-87-144.ph.ph.cox.net [68.2.87.144]) by hub.freebsd.org (Postfix) with ESMTP id 85A0737B400 for ; Sat, 23 Feb 2002 07:02:17 -0800 (PST) Received: from whale.home-net (whale [192.168.1.2]) by ip68-2-87-144.ph.ph.cox.net (8.11.6/8.11.6) with ESMTP id g1NF2G458294; Sat, 23 Feb 2002 08:02:16 -0700 (MST) (envelope-from johnjen@reynoldsnet.org) Received: (from jjreynold@localhost) by whale.home-net (8.11.6/8.11.6) id g1NF2FT47107; Sat, 23 Feb 2002 08:02:15 -0700 (MST) (envelope-from johnjen@reynoldsnet.org) From: John Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15479.44791.103461.897457@whale.home-net> Date: Sat, 23 Feb 2002 08:02:15 -0700 To: Pete Fritchman Cc: John Reynolds , mobile@freebsd.org Subject: Re: recommendation not to purchase DWL-1000AP In-Reply-To: <20020223040048.A42166@databits.net> References: <15479.20563.424313.788279@whale.home-net> <20020223040048.A42166@databits.net> X-Mailer: VM 6.88 under Emacs 20.7.1 Cc: Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [ On Saturday, February 23, Pete Fritchman wrote: ] > > This is what I got a few months ago. > > If you can manage to get the new firmware onto the AP, you can use > web-based configuration (but you'll need a windows machine to do > that...) Even hooked directly to the computer via cross-over cable, I could not upload the latest "web file set" onto the AP. I was able to do the first step of getting the latest firmware downloaded, but their upgrade utility just sat there looking for the IP address of the AP when trying to deal with the web set ... (this is with a cross-over cable and me being 100% positive the AP had an IP address and was "pingable" across that cable). The "outsourced tech support idiot" at D-link (after not being able to come up with a fix for this) suggested that I not go that route anyway because he says there are known issues with the web configuration that can cause the AP to "lock up". He refused to elaborate further but would only tell me they're working on another firmware and "web file set" upgrade to combat the problem. > I currently have it hanging off a switch right now with no problems. you are lucky. What kind of switch? At first I thought it was because my switch is a little unmanaged "cheapo" switch, but their lame software couldn't find the AP through my friend's $500 3com managed ultra-spiffy 24-port switch either. > Yep, same here... I ended up getting the MAC address by looking at the > latest lease on the DHCP server after plugging the AP in. When you cannot put the right sticker on your hardware to identify its MAC address, then your company has problems ... > Agreed... the software and upgrade stuff leaves much to be desired. The > window title for the upgrade software is "TestDLL" :-) yup!!! quite lame. Well, anyway, thanks for your $0.02 on the AP. I would still recommend that people who are just forging into 802.11b (like me) avoid this AP. The software is just too stupid to deal with. -Jr -- John & Jennifer Reynolds johnjen@reynoldsnet.org http://www.reynoldsnet.org/ Senior CAD Engineer, WCCG, Intel Corporation jreynold@sedona.ch.intel.com Running FreeBSD since 2.1.5-RELEASE. FreeBSD: The Power to Serve! "Unix is user friendly, it's just particular about the friends it chooses." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message