Before I go into any further details, I'm going to describe the current setup. Connected via ADSL, I have a BT HomeHub. This is the networks DHCP server with both wired and wireless connections. It came with static IP addresses/masks of: ...
Before I go into any further details, I'm going to describe the current setup.
Connected via ADSL, I have a BT HomeHub. This is the networks DHCP server with both wired and wireless connections. It came with static IP addresses/masks of:
10.0.0.138/24 (assuming that's for WAN)
172.16.1.254/24 (this is for the telephone handsets it also manages)
192.168.1.254/24 (for the LAN/WLAN connections.)
It serves two pools of DHCP addresses:
172.16.1.1 - 172.16.1.253 (handsets)
192.168.1.64 - 192.168.1.237 (LAN/WLAN)
Wireless encrytion in use is WPA2. A laptop, server and Wii console all connect to this via WLAN, with the router being configured to use specific addresses for each device. These all work perfectly.
Unfortunately, the Nintendo DS Lite handheld is not compatible with WPA based encrytion. So after mulling over spening money on the PC connector to let it hop on the connection, I decided to add a WEP access point to the network instead as I already had the hardware lying around. When I'm not using the DS online, I can just switch off this extra AP without disrupting the rest of the network.
This AP is a "Belkin Wireless G Access Point F5D7130". It is configured with a static IP address of 192.168.1.253, and is connectd directly to the HomeHub via cable. The HomeHub recognises its presence and static addressing.
Everything works. The Homehub recognises the DS as being connected through the cable (as the wireless AP is) and it can get online easy. I just can't administrate the Belkin AP from the laptop or server.
The first page will load correctly, but after that it will refuse to show, with Firefox citing reasons such as "Connection reset...." or "Failed to connect (though the site seems valid)". The device always responds to pings and has the most recent firmware installed. Connecting the AP directly to a computer with the cable shows no problems.
Hell of a description for such a small problem but I thought it would be better to list it all. Here's an image of the setup:
Cheers,
DFF