This topic

The dreaded IPC-6023 using Google Wifi

RichieCat — Thu, 08 Apr 2021 22:47:02 GMT

I had FTTP 500/73 installed last week and today I received my Youview box .

I excitedly set it up and since then I've spent several hours being frustrated and several hours browsing to find out my Google Wifi mesh network doesn't seem to be currently compatible with BT IPTV requirements?

I've tried all the suggestions I can find to get a native solution but nothing works and with 5 'mesh pucks' around my home I'm loathe to remove all that 'coverage' just to use 1 SmartHub2....especially as my home is also pretty 'smart' and Google Assistant/Nest/Smartthings is all well pretty integrated.

So, at the moment I'm either :- cancelling my BT TV and going back to Sky or (more probably) digging a bit deeper and trying to get a 'not too clunky' workaround....Best/easiest option so far seems to be use the supplied SmartHub2 in bridge mode and let it handle the modem/VLAN functionality then connect my Google primary to a LAN port and continue to use the pucks for Wifi and Ethernet..

Long story short HOW??? Is it just a case of connecting the Samrthub WAN port to the ONT and then turning off 2.4 & 5Ghz wifi and disabling DHCP in the Smarthub admin page before connecting the Google primary to an ethernet port ...or is there something else I need to do like put the Youview box on a direct wired connection to the SmartHub2 and then configure it to be in a DMZ off the network? All options are available as I can patch various CAT5 structured cabling together to make any necessary 'runs'

Thanks in advance

Re: The dreaded IPC-6023 using Google Wifi

RichieCat — Fri, 09 Apr 2021 05:52:15 GMT

Bump

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 07:25:32 GMT

Connect the SH2 to the ONT as normal. Connect the YouView box to one of the LAN ports on the SH2.
Confirm YouView IP channels work ok.

Assuming everything is good at this point then you can turn off WiFi on the SH2 in favour of using the Google WiFi, but make sure you turn off DHCP on the Google WiFi settings - let the SH2 continue to manage that. You don't need to do anything with DMZ.

Re: The dreaded IPC-6023 using Google Wifi

RichieCat — Fri, 09 Apr 2021 09:17:18 GMT

@DarrenDev

Thanks for the reply

The Youview box does work ok if connected to the SH2 so putting the SH2 straight after the ONT and upstream of my Google primary puck is the initial plan with both the Youview main box and mini box both connected directly to the SH....now the wrinkle....

Is there any way to let the SH2 assign IPs to the 2 Boxes and just my Google Primary and then let the Google primary be DHCP master for WiFi AND everything that's wired downstream? I've got something like 45 clients some with static IPs and it seems easier to leave to rest of a fully functioning network alone?

Eg could I just change the login protocol in the Google primary from PPPoE to DHCP and let it get and use and share an IP from the SH2?

I don't want to end up with Double NAT issues if I can help it that will affect eg PS5 multiplayer

Re: The dreaded IPC-6023 using Google Wifi

licquorice — Fri, 09 Apr 2021 09:32:13 GMT

You basically have 2 choices, you either have double Nat or just one DHCP server. You can't have 2 DHCP servers without double natting. If the static IP addresses are true static addresses, i.e they have been set on the device itself, it doesn't matter which device has the DHCP server as they won't be requesting addresses anyway.

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 09:37:21 GMT

If you put the Google WiFi into DHCP mode but then put it into the SH2 DMZ, that should resolve the double NAT issue. You can leave both DHCP servers active in that situation, as they'll be seen as separate networks.

Re: The dreaded IPC-6023 using Google Wifi

RichieCat — Fri, 09 Apr 2021 12:33:44 GMT

@DarrenDev

That sounds like plan A 👍🏻

The only compromise is I'll either have to hand over the CAT5 I had running to the loft for my drum kit and Mac mini to the youview mini box. Or fit an 8W switch so I can pick up the Mac Mini and Youview mini box too which means the Mac mini either gets to keep an ethernet connection but on a different network via the switch to the SH2 or I move one of my Google pucks to the loft and mesh the Mac mini onto the Google WiFi to keep it with everything else

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 12:47:21 GMT

That obviously depends on whether you need anything to be accessible on the LAN. e.g. a NAS or media server, or if you want to cast music from your Mac to the pucks.
Personally, I'd go all-in on the Google Wifi, and just keep the BT TV box on the outside doing its own thing. Much simpler.

Re: The dreaded IPC-6023 using Google Wifi

