Community Updates for the DG834GT

[James67]

Originally Posted by Monday

I did but it keeps rejecting the user name and password

Well, that's rather odd. It works absolutely fine for me, and not just for the default sky password, but also when the password has been set to a different string, and when the password is blank. It's hard to see why it could fail, other than as a result of... human error.

Try temporarily reseting the web interface password to a simple string like abcd and see if you can telnet in with that. Remember the only login name that is accepted is admin, and both the login name and the password are case sensitive.

[Monday]

[James67]

I've released the CU2.03 firmware image. This has a bug fix for an issue on the "Wireless Station Access List", and updated ADSL driver code.

To download the new firmware, please use the links given in the first post of this thread.

[Monday]

any fixes for the my telnet problem?

[James67]

I think I know what the problem is. It's a problem with both Windows XP and Vista, and in fact the problem was there even in the standard Sky firmware, but because Mognuts enables a password-free telnet server, you might not have noticed, and you wouldn't have had a problem.

Basically what's happening is that every time you you press the Enter button on your PC, Windows sends a "Carriage Return" character and a "Line Feed" character. The problem is that Linux regards that as two separate "end of line" characters. So you type in admin then press Enter, but the router thinks you've pressed Enter twice, which means it thinks you've typed the login name and a blank password.

You can work around this problem by typing Ctrl-J after entering the login name and password, instead of pressing Enter.

I'll see if I can fix this problem. The problem is likely to be in the utelnetd program (it's supposed to negotiate with the PC issues like how the end of a line of text is signalled), but like I say, it's always been there.

[James67]

I've released a new version of the CU2 update:

1. Telnet problem has been fixed
2. After changing fixed DNS settings, a reboot is no longer required

The new firmware is available from the following links:

• CU2.04 flash image
• CU2.04 source code kit

[Monday]

Originally Posted by James67

I've released a new version of the CU2 update:

1. Telnet problem has been fixed
2. After changing fixed DNS settings, a reboot is no longer required

The new firmware is available from the following links:

• CU2.04 flash image
• CU2.04 source code kit

Nice just flashed it..seems to be working "ok" but am i right in thinking these are using the netgear drivers?

Cause the Sagem ones seemed to hold the connection with an SNR or 1 or 2 these seem to drop out on 3

[James67]

I can't really account for the difference. All releases since CU2.02 have the Sagem ADSL drivers in them. You can tell from the ADSL Firmware Version on the Router Status page:

• Sky DG834GT (V1.02.28) - Version A2pB018e, built 2005-05-23
• Sky DG834GT (CU2.01) - Version A2pB022c, built 2006-11-10
• Sky F@ST2504 - Version A2pB023c, built 2007-04-16
• Sagem F@ST2404 - Version A2pB023f, built 2007-05-19

The ability of a router to hold a connection depends on so many variables - the nature of the increased noise, other sources of noise, etc, etc. Realistically, it's difficult to say that a specific driver will always hold a connection down to precisely 1.75dB or anything like that.

[hellbelly]

Hi

I have a DG834GT as a spare router so thought I would play around with this custom firmware just to see what was on the extras tab. I just flashed CU1 and that worked fine, I flashed CU2.04 and wireless stopped working, my laptop and PC can see the SSID, I try to connect and it prompts for the WEP key that I set (WEP as not all my devices work with WPA) and they both get stuck on acquiring network address.

I assigned a manual IP address to the laptops wireless NIC and there's still no communication. If I flash back to CU1 or the Sky firmware then it all works fine.

Any ideas? I'm not sure if it's a bug with the CU2 or if I'm doing something wrong?

ta
Pete

[James67]

Yeah, I didn't bother checking WEP on CU2 - it might well be broken. There's probably not much value in me trying to fix it, what with Sky's new firmware coming out soon.