whatever you guys have done with the latest firmware release on the Homehub 2 has completely messed up my dual-boot Ubuntu-Win7 installation.
Current firmware 184.108.40.206.83.3.18 (Type B)
Last Updated 21/04/11
Ever since Friday when I boot into Win7 then reboot into Ubuntu, Ubuntu cannot aquire an IP address from the router. I have to do a factory reset on the router to get an address. I've 10's of port forwarding setup and this is far from ideal.
What do I do to go back a firmware or who do I contact to get it fixed.
Its a bit pathetic TBH and I'm quite annoyed about this
I've got exactly the same (baffling) problem with my BT HomeHub 2 and Ubuntu 10.10. - worked fine last Wednesday (20th April) and won't work today (26th April). Can see the router just fine but won't connect wirelessly or wired but will connect to BT Open Zone which is enabled on my hub and a couple of other hubs nearby. The OpenZone connection is full strength (which is my hub) - none of the neighbouring connections has ever been a full strength signal. Very odd.
Checked to see if it was my Ubuntu set up by running the machine off the installation disk and got exactly the same symptoms. My HomeHub also updated its firmware some time on the 21st April so, given that nothing else has changed (my windows 7 laptop has continued to work flawlessly) I am driven to the conclusion, like other correspondents here, that the HomeHub update is the culprit.
Ubuntu is growing and it would be good to see BT do some work on this quickly.
there was a firmware update?
that could explain why I'm getting issues.
I had a HUB go bad and mess up my speed.
From about the 20th my hub has been playing the same game as the old one.
Same issue with a HTC Desire Android device, it won't accept an IP via DCHP, set it manually and it connects. Where do I post the complaint too?
Additional info: The firmware on the Home Hub was updated on 23rd April and I noticed the problem the following day.
I have the same problem. The recent BT Hub upgrade appears to have messed up eth0 connectivity in some versions of Linux.
XP still works using wired and wireless connections but Mepis 64bit 11 (RC3), Mint 10 KDE and Gnome are all affected on family computers. Using Mepis I can set up a new wired connection that works until re-boot, then defaults to eth0 and fails to connect.
Puppy Linux (Lupu 525) is unaffected. Is there a Debian link?
This is not a issue I am aware but I am getting this looked into. Once I know more I will post an update on the thread.
I've been suffering the same problem with various forms of Linux, tried all sorts, rolling back to previous kernels etc assuming that an update had broken it. I then found the firmware info in the Home Hub settings and saw that there had been an update on 23/04/11 so figured it must be that. A quick google brought me here and I have now just filled in an online complaint also. It really is not acceptable that Linux is not supported and may even have been deliberately crippled!