jkbull
11-13-2002, 01:52 PM
Slashdot ran a thread about a Linksys DOS vulnerability last week (http://slashdot.org/article.pl?sid=02/11/07/0324213&mode=thread&tid=172), so I decided to update the firmware in my Linksys BEFSR81 to the latest, even though the '81 wasn't specifically mentioned as being vulnerable.
However, after updating my Linksys BEFSR81 firmware from version 2.40.2 to version 2.42.7.1, the router no longer processes DNS queries.
My ISP gives out IP data via DHCP. On my small LAN, I use DHCP for all clients except for my server (file server, not web server). For the server I permanently assigned IP address (192.168.x.x, not interfering with the addresses the router's DHCP gives out), mask, and DNS data. For DNS IP address(es), I used the address of the router as if it were a DNS server. This worked fine under 2.40.2 - the router passed on DNS queries to the DNS server it was given by the ISP's DHCP, and passed answers back. No problems.
When I updated the firmware to version 2.42.7.1, however, this DNS processing was broken. Trying to get to a web page from the server using, for example, "http://www.google.com" would hang and eventually get a "page not available" error. Trying a google IP address, "http://216.239.51.101", worked fine. (This only affects the server; on my client machines, either way works fine. The clients, of course, query the DNS servers the ISP's DHCP gave out directly.)
Since I don't want to have to watch the ISP's DNS address and change the server's setup data whenever it changes, is there anything else I can do? Other than going back to 2.40.2, which I assume is vulnerable to the DOS problem?
However, after updating my Linksys BEFSR81 firmware from version 2.40.2 to version 2.42.7.1, the router no longer processes DNS queries.
My ISP gives out IP data via DHCP. On my small LAN, I use DHCP for all clients except for my server (file server, not web server). For the server I permanently assigned IP address (192.168.x.x, not interfering with the addresses the router's DHCP gives out), mask, and DNS data. For DNS IP address(es), I used the address of the router as if it were a DNS server. This worked fine under 2.40.2 - the router passed on DNS queries to the DNS server it was given by the ISP's DHCP, and passed answers back. No problems.
When I updated the firmware to version 2.42.7.1, however, this DNS processing was broken. Trying to get to a web page from the server using, for example, "http://www.google.com" would hang and eventually get a "page not available" error. Trying a google IP address, "http://216.239.51.101", worked fine. (This only affects the server; on my client machines, either way works fine. The clients, of course, query the DNS servers the ISP's DHCP gave out directly.)
Since I don't want to have to watch the ISP's DNS address and change the server's setup data whenever it changes, is there anything else I can do? Other than going back to 2.40.2, which I assume is vulnerable to the DOS problem?