If it's weather dependent then it could just be a bit of poor quality wire somewhere where the rain is getting in. (Apparently a common problem. This was the problem in my friend's case.) Most likely from your house to the first junction box. If this is the problem then you somehow need to trick Clara/BT/Openreach into replacing that bit of wire, or the casing which is letting the water in.
The trouble is, any one explanation like this only has about 10% chance of being right... Might help if you kept records of when it functions well and when it functions badly. (To see if it is correlated with weather, street lights, neighbours using radio equipment...) You could have a system where it pings some suitable address every minute and adds the result to a log file to be analysed later.
The only way I can see if your router does not have a command for it is to ask your ISP to request that BT set a higher target SNR margin for you line.
I note that you keep referring to SNR, it might be that actually you have a 6dB margin set and the router is reporting relative to this, so maybe it means 3.5dB SNR on top of the requested margin. Not all routers report this information in a standardised manner.
No, the MSR is used to set the BRAS limit for throughput in the ATM network, by design ATM networks aim for minimum delay and minimum buffering so if the incoming data rate is higher than the line sync rate all the network can do is drop the excess packets and hence you get lots of TCP retries.
You didn't actually think that any of this was for your benefit did you ;-)
Er..well ultimately I thought the whole broadband thing had to be for the customers benefit ..or no one would buy it ;-)
Anyway finally got sesible e-mail from Claranet. I have asked them to get the SNR reset upwards on the DSLAM. If that doesn't work the router is the problem.
Been thinking about the interference..cold clear high pressure=worse interference. MW/LW radio?
Anyway it's largely immaterial. Wherever its from I need to be above the noise floor.
I have no idea what it was. I stumbled through the totally non documented telnet CLI interface, found the itex section, which dealt with all the ADSL stuff, and tried various things until one made a difference!
Googling "itex enhance" produces 3 hits (as I type this). Two are followed by nothing relevant, one is followed by "(try 0)". Perhaps Google should offer an omni-configurer based on that principle.
The Natural Philosopher wrote in news: snipped-for-privacy@proxy02.news.clara.net:
As I have posted previously when I pointed you to the 'itex' command, the CLI interface is well documented - just not by D-Link. More accurately, there is indeed a Technical Reference Manual, but D-Link have never (to my knowledge) made it publicly available. [Aside: Frankly, that's typical of all manufacturers of consumer class routers]
The DSL-504 is based on the GlobespanVirata Helium 210-80 communications processor running the ATMOS embedded operating system. There is a wealth of doumentation on ATMOS - but it's generally not accessible to the public, unless you fork out for a development system. It's also not helped by the company having been acquired by Conexant, who have obsoleted the old GlobespanVirata product lines...
However, the Console Commands Reference Manual is readily available, so no problem there. The problem lies with the modem section of the router, which is based on an Integrated Telecom Express (ITeX) chipset (hence the 'itex' command). Unfortunately ITeX is defunct, so availability of info on its products is minimal, and the ATMOS CLI manual is generic and doesn't cover the commands for the modem section which is product and manufacturer specific.
The issue isn't helped by the fact the D-Link uses ATMOS 7 in that range of products (which includes the DSL-504, DSL-604+, DSL-300G+ all of which are now obsolete but otherwise good, reliable products) and not later versions for which the documentation is more abundant.
Don't forget to commit your config change made via the CLI to flash memory. The commands for this are (with comments in [...] backets): home [get back to the top level commands] config save [confirm the change to the flashfs filesystem] flashfs update [commit the filesystem to flash memory and reboot]
Pleased to hear you've got it working.
Kind regards
[Note: to the poster who tried Googling on "itex enhance" - be aware that one of the links that this turns up is misinformed in his attempt to advise someone on how to deal with a DSL-504G. Despite the similar names, the D-Link G-series products are based on the entirely different GlobespanVirata Viking chipset with an entirely different CLI (but one which is also well documented - again not by D-Link, but to be fair they did publish a little more this time]
There was no syntax for anything, no explanation of what any command actually did, and working from the miniscule help inside the thing, no way to eell what you are doing.
Many of the commands did nothing visible.
More
Not true. e.g. There IS a command 'itex getsnr' Yes, its in the manual. It waits a few seconds, and returns nothing. Write only memory update? possibly :-)
Excatly.
#telnet 192.168.0.254
Trying 192.168.0.254... Connected to 192.168.0.254. Escape character is '^]'. password: logged on; type `@close' to close connection.
192.168.0.254> itex
192.168.0.254 itex> enhance 0 Change will have no permanent effect after restart unless you config save.
192.168.0.254 itex> home
192.168.0.254> config save Saving configuration...Configuration saved.
192.168.0.254> itex line down Deactivating line...
192.168.0.254> itex line up
192.168.0.254> flashfs update Updating Flash filing system ... done
192.168.0.254> @close
Not to mention that there at least two hardware versions and several different firmware versions of this router.
I THINK from hints in the research, that here is another version of ADSL
- ADSL enhanced? and the enhance switch may be to set the thing up for that. ADSL or DSL max is what BT uses...or possibly ADSL 2 but AFAIK the router does not support that.
HomeOwnersHub website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.