1. I need to have the Smart Hub 2 router / gateway / dns address as 192.168.1.1, because Apple Devices will not connect to the internet by default if those addresses remain as the default 192.168.1.254. (They connect to the network, but never to the internet.)
2. But if I do set the router / gateway / dns addresses to 192.168.1.1 then the network is much flakier than when it's on 192.168.1. 254 — web sites won't connect, connections are dropped several times an hour, and even the safari link to 192.168.1.1 to manage the router takes several attempts at loading.
So, there's obviously two problems / questions:
1. When the router / gateway / dns addresses are 192.168.1.254, it's not sending these details out correctly on dhcpd for the Apple devices to pick them up. But if this is the case then the internet would be alive with BT breaks Apple headlines and it isn't... So what do I need to change to get it working? What tests should I run to find the problem settings?
2. If the addresses are set to 192.168.1.1 then clearly there's a problem with the settings causing the flakiness. Where should I be looking to diagnose the problem?
The problem is that no matter what I do, when I am setting up an Apple device, it will not connect to the internet with the router / gateway / dns set to 192.168.1.254 — initial connection is made, but the next step (connection to Apple's servers etc) never takes place and the installation eventually times out. The only way of proceeding with the installation/setup is to change the router/gateway/dns addresses to 192.168.1.1 -- and when I do that the setup immediately works with no problem.
This behaviour is repeatable and has caused problems with iPads, iPhones, and the internet reset of MacOS, and yesterday, the HompPod — every time without fail, installation/setup hangs until I change the router/gateway/dns to 192.168.1.1.
I could just go with the flow and accept 192.168.1.1 as the router/gateway address, but the problem is that the router is for some reason much less robust on that setting — it's definitely more stable with 192.168.1.254 (though I have been unable to sort out why — all the other settings are as they should be).
It looks as though the Apple devices do not pick up the network router settings properly - in other words, it finds the network itself, but does not change the gateway/dns to 192.168.1.254 as it should.
BTW I've had this problem ever since I received the Smart Hub 2, but changing the network addresses temporarily to 192.168.1.1, then back to 192.168.1.254 (and then giving the devices static IPs so I can manually set the router / gateway / dns to 192.168.1.254) worked well enough that I just lived with it. But now I've bought a HomePod and that option isn't available, so I need to fix the underlying problem...
Does anyone have any idea why this should be, and any suggestions to fix it?
Never heard of that one. I have an ipad and various friends and family have iphones, none of them ever have any problems connecting to my SH2 when they come round. What makes you think that ?
If you're 100% sure that what you say is true then you could try a class B address (say 172.16.xxx.xxx), don't forget to change the DHCP pool accordingly though if you do.
"Never heard of that one. I have an ipad and various friends and family have iphones, none of them ever have any problems connecting to my SH2 when they come round. What makes you think that ?"
Bitter experience! It's something I've had to do about twenty times (new iPhone, iPad, recover MacOS, install BT TV, Apple TV etc on various occasions). It shouldn't happen, but it really does. There's clearly a mismatch in a config somewhere, but I can't find it, despite trawling through every advanced setting.
But aside from the dhcp issue, why is a network based on 192.168.1.1 so flaky? It doesn't make sense, but it’s definitely the case.
I've gone back to .254 now because .1 is unusable. Once I've got over the frustration, I'll try a B class network.
Do you have Private Addressing turned off on your iOS 14 phone for your home wifi? If not do so as this new function in iOS14 causes all sorts of issues.
Other options are :- Turn off Smart Setup and maybe the 5gHZ wifi as the same wifi SSID on both frequencies seems an issue with Apple devices.
That certainly sounds something Apple must have updated recently as I have an old MacBook Pro (but running virtually latest OS 11.4), a work MacBook Air, an iPad Pro (up to date), my wife has a Macbook and iPhone, and all work with the device set with standard .254 as gateway address with no problems whatsoever.
I connect via wifi and cable, sometimes from the same devices (i..e both lan and wifi connected to the sh2). I also have a tonne of other devices connected.
I'd agree, not sure why .1 would be a problem either as the DHCP/DNS. My only thought is what's your DHCP range assignment - if you changed it (and it can assign .1 to another device) again you may get collisions. Also, set a secondary DNS server on all your Apple devices of maybe 184.108.40.206 or 220.127.116.11 etc (free semi-secure dns) - that might make connections more stable.
I'd suggest maybe 2-3 things (you seem to be pretty technical) - check the LAN & DHCP logs when setting to .1 or when apple devices are connecting and look for anything weird - likewise (admin on Mac) console logs.
Also, on a device that works (wirelessly) like a tablet or phone, download 'fing' and scan your network (it's free) and scan for devices on your network and see if there's a clash (more than one device reporting itself on .1) - fing's pretty good at IDing devices too.
Final thought - you don't have ANYTHING else that may be acting as a DHCP server on the same network do you (backup device)? I would expect that to cause issues on all devices and on either .254 or .1 but just in case...
Hope you find a solution!