Is there an ongoing issue with 2Wire Router usage ? Im having an issue .

[Gary]

The dreaded biggy from BT  I'll be happy when its over

[Rik]

Early hours of Tuesday, Gary, with more to come for 21CN of course.

[Simon]

I should just make it to the 15 days for the SNRM to drop, then I suppose they'll bugger it up again!   

[Gary]

Early hours of Tuesday, Gary, with more to come for 21CN of course.

Our exchange is being done for 21CN this year, great  does this work tuesday mean we lose sync as well Rik?

[Sebby]

I think it's difficult to say, Gary. 

[Rik]

The answer is we don't know, Gary, because BT haven't told IDNet.

[Dont mention Talk Talk !!]

My third 2700 (2xSSID) has now been up and running for 13 days, so I don't think the reboot fairy has visited. 

what does this 2xssid mean, do they still make those routers this way ?

James

[Rik]

There is a later model, with dual SSID, meant for the BT Fusion service. These seem to be the ones in the current supply chain, James. They can't take the SBC firmware, but seem able to resist the blandishments of BT using the DNS poisoning trick.

[Dont mention Talk Talk !!]

"poisoning dns "

you have lost me rik. I use the idnet dns servers, am i at risk of this dns poisoning ?

James

[Rik]

Naah. The routers 'phone home' periodically, and reset the login to a BT domain. The poisoning trick is to enter the sites they use in the DNS table, and point them to nowhere. The router looks in the table before asking the DNS servers, finds the addresses and sends the check on a wild goose chase to nowhere. Problem solved.

[Sebby]

Put simply, it's a method of getting around the system BT has for stopping users of other ISPs using their routers. 

[kinmel]

There is a later model, with dual SSID, meant for the BT Fusion service. These seem to be the ones in the current supply chain, James. They can't take the SBC firmware, but seem able to resist the blandishments of BT using the DNS poisoning trick.

DNS poisoning does not work with the Dual SSID with the latest firmware and there is no point in doing it.  Any URLs that are built into the firmware do not refer to the DNS Resolve list.

[Sebby]

So what's the solution for dual SSID models, then, or isn't there one?

[Rik]

Thanks, Kin, and what Sebby said.

[Ted]

I run a dual ssid 2700hgv and As far as i see it, you have to somehow fool the router into letting your username and password be valid and after that you're good to go.
DNS poisoning doesn't appear to work as i and people i know have been auto upgraded regardless of DNS resolve settings.
i wouldn't swap mine for anything, every time i look at the tech pages its like a screen shot over and over, its so stable its boring!!
The only 2 resyncs i've had in the past months have been electrical power cuts.


Happy 2wire user
Ted

[kinmel]

So what's the solution for dual SSID models, then, or isn't there one?

It doesn't seem to matter, updates happen automatically and the router report homes once daily, but as yet to no visible effect.

I am with xild on this

[Sebby]

DNS poisoning doesn't appear to work as i and people i know have been auto upgraded regardless of DNS resolve settings.

So what do you do if DNS poisoning doesn't work anymore?

[Sebby]

It doesn't seem to matter, updates happen automatically and the router report homes once daily, but as yet to no visible effect.

Ah, that would explain it. I wonder what the point of it phoning home each day is if it doesn't take any action.

[Rik]

I run a dual ssid 2700hgv and As far as i see it, you have to somehow fool the router into letting your username and password be valid and after that you're good to go.

Is there a specific technique to that, Ted?

[kinmel]

Ah, that would explain it. I wonder what the point of it phoning home each day is if it doesn't take any action.

I think it's checking for firmware updates, those I have installed for people have always updated their firmware next day.

[Ted]

Is there a specific technique to that, Ted?

There seems to 3 methods to achieve this.
1/ is a firmware hack to allow idnet as a recognized domain
2/ use a java script hack to circumvent the process page
3/ use the wizard to enter username/password.

All appear to work fine and asa i say after that you're good to go

[Sebby]

Interesting; thanks for that.

[Rik]

Care to expand on 1 & 2, Ted? (I know, always after a pound of flesh! )

[Lance]

The first one involves using Opera to view the code, and adding idnet to the allowed domains. When you press the  submit button, it checks this list to see whether you have entered a valid domain.

The second one is entering the javascript in the address bar, in order to get around the validation on the submit button. I used this and it works fine

[Rik]

Thanks, Lance. Why Opera, aamoi?