"Looking up..." Delay

[Rik]

Yup.

[Sebby]

It sounds like a typical Netgear response, having not read the question at all.

[Rik]

Sadly, yes. Drives you batty, doesn't it. 

[net91]

Surely idnet support will be able to tell you whether your interleaved or not? Having been messing round with a Dg834g v2  this weekend I coudn't find detailed adsl stats either. However one solution,a lot of a faffing required is to use DMT tool , which should give you the info, but I believe your using a mac which would mean installing windows

I have access to a Windows machine that's connected to the router so I could try DMT tool on that.

It sounds like a typical Netgear response, having not read the question at all.

I'm going to try what that Netgear support email suggests just in case, and if it doesn't work I'll email them again and see if I get anywhere. 

[net91]

  indeed Rik.

[Rik]

Frustrating as hell, and there's little any of us can do about it - except not buy in the future, but that doesn't help the current problem.

[net91]

Yup, and my experience with their phone support is no better.

[Sebby]

IDNet should be able to give you your interleaving status...

[drummer]

Don't know if this will work on a Mac, but it worked on Windows:

http://dg834gt.mognuts.com/NetgearRouterUtility.html

Click on "Get detailed modem statistics", then click "Download netgear.cfg", which should download a cfg file.  Open it with a text program that reads formatting.  On mine, line six reads: Channel:   Interleave, so I'm guessing the alternative would be Channel: Fast.

Just a thought.

[Rik]

Thanks, Drummer. 

[net91]

Thanks Drummer, it worked.  

My connection is interleaved.

[Rik]

That explains the ping times, then. Did you see your error counts in the process?

[net91]

_{Bit Errors:   0      0}

Is this it?

[Rik]

No, I was interested in FEC errors, Dan (and how long the router has been 'up').

[net91]

I'm not really sure where to look. I've attached the file to this post.

[attachment deleted by admin]

[Rik]

If I'm reading that right, you seem to have had about 3.25M errors in 41 hours, about 20 a second, in which case interleaving is justified.

[net91]

So does this mean I should just leave interleaving on, or does it indicate a problem with my connection?

[Rik]

Yes, leave it on. It's not a problem as such, it's just that you are picking up enough noise to generate errors. I also have interleaving on for that reason.

[net91]

Ok, thanks for looking at the file. 

[Rik]

NP. Thanks. 

[net91]

I've now closed the case with Netgear support.

[Rik]

Very wise - you could go grey very fast otherwise. 

[net91]

After a few days of using Safari the problem does seem to be affecting it as well. I will get stuck on "Contacting..." for long periods of time.

[net91]

I've spoken to IDNet support again and they've suggested that it may be an issue with my router or the TCIP elements on my computer. They have suggested I try and reset the settings on my router. They've also said that I will need to speak to a Mac engineer about any possible problems with the TCIP elements on my computer.

So I'll give these things a try.

[RichR]

I have the firewall that comes with MAC OS X enabled and the router has a firewall. Which one of these is likely to be causing the problem?

Thanks
Daniel

(I've attached a screeshot of the error message if it's of any use.)

Diving into this very late but there is a typo in your screen shot which is why you're getting "not found" as a response.
It should be
   cat /proc/avalanche/avsar_modem_stats
but you have typed
   cat/proc/avalanche/avsar_modem_stats
note the missing space between "cat" and the first "/"