I loaded 1.21 on my router.
I've disabled INFO logging, even though I now have it all being sent to a syslog-ng server on the local lan, I noticed the router was still keeping in memory its log entries. Having the logging reduced kept my router running longer, 8-10 days at a time, versus having it lockup within 3-4 days with out of memory issues.
I reenabled the NTP update to see whether that'll work or not. I had issues with 1.20. It seems the router has issues doing DNS queries to LAN side DNS server.
The router itself feels less responsive than 1.20. It's slower in displaying the login screen and the various pages. I've been noticing pauses in viewing youtube videos, although I'm not sure whether that can be attributed to the router or not.
Haven't seen too many issues with either Xbox or VOIP/UMS traffic, but it's only been a couple of days since I've loaded it on.
EDIT: Nope, NTP updates still fails.
(double timestamp due to router not being able to update its own time correctly)
Jul 12 16:35:58 192.168.0.1 Sun: Jul 12 08:07:31 2009 Sanity System Log: Unable to find DNS record for time server time-a.nist.gov
And yes, the named can be queried from anywhere, including the router IP address. If the port was open on the router, you could query the named from the internet. I'm not even seeing the query within the named log in debug mode so the internal routing isn't working.
I check the Routing and I see the following:
192.168.0.0 255.255.255.0 0.0.0.0 1 LAN System
So it should be routing the DNS queries correctly to 192.168.0.101
Local query of the DNS I'm running locally shows:
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1729
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;time-a.nist.gov. IN A
;; ANSWER SECTION:
time-a.nist.gov. 1765 IN A 129.6.15.28
;; Query time: 0 msec
;; SERVER: 192.168.0.101#53(192.168.0.101)
;; WHEN: Sun Jul 12 16:42:24 2009
;; MSG SIZE rcvd: 49
I tried setting it to the dlink NTP servers, and no dice.