swatboy79 wrote:Vectoring is not the same as g.inp. Maybe i missed it but I didn't see any mention of g.inp?
Our engineers have stated they are building a new firmware that will have g.inp support. (I have no doubt once the function is added, our web site will reflect this)
swatboy79 wrote:Vectoring is not the same as g.inp. Maybe i missed it but I didn't see any mention of g.inp?
Our engineers have stated they are building a new firmware that will have g.inp support. (I have no doubt once the function is added, our web site will reflect this)
Attached is firmware version 2.32d.dh61 with g.inp enabled by default (you won't see this function within the web gui), we need someone with a VDSL line that has g.inp enabled on their line to test and confirm.
Edit firmware pulled while we verify option 61 IPOE DHCP lease issue
I'll give it a go, hopefully the Authentication bug has been fixed
I have no idea if G.inp is avaible where I am, does anyone know how to tell, i guess the telnet interface?
Last edited by swatboy79 on Mon Mar 16, 2015 1:24 pm, edited 1 time in total.
I guess since my line does not even require interleaving (D (interleaver depth) is 1, 1)
There is no point in G.INP. Is my understanding correct for those of you who may know?
I really wish BT would get their act together with vectoring, since my line went live i have lost 11mbit on download and 5mbit on upload.
Then BT quickly updates your expected speeds using their Avaiblity checker using your stats to give an ever lower expectation of your line.
Great marketing BT! Only another 14mbit to go before I can just get Plusnet 38mbit capped product and save a few bob!