Like Jamie, I've been having problems with my Dynalink RTA1320 modem/router. I ended up replacing it with a Linksys AG300. That seemed to fix the problems, but ... about once per day access to the Internet gets cut off. It's easy enough to restore functionality. All I have to do is (a) power off/on the modem/router, or (b) disconnect/connect, or (c) add my ISP's DSN servers to the network tables on my computer. In other words, it appears to be a DNS problem. The question is what's happening? I've put my ISP's DNS addresses in the router/modem's setup (makes no difference). When DNS name resolution via the router fails, all computers on the network fail to access the Internet. The timing of the problem doesn't coincide with the monitored with the monitored burglar alarm "phoning home". Any suggestions on what the problem is or what to try next? Michael
On Jan 11, 2008 3:05 PM, Michael McDonald <mikencolleen(a)gmail.com> wrote:
Like Jamie, I've been having problems with my Dynalink RTA1320 modem/router. I ended up replacing it with a Linksys AG300. That seemed to fix the problems, but ... about once per day access to the Internet gets cut off.
It's easy enough to restore functionality. All I have to do is (a) power off/on the modem/router, or (b) disconnect/connect, or (c) add my ISP's DSN servers to the network tables on my computer.
In other words, it appears to be a DNS problem. The question is what's happening?
What is the period of your DHCP lease? Perhaps it is tied into that? -- Web: http://wand.net.nz/~iam4/ Blog: http://iansblog.jandi.co.nz
I have an ag300 and the DNS forwarder is a bit broken so you are better of not using it and stick with putting the DNS entries on each PC. The device uses a very old 2.4 kernel and a very buggy DNS package. Also be very careful with ADSL2 connections as they can cause many stability problems. Cheers Brett. Michael McDonald wrote:
Like Jamie, I've been having problems with my Dynalink RTA1320 modem/router. I ended up replacing it with a Linksys AG300. That seemed to fix the problems, but ... about once per day access to the Internet gets cut off.
It's easy enough to restore functionality. All I have to do is (a) power off/on the modem/router, or (b) disconnect/connect, or (c) add my ISP's DSN servers to the network tables on my computer.
In other words, it appears to be a DNS problem. The question is what's happening?
I've put my ISP's DNS addresses in the router/modem's setup (makes no difference).
When DNS name resolution via the router fails, all computers on the network fail to access the Internet.
The timing of the problem doesn't coincide with the monitored with the monitored burglar alarm "phoning home".
Any suggestions on what the problem is or what to try next?
Michael _______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
On 11/01/2008, DrWho? <x_files_(a)ihug.co.nz> wrote:
I have an ag300 and the DNS forwarder is a bit broken so you are better of not using it and stick with putting the DNS entries on each PC.
The device uses a very old 2.4 kernel and a very buggy DNS package.
That doesn't sound too good. I'm wondering what will happen if I decide to go for VOIP from my ISP. Don't want to have to reset the router every day. Michael
I have an ag300 and the DNS forwarder is a bit broken so you are better of not using it and stick with putting the DNS entries on each PC.
The device uses a very old 2.4 kernel and a very buggy DNS package.
That doesn't sound too good. I'm wondering what will happen if I decide to go for VOIP from my ISP. Don't want to have to reset the router every day.
As the parent posted suggested, hardcode your DNS entries and you'll be fine. This seems to be a common thing to if you have a DLink DSL router, but this is the first time I've heard of a Linksys DSL router being similarly broken.
On Jan 11, 2008 3:54 PM, Daniel Lawson <daniel(a)meta.net.nz> wrote:
As the parent posted suggested, hardcode your DNS entries and you'll be fine.
This seems to be a common thing to if you have a DLink DSL router, but this is the first time I've heard of a Linksys DSL router being similarly broken.
I think you'd have a good case under the Consmer Guarantees Act to get this fixed/replaced as not fit for purpose. I have a faulty DLink, got the source code and identified the package that was causing this bug. I even offered to fix it for DLink but got no response, so I just hardcoded the DNS. Still might do it one day... There is a bit of flak in the kernel community how embedded Linux users aren't really trying to fix bugs, keep up to date and get involved in the community. I guess these are a prime example. Ian -- Web: http://wand.net.nz/~iam4/ Blog: http://iansblog.jandi.co.nz
As the parent posted suggested, hardcode your DNS entries and you'll be fine.
Usually you can get into the router's DHCP config and change that to provide your ISP's DNS addresses rather than the router's IP. This is a much better solution that 'hard-coding' the DNS addresses on each PC.
On Jan 11, 2008 5:21 PM, Bruce Kingsbury <zcat(a)wired.net.nz> wrote:
As the parent posted suggested, hardcode your DNS entries and you'll be fine.
Usually you can get into the router's DHCP config and change that to provide your ISP's DNS addresses rather than the router's IP. This is a much better solution that 'hard-coding' the DNS addresses on each PC.
Thanks Bruce - don't know why I didn't notice that earlier - works a charm. -- Web: http://wand.net.nz/~iam4/ Blog: http://iansblog.jandi.co.nz
participants (5)
-
Bruce Kingsbury -
Daniel Lawson -
DrWho? -
Ian McDonald -
Michael McDonald