This build still uses the build 270 wireless driver, as I need more feedback. It seems like there not one single wireless driver that works best for everyone... Build 220 had average performance across the board, 246/260 were giving issues to half of the users, and 270 fixed issues for some but create other issues for others. So at this point I still broader feedback on this build 270 driver.
I loaded the b4 firmware 2 days ago and the wired internet is ok
but the wireless Part has gone down 4 times since then (2.4 & 5 ghz)
I didn't have the issue with b3
It said I had an internet connection but no dns
thanks
I have a mix of Win 7, Android and iOS devices hooked, some wired, many wireless to the RT-N66U and everything looks ok. The only strange thing is the fact that almost every time I click on "refresh" in the "Client status" section of the Network Map I get a different quantity of devices...
Looks similar to the situation reported on this thread: http://forums.smallnetbuilder.com/showthread.php?t=9869... but an Iphone4 and Android/Samsung Gal II (connected < 1 hour) were visible in the wireless log and dhcp leases log, but not included in the Client status... nevertheless I refreshed many times.
Merlin, will you be released any more updates for RT-N16 or no? I believe I am running 3.0.0.4.266 23b
Looks similar to the situation reported on this thread: http://forums.smallnetbuilder.com/showthread.php?t=9869
GH
I have similar experience, if I click fast on Clients or Refresh I see different quantity of devices.
Also I now experience that the all our devices, which were in the house for >2 hours, are included in the Client list, but an Iphone4 and Android/Samsung Gal II (connected < 1 hour) were visible in the wireless log and dhcp leases log, but not included in the Client status... nevertheless I refreshed many times.
>nslookup ts11.test.local
Server: www.asusnetwork.net
Address: 192.168.1.1
*** ts11.busse.local wurde von www.asusnetwork.net nicht gefunden: Non-existent
domain.
>nslookup ts11.test.local 128.39.51.1
Server: dc3.test.local
Address: 128.39.51.1
DNS request timed out.
timeout was 2 seconds.
Name: ts11.test.local
Address: 128.39.51.21
nameserver 128.39.51.1
search test.local
nameserver 212.6.108.142
nameserver 212.6.64.15
Hi Merlin, bad news, after reboot my router the dns resolution does not work.
The resolf.conf ist correct but dnsmaq dont use it.Code:>nslookup ts11.test.local Server: www.asusnetwork.net Address: 192.168.1.1 *** ts11.busse.local wurde von www.asusnetwork.net nicht gefunden: Non-existent domain. >nslookup ts11.test.local 128.39.51.1 Server: dc3.test.local Address: 128.39.51.1 DNS request timed out. timeout was 2 seconds. Name: ts11.test.local Address: 128.39.51.21 nameserver 128.39.51.1 search test.local nameserver 212.6.108.142 nameserver 212.6.64.15
Yes, indeed...I just noticed the (same) nickname... ;-)Yes, indeed...
I don't see that as a problem, I was just reporting about the observation. As you mentioned, it takes 1 minute or 2 to get back the full list after asking for a refresh. That said, all my devices are there: Win 7, iOS, Android, linux.When you click on Refresh, the router starts a process that doesn't immediately complete. Wait 1 minute or two after clicking on refresh, more devices can automatically start appearing at the scan process progresses.
For everyone with this issue, are missing devices usually devices with a static DHCP reservation + name, or fully dynamic?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!