DLink AP-2000+ Setup (was: question)

[Andrew L. Gould]

On Saturday 10 January 2004 02:31 pm, Joel Hammer wrote:
> Came in late here, but I just got done configuring a
> linksys wireless router and wap. This has wired network
> ports, the wireless port, and an "internet" port.  I put
> my linksys router behind my linux firewall/router. I used
> linux for all the configuration of the linksys router.
>
> Some problems with setting up this device may shed light
> on what you are facing.
>
> 1. The wired and wireless clients are all the same to the
> router. No difference as far as I can tell except in some
> wireless security measures.
>
> 2. The MAC filter immediately kills my wireless's client
> ability to talk to the wired network. I guess the MAC
> filter applies to all clients, not just the wireless
> ones. WEP has not been a problem.
>
> 3. If you change the default ip of the router (not the
> internet port) then you may not be able to access the
> router no matter what you do.

I changed the router IP and network address of my Linksys BEFW11S4 V.2:

1. I used a static IP address for the computer from which I performed the 
admin functions.  Initially, the IP address for this computer was 
192.168.1.10.  The gateway was 192.168.1.1.

2. I accessed the router's configuration program using mozilla.

3. I changed the LAN IP address from 192.168.1.1 to 192.168.13.1; but left the 
subnet mask at 255.255.255.0.  When I clicked "Apply", the changes were made 
and, as expected, I lost contact with the router.

4. I reconfigured my computer's static IP address to 192.168.13.10, the 
gateway to 192.168.13.1 and reactivated the ethernet port.  I was then able 
to reestablish contact with the router.

5. After accessing the router's configuration program again and clicked on the 
DHCP tab.  The network address portion of the starting IP address for DHCP 
had changed to match the new network address (192.168.13.__).  I continued 
configuring and activating DHCP w/ WEP as normal.

6.  I also changed the default password for the configuration program.

>
> 4. It just happens that the ip of my internal network
> (192.168.1.x) is the same as the default of the router and
> the same as the apparently mandatory 192.168.1.x addresses
> served up by the builtin DHCP server. This means that my
> wireless client has the same network name as all my wired
> clients. This has been good and bad.
>
> 5. The wireless router can be flaky, with pinging from a
> client  often not getting any replies for a while, then
> it will start working.
>
> 6. When refreshing your network connection on the client
> (windows xp laptop in my case) the network device you
> refresh is the bridge, not the actual interface.
>
> 7. Routing has been a big problem. I finally have gotten
> the router to use the "internet" port as its default port,
> but this was a struggle, and I don't know what I did to
> make it finally start working. I have been unable to get
> routing to change using the "advanced" routing features.
>
> Anyway, wireless looks like it is going to be useful. Since
> our IS dept is ignoring my request to run cable between
> two rooms in the lab, I think I have found a work around.
>
> Joel

Andrew Gould