cancel
Showing results for 
Search instead for 
Did you mean: 

Conflict between Home Hub and Thompson Gateway routers

FIXED
shermans
Pro
Posts: 1,303
Thanks: 101
Fixes: 3
Registered: ‎07-09-2007

Conflict between Home Hub and Thompson Gateway routers

I have recently installed a BT Home Hub successfully.  However, my house is very long with very thick walls - two old cottages.  To obtain WiFi coverage, I have to piggy-back a second WiFi router using an Ethernet network between the two routers.  It has worked successfully for years.  All other system like TP Links etc. just do not give satisfactory coverage.

However, I have hit a problem with the BT Home Hub, because it uses the same http://192.168.1.254 address as the Thompson Gateway.  My previous Linksys router used http://192.168.1.1.  There is therefore a conflict between the two routers, I suspect because the system does not work.  I have tried to ensure that DCHP is turned off on the Thompson Gateway router.

 

Any suggestions ?

 

Thanks.

 

 

8 REPLIES 8
ReedRichards
Seasoned Pro
Posts: 4,927
Thanks: 145
Fixes: 25
Registered: ‎14-07-2009

Re: Conflict between Home Hub and Thompson Gateway routers

Unless your Thomson gateway is very very primitive it should be possible to change its base IP address.  Give a computer a temporary fixed IP address (e.g. 192.168.1.20) then connect it directly to the Thomson and change its base IP.  I had to do this a few months ago and because the Thomson router I was dealing with was pretty primitive I had to create a file of the settings, edit the file and then read it back.  This procedure was described somewhere on these forums.  Any new IP address on the range 1 to 63 should be okay.   

Mustrum
Community Veteran
Posts: 3,559
Thanks: 1,056
Fixes: 77
Registered: ‎13-08-2015

Re: Conflict between Home Hub and Thompson Gateway routers

Its very easy to change the IP addresses on the Home Hub, just go to Advanced Options - Home Network - IP Addresses, and chose the 172 range, or you can choose your own range, however don't forget to leave the first 64 for BT's internal stuff (WiFi).

ReedRichards
Seasoned Pro
Posts: 4,927
Thanks: 145
Fixes: 25
Registered: ‎14-07-2009

Re: Conflict between Home Hub and Thompson Gateway routers

The first 63/64 IP addresses are just left vacant for use by static IPs.  AFAIK it's nothing to do with "BT's internal stuff".

Browni
Aspiring Hero
Posts: 2,673
Thanks: 1,055
Fixes: 60
Registered: ‎02-03-2016

Re: Conflict between Home Hub and Thompson Gateway routers

Yep, nothing to do with BT's internal stuff.

My Thomson/Technicolour routers when I was with O2 then Sky, and now my Plusnet Hub One, all use the same IP ranges and my PC has had the same static IP of 192.168.1.63 all along!

shermans
Pro
Posts: 1,303
Thanks: 101
Fixes: 3
Registered: ‎07-09-2007

Re: Conflict between Home Hub and Thompson Gateway routers

Thanks.  I have tried it on the Thompson and it is indeed easy.

 

However, what IP address can I use for the Thompson ?  My old Linksys was 192.168.1.1 which is therefore easy to remember, but would that be compatible with the Hme Hub in view of the first 64 discussion above ?  The Thompson is the slave router, nit the master which is the BT Home Hub.

Browni
Aspiring Hero
Posts: 2,673
Thanks: 1,055
Fixes: 60
Registered: ‎02-03-2016

Re: Conflict between Home Hub and Thompson Gateway routers

192.168.1.1 would work fine.
ReedRichards
Seasoned Pro
Posts: 4,927
Thanks: 145
Fixes: 25
Registered: ‎14-07-2009

Re: Conflict between Home Hub and Thompson Gateway routers

I suggest you use 192.168.1.20.  That should work perfectly with a BT Home Hub but is large enough to be unlikely to clash if you switch to another router.  Whatever you choose, make a label and stick it on the Thomson router for future reference.

Any address in the range 192.168.1.1 to 192.168.1.63 is extra-compatible with a Home Hub.

 

shermans
Pro
Posts: 1,303
Thanks: 101
Fixes: 3
Registered: ‎07-09-2007

Re: Conflict between Home Hub and Thompson Gateway routers

Fix

Thanks to everyone for their various suggestions and comments which have fully resolved the problem.  Everything is working tickety-boo !