Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[roseway]

Upgrading the firmware doesn't make it a v4 because the chipsets are different. What version do you have?

[jaydog]

     V4.01.20

[kitz]

nope, i have version 4 as i upgraded the firmware lol

so what do i put in under the login details and port in the dmt software?

Theres a tutorial here
DMT v8.

which steps you through the process.

[jaydog]

doesnt tell u what port number to use though or where to get the port number from

[kitz]

whoops I orginally posted the following

"Can I ask if you are certain that you have v4?  This is a relatively new router and not many of that particular version around.  Updating the firmware doesnt upgrade the actual Netgear version - since this depends on the hardware inside".

Then deleted it because I saw roseway had beaten me to it on the next page.

However...  V4.01.20

 V4.01.20 relates to the firmware version of the router - not the hardware version.

To make it confusing Netgears firmware versions for the v3 router are marked V4

All v4 router firmware start with version 5

Therefore if your firware is v4 xxx then you have a DG834 v3

http://kbserver.netgear.com/products/DG834Gv3.asp

[kitz]

doesnt tell u what port number to use though or where to get the port number from

Port 23 is the standard Telnet port used by routers.

[jaydog]

it wont work with port 23 so im guessing my model is not compatible. nevermind.

kitz, how can i avoid low snr and losing sync every evening?

[kitz]

it wont work with port 23 so im guessing my model is not compatible. nevermind.

As mentioned above firmware V4.01.20 is for the DG834G v3 so DMT wont work with that router.

>> how can i avoid low snr and losing sync every evening?

Can we keep that conversation to the other thread please - This thread is about lodges's query about Interleaving and is now going very off-topic.

With all due respect I am very busy atm, but I will always respond to posts where I feel I can help. 
Please also remember there are many knowledgeable members who visit this forum, who are just as capable (and may even have more knowledge than me in a particular area), who will also respond if they can

[jaydog]

sorry, wont bother you again.

[lodge]

Hi lodge and welcome

Hello Kitz and thanks for the welcome. I have not had any luck with telnetting in. I tried both the cat proc/cpu command as per your post and the # cat proc/cpuinfo command from the page you referenced. You are right - the Voyager 2000 was the predecessor to the 2100 and then the 2110.

I tried running DMT but I keep getting a message that there are too many errors and not enough data, so the connection was terminated.

In the meantime, since I first posted my stats now read:

Downstream speed     4992 Kbps           
Upstream speed     448 Kbps
Downstream latency    Interleave
Upstream latency    Interleave    
Trellis coding    Disabled
Loss of signal    901    
Line attenuation    41.5 dB
Loss of frame    8    
Noise margin    9.5 dB
CRC error    15411    
Line up count    4
Total error duration    1898 seconds    

The noise margin has dropeed from 11.5 dB this morning and my speed is about  3600 Kbps atm.

Hope some of this means something. 

[roseway]

You're getting some CRC errors, which suggests that your connection is being affected by interference, and the connection speed is a bit less than it might be. Please read This and see if it helps.

[lodge]

No, I changed filters and went into the main socket after taking the faceplate off, but performance is much the same. Would a new router help?

[roseway]

A new router might help, but it's also possible that the incoming line is a bit noisy. One thing I didn't really notice before is that you appear to have a highish target noise margin (very possibly 12 dB) which would result in your connection speed being a bit less than it might be. This suggests that your connection has been a bit unstable in the past, and the target noise margin has been raised to stabilise it. If this is the case, then a router which is supported by DMT would give you some possibilities to reduce the target noise margin and see how it goes.

I have not had any luck with telnetting in. I tried both the cat proc/cpu command as per your post and the # cat proc/cpuinfo  command from the page you referenced.

Just to be clear, the correct command to type is:

cat /proc/cpuinfo

(although it apparently also works without the leading / in front of proc)

[mr_chris]

(although it apparently also works without the leading / in front of proc)

As you'd know eric, that depends which directory you're in - as a linux user you're used to starting up in your home directory, whereas I know the netgear dg834 starts up in the root directory.

It's always safer to tell people to type the leading /, as this is more likely to work every time.

Not that I needed to tell you that, just clarifying for the thread

[roseway]

Spot on Chris