licquorice — Fri, 09 Apr 2021 13:09:07 GMT

@DarrenDev wrote:
If you put the Google WiFi into DHCP mode but then put it into the SH2 DMZ, that should resolve the double NAT issue. You can leave both DHCP servers active in that situation, as they'll be seen as separate networks.

As they will be in separate networks, surely you will still be double natting, can't see how you can avoid it.

Public IP > private IP n/w1 > private IP n/w2

Putting the Google Wifi in the SH2 DMZ just obviates the need to forward every port on the SH2 surely.

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 13:08:49 GMT

By putting the Google WiFi router into the SH2 DMZ, it becomes directly addressable by the public IP.

Re: The dreaded IPC-6023 using Google Wifi

licquorice — Fri, 09 Apr 2021 13:13:45 GMT

But the SH2 still needs to translate the public IP address to the private address of the Google wifi to know where to route packets surely.

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 13:20:51 GMT

Yes, but it can do it on a 1:1 mapping - no manual management of port forwarding on the outer network, allowing UPnP on the inner network to work as it should.
Is there an issue with double-NAT other that port forwarding that also needs to be addressed?

Re: The dreaded IPC-6023 using Google Wifi

licquorice — Fri, 09 Apr 2021 13:29:27 GMT

1:1 mapping or not, it is still translating a public IP address to a private IP address to reach the Google WAN where it will be translated again from one private address to another.

I have no idea of the problems or not regarding double port forwarding as opposed to double NAT, but they are not the same thing surely. As said previously, putting the Google WAN IP address in the SH2 DMZ just avoids port forwarding not natting.

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 13:39:16 GMT

So you're just arguing semantics?
If so, then I'll point out that I said "should resolve the double NAT issue" ... not that it'd remove double-NAT.

Re: The dreaded IPC-6023 using Google Wifi

licquorice — Fri, 09 Apr 2021 13:44:18 GMT

No, its not semantics, its accuracy of terminology which the gaming fraternity seem to have subverted with their various shades of 'NAT'. To me NAT is NAT, Network Address Translation, there can't be more than one type. Port forwarding is port forwarding and is not the same as NAT.

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 13:47:50 GMT

"No, its not semantics, its accuracy of terminology"

Surely an oxymoron?

Re: The dreaded IPC-6023 using Google Wifi

licquorice — Fri, 09 Apr 2021 13:50:50 GMT

I think you need a better dictionary.

Calling a car a motorbike is not semantics.

Re: The dreaded IPC-6023 using Google Wifi

DarrenDev — Fri, 09 Apr 2021 13:55:47 GMT

OK, well the problem raised has been (hopefully) solved. My involvement ends here.
Feel free to pursue your issues with the gaming fraternity and their inability to correctly articulate their technical issues.

Re: The dreaded IPC-6023 using Google Wifi

RichieCat — Sat, 10 Apr 2021 14:48:34 GMT

@DarrenDev @licquorice

Hey guys, I've just noticed the ensuing debate, I hope it's healthy.

For info this morning I've been busy patching cables and running tests.

I set the SH2 up with no WiFi and only 3 IP addresses in its DHCP range. The first address I put into the DMZ and then I told my Google router to use that IP for a Static connection. The second address services the Main BT Box via a direct CAT5 link and the third address is straight to the BT Mini box .. This cures my IPC-6023 error on the BTTV boxes and allows my previously connected Google clients to continue on that SSID/CAT5 network...

The only downside is the DMZ suggestion hasn't had the originally proposed benefit of avoiding Double NAT so my PS5 now shows "moderate" instead of "Open"... I'll see if there's a tangible difference over the next few days and either live with it or maybe add a 4th IP to the SH2 DHCP range and make a direct connection from the PS5 to SH2...

Anyway thanks for the help, I've got a working and useable solution for now

Re: The dreaded IPC-6023 using Google Wifi

jbalmford — Mon, 30 Jan 2023 21:38:18 GMT

Hi,

I have recently moved over to BT from Virgin. I have Google WiFi with a main 'box' and then one further Google WiFi 'box' elsewhere.

Everything is working fine, until I try and get the BT TV to work (sounds like the same issue to me as experienced on this forum post, hence the post!). What options do I have to resolve this? I am a true novice, so will need step-by-step instructions please...

I am happy to get rid of Google WiFi, but only if I can rename the BT SH2 to be the 'same' as the Google WiFi to save resetting 25+ connections on devices.

Any advice welcome, please...

Thank you!