adsl.tin2tin.net

I have installed a forum into Tin2Tin.net located at /forum.
It looks like, as the current user's passwords are encrypted and the forum used a different password hash, I won't be able to just intergrate both logins for now.

Please feel free to Register on the forum.

With the new forum I have also installed a bug tracker plugin. I have included sections for both Tin2Tin and Tone. This will make it simple for users to submit and track bugs and feature requests

I've given tin2tin.net a new colour and banner fo make the site less 'hackerish' in hue.

The banner is thanks to baking_in_pearls @ Flickr who has some fun and cool photos in their profile.

I'm introducing you all to Tone:

Tone is a desktop version of this site, ie it looks at the stats from your modem and draws pretty graphs. At the moment the analysis is still done on this site but I hope that will all change in due course.

Read more on the news page

I'm introducing you all to Tone:

Tone is a desktop version of this site, ie it looks at the stats from your modem and draws pretty graphs. At the moment the analysis is still done on this site but I hope that will all change in due course.

Tone is fast changing at the moment and I would consider it is in the aplha stages. Here are some of the plots that Tone can generate:

Happy New Year! I didn't really have much time to dedicate to writing more content/utility for the site, I hope that this will change this year and I get more time to work on tin2tin.net.

Bad news first:
The server that I have my VPS on is now full so the CPU time has been limited, this has caused a slowdown in the website and graph generation and I cant aford to pay for a better server package at the moment.

I have fixed a major bug in the bitloading code that only came apparent when the server was under load (ie I have lees CPU time now :( ).

I have working code to the bitloading for Thompson routers that are used by BeThere, O2 and BT. These modems don't have the SNR or attenuation per tone like BusyBox based modems - although I think the older firmwares did, I guess that is progress :(.

New history graphs are now in the members area. Create an account and PM me your IP to have it added to the account.

I have sped up the graph generation for the tone graphs from about 20 seconds each to about 5 seconds. This was done by moving away from an abstraction layer (jpgraph) to do the plots and draw the plot directly using PHPs GD support to render a temp image. The image is then loaded into the jpgraph as a plot background. I have also implemented a cache/check/display so the graphs aren't drawn on each page call unless the cache is older than 15 min (was 60 min but as the graphs are now drawn faster I feel this is ok). Unfortunatly the call to the graph still has to do some of the DB calls because of the way the images are sized (1px/test + borders) and the way jpgraph initializes a new graph.

As well as writing new graph code and adding content to the account section, I'm cleaning up the site's code to make the upkeep easier, and to cut down on the amount of code. In the first ~10 scripts I have managed to remove, or place into includes, about 200-300 lines of code. This will make my life easier and will make the php a bit faster - this is important in the scripts that poll members' ADSL2+ routers and in the scripts that generate the graphics.

I have coded a remote checker (at the moment it is tested to work for only the DG834 GT and v4, but any modem that uses `adslctl` should work as well) that does nice analysis of the ADSL tones. There is no user front end written yet but, if you would like to have your line tested, PM in the IRCs and I'll add an account to start the testing. The frontend to test your line is in the Account Management section under Hosts - enjoy.

The new tone tools will generate the graph to the right for attenuation, bitloading (the one to the right is bitloading, and you can clearly see where an un-filtered phone was fitted to the line) and the real SNR at the tone graphed over 24 hours at 5 min intervals. This will probably change to 15 min intervals.

At the moment, these graphs are taking a long time to render. They contain between 2 and 3 million data points and need some optimization in how they are drawn. To help with this I have implemented some image caching and the images are only created when requested, and then only if the cached one is over 60 min old.

These graphs are good to help spot patterns in noise levels and in the bitloading of tones. ISPs use these types of graphs in their line monitoring tools.

You may have also noted a few layout changes. The tabbed content should make it easer to find content, particularly in the stats result pages.

Another new addition is the start of a proper history section for each set of results (see the history of my dsl line). This is still alpha code, so expect things to be broken, change and generally not be fully working just yet.

For those of you who don't have a static IP, the history function will not work so well, so I'm going to create an account system to keep track of your results, and for better management of your results (you will be able to keep tests for more than one line in each account etc).

To complement the history section, I have created an account system. If you create an account all your history data will be available in there, and you will be able to manage much of the data (when I finish the frontends for the functions). At the moment the account section is very incomplete, but new content should be added almost every day.

In the last 24h or so I have managed to break the stats checker. I will endover to get it fixed latter tonight when I get home, so it should be opperational again by the morning of the 24th.

Sorry about any inconveniance caused
Charles (Blueether).

Have had issues with image cahcing so removed all history graphhs, these will need to be regenerated by visiting the page they `live` on. Sorry if you use them in a forum post or sig.