Bug on Guest Network Wifi Hub 2

[LognotWd]

Hi,

I have a Wifi Hub 2 with firmware SG4K100206

I understand there is a long standing bug in this release where the Guest Wifi Network clients are getting assigned DNS of 192.168.1.1 despite having addresses in 192.168.8.0/24

Apparently this has been ongoing for months. 

When can we expect a fix? 

Thanks

[Debbie-TalkTalk]

Hi @LognotWd 

Please can you add your name and TalkTalk landline number or account number to your Community Profile.

I will raise this over to our Device Teams to investigate.

[Debbie-TalkTalk]

Hi @LognotWd 

Please can you add your name and TalkTalk landline number or account number to your Community Profile.

I will raise this over to our Device Teams to investigate.

[LognotWd]

Of course. Not blaming you for TalkTalk shortcomings but the fact that you as a customer, did more work to resolve and assist than their own staff is revealing. 
and the fact that the engineering teams took 10 months to come up with a lazy plug to circumvent the issue in the default settings but not being bothered to address the root of the issue is another. 

hope they will do the right thing now. Thanks for your help and waiting patiently for the next revision then. 

[KeithFrench]

OK, but how they write the firmware is down to them, I am just a customer.

[LognotWd]

Perfectly understand that. But in that case this is the fix that was wrong. they shouldn’t have hard coded the default router IP and made a static route to it, but rather use the router configuration, or map the DNS server onto the guest network subnet. 

that fix was sloppy and imperfect, and only works for a default configuration. 

[KeithFrench]

OK, I will report this, but as I say I cannot spare the time to test every facility with every possible IP subnet, just being a customer myself. 

[LognotWd]

Yes I have tried to reset it. It still doesn’t work. 
while I agree it doesn’t need to be on the same subnet, it still needs to point to an address that exists. 

as I just told you my router is on 192.168.0.1 so having guest dns server pointing to a non existing address of 192.168.1.1 (which happen to just be the hardcoded default ip address of the router)  is nonsense. 
it is still a bug that needs to be fixed. 

I need my local network to be on another different subnet that 192.168.1.x for VPN reasons. 

[KeithFrench]

The DNS server does not need to be on the same subnet at all, so long as the router has a route to that subnet. What about say Google DNS on 8.8.8.8, that is not on the same subnet as your main SSID.

Have you tried a factory default?

Now in your scenario, using 192.168.0.0/24, I cannot test every subnet with every facility. I am only a customer, not a TalkTalk employee. It might be a bug when the router is on 192.168.0.0, which is why I am asking you to try a factory default.

[LognotWd]

Hi Keith,

Thanks for the reply but given your config I am surprised this works on your end.

This definitely does not seem fixed on mine,  for the same details you posted above

IP : 192,.168.8.36

Subnet: 255.255.254.0

Gateway 192.168.8.1

DNS : 192.168.1.1

The DNS is still incorrect and in the wrong subnet. 

(Because my router, even on my private network, happens to be on 192.168.0.1, so 192.168.1.1 is completely wrong and shouldn't exist)

Two solutions : either allow a custom configuration where the DNS server address can be customised for the guest SSID, or use the Gateway address as a DNS server and not something hardcoded like 192.168.1.1 

Right now, this is not a fix and results in no DNS connectivity for the Guest network clients unless manually setting their DNS to a public server (cumbersome) or using a VPN...

[KeithFrench]

Hi @LognotWd 

As I thought, it was fixed in V206, but I had to do a factory reset on mine (probably due to test config changes a lot of the time). With both the default SSID & my own SSID, I get internet access:-

IPv4 Address. . . . . . . . . . . : 192.168.8.10(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 192.168.8.1
DHCP Server . . . . . . . . . . . : 192.168.8.1
DNS Servers . . . . . . . . . . . : 192.168.1.1

I am actually posting this via my Guest network.

[KeithFrench]

Hi @LognotWd 

Yes I have, but I am just a customer, I have no access to fix firmware bugs.

[Debbie-TalkTalk]

Hi @LognotWd 

Keith has done a lot of testing for this particular issue and I need to feed this back again to our Devices Team to look into.

I will post back as soon as I have further information.

Thanks

[LognotWd]

Thanks Keith.

Looks like you've been looking into this for the past 10 months if looking at this previous thread : 3024503 

So forgive me if I'm not exactly holding my breath...

[KeithFrench]

Hi @LognotWd 

Myself & @Debbie-TalkTalk are looking into this.

[Debbie-TalkTalk]

@KeithFrench Could you take a look please?

Thank you.