Quite some time ago I decided to change my protocol on my DIR-655 to "N" only, since I didn't need it to run an older protocol (since I had a second (older) router (airport extreme) running B/G. Basically what I did was piggyback my extreme to the DIR, and give it a new name, but with the same password. I have a pretty long house, so this allowed my a greater range, since I put the extreme on the opposite side of the house (underneath, in the crawl space). I gave it a separate name becasue I was finding that, with the same name, my computers would switch automatically and this would be disruptive. With a separate name, I can control which network I connect to manually.
Anyway, I ran a scan result yesterday, since I have been having really annoying disconnects lately - basically at some point during he day, nearly every day (when I am home) the network just drops completely. Whichever computer (or device) is connected will have to completely reboot/turn off in order to connect again. It is strange, since rebooting the DIR, or the modem, doesn't do it, but I actually have to restart the commuter (or TV, for example). If anyone has any comments on this it would be appreciated - I am looking at the DIR settings, but cannot figure out what it could be. I am thinking something with DHCP, but have no idea really. On my Mac, if I renew the DHCP lease, it has no affect.
Anyway, LONG STORY SHORT (too late I know), when i ran the scan results, I find that a network scan returns a protocol for my DIR-655 as B/G/N, instead of just N. I know i have the 802.11 Mode set to 802.1 1N only. What is going on here?
Also, is there a FAQ for an optimal manual setup for all the myriad of settings inside the DIR? I did add some DHCP reservations last night to a few devices to see if this helps.
Author
Topic: DIR-655 protocol settings verses scan results, and other issues (Read 3801 times)