Got Infinity 2 but have to power cycle modem every 6-12 hrs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
All I can say currently is absolutely wonderful!
After my hopes of getting it today going downhill with the engineer being late, I can finally say I have Infinity that currently works wonderfully.
I'm currently using BT's equipment, that is the OR modem and Business Hub 3. I have a Cisco 887VA which does VDSL2 directly (can connect direct to VDSL2 master socket) and/or PPPoE (if I connect to the OR modem instead of direct), but at this stage I think I'd be best to leave it all alone for around 10 days to ensure the line settles without me disrupting it.
Please read my third post for an update.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
CRC errors on your orignal look a little high and also they are starting to appear on te latest screenshot. Keep an eye on them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
Ok, not sure how I could go about reducing them though. I've performed a quiet line test using an analog phone and I can't hear any buzzing, crackling or popping, so I can't report to BT that I have a line fault necessarily. Fortunately DLM hasn't kicked in any interleaving or speed reductions as a result of a slightly higher than normal CRC errors.
Talking of that. What range would you say the CRC errors should be in a typical day?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
CRC errors come about becasue of corrupted data - such as when noise hits the line and a set of tones cannot be demopdulated correctly.
What can you do ? Very little except ensure that there are no electrical noise generating items close to the phone line and modem.
On a typical day? A difficult question to answer as every situation is different.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
I see. Well in about 24 hours I'll swap the cable back, unless this cable for some reason produces significantly less errors in the same timeframe as the other cable, but I have a feeling the original cable supplied by BT somehow performed a slight bit better.
I'll keep an eye on CRC errors, as well as other parameters of the line such as interleaving depth, noise margins and attenuations, sync speed, etc. So long as I get good throughput (which I am), a good ping (which I am again) and no DLM interference then I'm more than happy. One thing that's still pending, and up to me to figure out of course, is setting up the static IP's on the Cisco router, but that's another challenge I'll work on soon :P.
Thanks for your help so far.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Highlight
- Report Inappropriate Content
The test is over. I would say that the CRC errors occur mostly over night, after midnight, at a much higher rate compared to during the day. I've switched back to the BT supplied RJ11 cable which immediately provides me with the original results I had, e.g. around a 103000kbits/s DS attainable rate. I'm guessing the shorter, shielded and twisted pair RJ11 cable can't handle a very small area of the higher frequencies hence the slightly lower attainable rate on the DS.

- « Previous
-
- 1
- 2
- Next »