"Home Network" setting cannot be saved

kegobeer said:

It appears you can't see what channel you are using. I thought I saw it in there. I was probably thinking about the channel info you can see/set on the router. You could go to the router's config page and see which clients are connected to the router, though.

To know whether the channel switch-over happened or not, I need be able to check the channel info at the client side.

If you have multiple SSIDs, I don't think you can move between them in such a small area and expect Windows to move to that one. You'd pretty much have to move to the edge of the range of one and lose the connection - then if the other network is available it might auto-connect, but I think you'd have to manually connect.

In this case(two different SSIDs are used) I can see if the client changed the access point by checking the SSID.

I'd just use the same SSID. If the connection level drops to a magical point (Windows will determine that), it will automatically switch to the stronger signal with the same SSID.

In this case I lose ability to use the SSID as above. But I have just gotten an idea and will give it a try.

The DHPC client list shows what devices are connected and their IPs, device names and MAC addresses, but no channel being used by these devices. Probably I have to look for a utility or something if I really want to check the channel info.
I am just interested to check how dual-AP works or how well doubling the AP works.

I appreciate your response which prompted me to review the router settings and resolved the problem stated in my original post.

I appreciate your continued follow-ups.
My experiment indicates that all devices regardless of which AP being connected to, are listed on the router A and none on B. This makes sense because there cannot be such DHCP client list on the router B. However, I notice that the router B still has its DHCP list which shows the device used to setup the router B. It stays even the device is shut off and cannot be erased. The IP is the first one in the default DHCP range for the router B so that it must be the one assigned to the device when being used to configure the router B.

Another thing: I have started the experiment for using two SSIDs. The public network problem came back which is the topic of this thread. This indicates that this configuration may not be stable. As a matter of fact this is the second time that it happened. When it happened for the fist time I started this thread.

kegobeer said:

Do you have them connected via ethernet cable? If not, make sure you do that as well.

Yes.

Do not connect the network cable to the WAN port on either router.

The above is quote from your earlier post. I think you meant to say that the WAN port of the router B should not be used for cascading the router B with A. Another word, the Ethernet cable should be run from LAN port to LAN port. Is this correct?

I think my configuration using the two routers is the same as yours except the IPs assigned to the two routers, and the DHCP range of the router A.

The problem I encountered (being the topic of this thread) is that the settings of the router B appears to be for some reason, screwed up. And when this happens I can no longer access the router B to determine how it is altered.
I will continue the experiment in an attempt to find out what is exactly happening.

I am using D-Link DIR655 v.A4 as router A (DHCP enabled) and Linksys WRT54G v5 as router B (DHCP disabled).