![]() ![]() ![]() |
|
Yyrael:
Interleaving is always off with VDSL, VDSL profile automatically tweaks your interleaving to suit. In terms of ways to resolve it the only thing you can really do is follow the Helpdesks instructions =/Out of interest did Chorus put in Cat 5 from your ETP to jackpoint?
Inphinity:FEC errors can *usually* be ignored, because they're simply an indication of how many packets have been corrected, essentially. But this is a monumentally high count, and very one-directional. Ehile it's out of context without details on total packets transferred etc, I suspect that the line quality is very poor (you're probably quite far from the cabinet, or there's an issue somewhere), and most of the data you're transmitting is having to be retransmitted multiple times - thus the sluggish internet response. As a comparison, I currently have ~200k upstream FEC errors with just on 3 days uptime and 80GB transferred. Those line attenuation values are, imo, alamringly high also, and reinforce the idea to me that you are either too far from the cabinet, or have wiring issues. Bear in mind, a faulty modem could potentially cause similar symptoms, but is not likely. I'd suggest getting one of the Telecom guys on here, like michaelmurfy, to check your line stats etc if they haven't already.
nossi: Upgraded to VDSL today. everything working fine (ADSL speeds) with the Telecom connection when Chorus guy left around 11am, but things stopped working around midday and still not restored at 8pm despite a few calls to Telecom Helpdesk, thankfully we have dual connection to TelstraClear/Vodafone.
bot:
The cable the Chorus guy used from the ETP to the jack point is not cat 5. It looks like normal phone cable.
Is that right?
bot: Also, I'm not sure why it reports the data transferred as 0/0. It hasn't been used much but 0B?
Quick google search gave me:
http://www.speedguide.net/articles/how-to-set-a-wireless-router-as-an-access-point-2556
Quick skim seems to look fine :)
Inphinity:
Since your objective seems to be to have a separate AP for older devices so as not to impact performance of the N network rather than to extend the range of an existing network, yes, you should use a different channel and a different SSID. Also, bear in mind you should ideally only have one DHCP server running within a given network - most routers/APs will have an option to DHCP Relay from an existing DHCp server (which in this case would be your Thompson).
So, for example, you have have your TG589 at 192.168.1.254 running DHCP, with it's Wifi using channel 5 and SSID Wifi1. Then, you could have your other device at 192.168.1.253, with it's Wifi using channel 10 and SSID Wifi2, relaying DHCP requests to 192.168.1.254. In this example, you'd need to have the LAN ports of the respective devices connected together. You don't have to use the specific IPs, channels etc, of course, it's just an example.
Inphinity:bot: Also, I'm not sure why it reports the data transferred as 0/0. It hasn't been used much but 0B?
It will probably show 0/0 transferred under the DSL Connection statistics, but will show the actual values under the Internet Services statistics.
“The modern conservative is engaged in one of man's oldest exercises in moral philosophy; that is, the search for a superior moral justification for selfishness.” -John Kenneth Galbraith
rb99
|
![]() ![]() ![]() |