DLink AP-2000+ Setup (was: question)

[Roger Oberholtzer]

On Fri, 2004-01-09 at 20:10, Condon Thomas A KPWA wrote:
> > In terms of just using it, it worked out of the box. At least 
> > with D-LINK
> > cards. The web interface seems to not work from Linux (with 
> > or without the
> > linuxart/XP drivers) nor from Win98. And that is needed for 
> > turning on the
> > encryption, as you know. I did choose the AP2000+ 
> > specifically because it
> > could be configured on the web. LOL.
> 
> I think it was your recommendation on this list that got me to purchase
> mine, for the same reason, too. 

Yipes. Still, it is working nice for me. Mine is also behind a firewall.
Just the computers at home use it. Still, there is a cafe downstairs,
and you never know what cafe folk get up to.


>  I was able to access it via the cable
> (crossover cable required but not provided), and access it, but not complete
> the setup that installed the encryption key with anything but the XP laptop
> using IE6.  I was wondering if you had tried it with Mozilla, but it doesn't
> sound like it.

Mozilla, konqueror and Opera on Linux. Mozilla and IE on Win 98. With
every mix of drivers I have. As I wrote: next I will try the cable
direct to see what I can break that way. The docs do say that you 'can'
do this. Maybe they mean that you MUST do this.

As to the cable, the 2000AP+ autosenses this. This was the first time I
came across this. So, one cable works in both conditions. Or so the AP's
docs claim.

This is my Saturday task.



>  
> > It wants a 192.168.x.x address to access the web config, 
> > which I think is
> > only available via the cable. Despite what the docs say. I am 
> > also going to
> > try to access it when it has been powered on and never connected to my
> > external net. Maybe it then gives me a 192.168.x.x address. 
> > As it is, it
> > seems to pass on dhcp addresses from our building's dhcp server in the
> > basement, which is nice. But they are not 192.168.x.x. As it 
> > is acting as a
> > router, I thought it 'might' intercept things for the web admin's IP
> > address. Of course, that would let anyone in from a wireless 
> > card. Maybe
> > that is not good.
> 
> The specific address it wants (default) is 192.168.0.50.  This can be
> changed (and I *was* able to accomplish that via the Mac).  It also allowed
> me to change the password.  I would think that by changing the IP, password,
> the encryption and the SSID you would have made it too difficult to crack
> from the web access.  However, since mine sits behind the firewall, and
> someone would have to be in the woods near our house to access my wireless
> without my knowledge, I'm not real worried about outside cracking.
> 
> I'll try accessing the controls from my laptop tonight (via wireless) and
> report the results on Monday (there is some problem between my ISP and the
> old list server that precludes me joining the list from home -- hmm, perhaps
> I can post from there, though).

I have tried from a laptop running SUSE 8 and 9 with an OpenSource
driver and the linuxart/XP drivers, as well as Gentoo and a PCI card
with the same drivers. I really feel that the admin is over the cable
only. At least the first time.