To start I connected just my pc to the Home Hub.

Reset router and insalled 6.2.2.6.
Logged into router changed password.

Switch to BT Home Hub Modder.
Added route access.
Stop BT Auto Update
Set other Voip Provider
Route Internally Hack

When route internal hack was selected, I set my routers IP as 192.168.0.1.

I then closed BT Home Hub Modder.

I then needed to log into admin page and deselect DHCP Server and edit static IP from 192.168.1.254 to 192.168.0.75 (one from my routers range).

Obviously when I set disabled DHCP server and changed the BT Home Hubs ip, I needed to temporarily use a static ip in the new range on my pc's nic.

At this point, I connected the Home Hub to my lan and reconnected my pc to the lan and also and reset my nic to obtain an ip automatically.

I had data light and wireless lights on, but no phone.

I logged into the home hub and enabled telephony as there was no tick. Is the fact that there is no tick a red herring? Is it enabled but no tick has been added to the gui?

Anyway still no phone.

What was needed was this line in the ip.ini

ipconfig addr=***.***.*.*** preferred=enabled primary=enabled

where ***.***.*.*** is the new ip address of the home hub.

I think if you do not change the ip address of the home hub then this line is not needed.
Since my router is on 192.168.0.x range then this line was the key for getting it to work for me.

This is an extract from my ip.ini

ipadd intf=LocalNetwork addr=10.0.0.138/24 addroute=enabled
ipadd intf=LocalNetwork addr=172.16.1.254/24 addroute=enabled
ipadd intf=LocalNetwork addr=192.168.0.75/24 addroute=enabled
ipconfig addr=192.168.0.75 preferred=enabled primary=enabled
rtadd dst=255.255.255.255/32 gateway=127.0.0.1
rtadd dst=0.0.0.0/0 gateway=192.168.0.1 intf=LocalNetwork

So I think you could add a line to the Route Internal Hacks that when you choose the routers ip, then could you also change to static ip + select a new one (use this to create preferred ipconfig) and disable DHCP server. Maybe warn the user that after the operation has carried out they will need to tepmorarily change to static ip on the pc's nic to proceed or simply at this stage connect to their pc and homehub back to their lan.

I'm not sure if any of this is needed if the user is going to use the home hub on lan with the ip range of 192.168.1.x

Also I noticed that the wireless is still on when the Routes Internal Hack mentioned wireless will be disabled.

I hope this info helps

dewi

Hi, I will try and add something along those lines in the next version. Thank you very much for taking time to suggest improvements, it's much appreciated.



The actual wireless interface isn't disabled, and therefore the light stays on, but the route internally does something to the routing that prevents with any client connected to the wireless access point from communicating with the network. I was most annoyed to discover this when I wanted to run the Home Hub as a voip ata, and as a wireless access point, but I guess I couldn't have it all!

My wireless access point is working fine
At home I didn't need/want it so switched it off, but this one I have just setup in work I am using it as an extra wifi access point and voip point.



dewi

Oh right, maybe something else was causing issues on mine. I'll remove/change the message on the tool in the next version

not a coder myself but i too noticed some strange behaviour when using the route internal hack.
the default setup of the homehub once the recovery to 6.2.2.6 has been done is too have 3 dhcp pools.
10.0.0.*
172.16.1.*
and the 192.168.1.*
for some reason the hack used the first available ip addresses to allocate to its external interface and wouldn't work.
reseting the hh, i made a few changes before using the hack
1.changed its ip to 192.168.1.1(as was using with hh2(.254) with dhcp as main router)
2. added another external ip of 192.168.1.2
3 removed the other ip addresses and pools(10.0.0.138,172.16.1.254 etc)
then applied the other voip and route internal hacks,hey presto all working.
hth

Thanks for the feedback.

Version 2 is on my summer holiday to do list Sorry about the very long delay folks