Use Smart Hub 2 as VoIP client only - no Wifi, no routing

[T_Lancer]

Hi, my parents in-law have just upgraded to full fibre and have had an open reach ONT and new Smart Hub 2 installed.

Currently this works. however originally they had a DSL modem connected to a Netgear Router, which I would like to continue using as it runs the local network Backup server and VPN services.

I would like to know if the SH2 can be configured purely as an IP client connected to the Network behind the Netgear router.

From what I have read, that should work if all you want is an AP.  However it is critical that VoIP continues to function.

So if I disable WAN configuration, DHCP server, WiFi and configure a static IP, will VoIP still work?  Do I need the VoIP login credentials to reconfigure this?  Also having switched from DSL to Fibre, would the PPPOE login details still be the same or would I have new ones?  Can I read these out from the SH2 or do I need to request them from BT (same goes fro VoIP login)?  If the login ist he same, this will make reconnecting the Netgear router that much easier.

I am based in Germany, and have become the de facto IT-Support for my in-laws, which is not always super easy living in Germany, especially now since I have no experience with UK ISPs. But from my understanding, it should all be quite similar.  In fact the setup I propose is the same setup I use in Germany.  I have a Router with VoIP capability (with analog line out) and have it setup only as a client device behind my proper Router.  VoIP works as expected and everything is fine.  I am hoping it is this simple with the SH2 as well.

Many Thanks

[imjolly]

if you want to use DV (VOIP) then the SH2 must be the first connection to the ONT and then the netgear not other way round

the username and password are the same as previously and is same on all hubs

[gspearson]

I have recently installed my 2 year old SmartHub 2 solely for the DV - of which I've had an alert.  The SH2 has its wifi turned off and is connected to my Deco M5 mesh system. 

[T_Lancer]

Thanks for the reply, gspearson.  what did you have to configure exactly?

I assume you would have turned off WiFi, disabled any WAN settings and the DHCP server and set the SH2 IP to a static one within the network you are connecting to?  did you have to do anything for the VoIP settings or did it just continue to work because the SH2 had internet via your main router?

[WSH]

The SH2 needs to be directly connected to the phone socket/ONT for digital voice.  I did mine this way:

Smart Hub 2 (SH2) router settings:

Turn IPv4 DHCP off.  (The addresses here are best set as static addresses but you can use dynamic addressing if you really want).

Set IPv6 DHCP to ‘Stateless’.

Set the router itself to a static IP of 192.168.1.254 and a subnet mask of 255.255.255.0 or /24.  (These settings are its defaults, so you may not need to change anything).

Set the DMZ host to 192.168.1.2  (This helps with double NAT problems or at least it takes care of the port forwarding on the SH2.  There is still address translation happening, however, so you may still have problems with multiplayer games, UPnP etc.  In fact, you only really need this if you have incoming external connections to a server etc.  Personally, I’ve never found double NAT to be an issue and I don’t use the DMZ setting.  If you do use it, note that this setting allows a lot of traffic to effectively bypass the SH2 firewall, so you are relying on your own router’s firewall for security, just as if it was directly connected to the internet).

Turn off the Wi-Fi in favour of your own router.  (This may also be a good security move if you do enable the DMZ host.  I would still expect Wi-Fi traffic on the SH2 to go through its firewall but I can’t be sure how they’ve set it up internally).

Connect the DSL port to the phone socket on the wall or the WAN port, (port 4), to the ONT, whichever is applicable.  If the latter, don’t forget to also enable FTTP Mode on the SH2.  (Again, this is usually on by default).

The DV phone/extension then plugs into the green phone socket on the SH2.

Own router settings:

Turn the IPv4 DHCP on.  Set the range to 192.168.0.2 - 192.168.0.200  (Note the 0 in the third position, making this a separate network to the SH2.  This is deliberate, not a typo.  You can use another number if you want but not 1).

Set IPv6 to DHCPv6 Client.

Set the router itself is on a static IP of 192.168.0.1 and subnet mask of 255.255.255.0 or /24, (if using static addresses.  If dynamic, set it to get an address automatically).

Enable the (E)WAN port and set it to a fixed IP of 192.168.1.2  (This makes your router’s WAN port part of the SH2 network).

Set the gateway to 192.168.1.254  (Again, pointing to the SH2).

And also set DNS to 192.168.1.254, (or whatever you usually use).

The EWAN socket on your own router, (probably no.4), then connects to a LAN port on the SH2.  (NB. This will not work if you use the DSL port on your own router).

Lastly, any static addresses on devices in your own network will also need to match the network address of 192.168.0.x  If you’ve used the range I suggested above, that means the x will need to be 201 or above, of course.

[licquorice]

@T_Lancer As others have said, you cannot do what you are proposing.

The BT hub has to be directly connected to the ONT (optical modem) as the BT VoIP system is proprietary.

If you wish to use a third party router, it has to be the secondary device not the primary.

[michaelkenward]

---

@T_Lancerwrote:

Currently this works. however originally they had a DSL modem connected to a Netgear Router, which I would like to continue using as it runs the local network Backup server and VPN services.

I would like to know if the SH2 can be configured purely as an IP client connected to the Network behind the Netgear router.

Here's what I did with my SH2 and Netgear MR90 router.

The trick is to set up the network so that the Netgear router sits in the "DMZ" of the HomeHub.

In this way, you can use the two routers on the same network without causing clashes. You can also get into the controls of both routers very easily.

The key is to set up the Smart Hub2 with a local IP address that does not clash with whatever the Netgear router is already on.

By default the Smart Hub2 squats on 192.168.1.254. That clashes with the Netgear router which will try to allocate itself 192.168.1.1.

I wanted to keep that IP address as the basis for everything already on my local network. All those fixed and reserved 192.168.1.XXX addresses.

I set my Smart Hub2 to use 192.168.2.1 as its local IP address.

Advanced settings >> My Network

Then in the SH I went to:

• My Devices

Look in the list for your Netgear router's local IP address – in my case, it was on 192.168.2.175.

After I connected things and restarted the network, I went into the Smart Hub2

• Advanced settings
• Firewall
• Configuration
• DMZ On

Look at the drop down and pick the IP address that the Smart Hub2 has allocated to your main router.

Use that as the DMZ address.

Then the Netgear can use 192.168.1.1 as its starting point for the network.

Since doing that all has been well. No conflicts between the two routers. I have turned off the redundant wifi from the Smart Hub2.

Both routers are accessible using the a web browser and the graphical user interface (GUI). Just aim the GUI at their IP addresses, 192.168.2.1 for the SH and 192.168.1.1 for the Netgear.

The HH has scary warnings about the safety implications of letting traffic through its defences, but your Netgear router may be at least as protective, especially of you have signed up for one of its security add ons. I haven't.

I have yet to be forced on to Digital Voice so I don't know if that works. But I would certainly try that before buying yet more hardware.

This is from memory a few months ago. It still works, but you may have to tweak it for your setup.

Here's another guide on what to do:

How to Use Your Router and ISP’s Modem/Router Combo In Tandem

[WSH]

Funny, I thought I'd already said all that?

[michaelkenward]

---

@WSHwrote:

Funny, I thought I'd already said all that?

---

Not really.

You wrote:

Personally, I’ve never found double NAT to be an issue and I don’t use the DMZ setting.

That is not what I said. By a long stretch. I also added screenshots that the user might find useful.

[WSH]

Yes, you do make a good point in so far as it might be easier to alter the IP address on the hub if the network already uses 192.168.1.0

Still seems like duplication of effort, though, but up to you, it's your time.