it is unlikely unless very close to the AP like 10 cms or so but even then very unlikely if the hifi product is complaint to EMC regulations (which include susceptibility and emissions). Wifi is many magnitudes in frequency higher than PLAs and near field strength over distance exponentially falls away with frequency. Wifi is very low power and is lower power than a 4G/5G or 2/3G mobile phone and is relatively extremely narrow band compared to PLA.. so I suspect your hifi is fine. IF there is any issue you ar more likely to hear break through which will be a buzzing type sound.. turn the volume up with no signal from a powered source.. if you hear nothing but a gentle hiss you are fine…
But I personally would not put a wifi access point or mobile phone very close to the head of a sleeping infant.
1 Like
I’m in the states. I have AT&T gigabit fiber to the wall. The fiber gateway is attached to an AT&T provided and provisioned Pace Router that includes WiFi.
I have TP-Link Deco 6e Mesh with an extra remote unit. I have the AT&T Pace router setup in bridge mode (with disabled Wifi, DHCP, DNS, etc) and use the TP-Link Deco directly attached to the AT&T router as the router for my LAN. It’s attached to a Cisco 2960G switch in unmanaged mode, which is in turn attached to another one on the 2nd floor. The 2nd Deco is attached to that, so I have ethernet backhaul between the two Deco mesh nodes on two floors.
I keep the AT&T router hardware in the mix, in the event that I have service issues. In that case I can attach a laptop to the AT&T router ethernet port, call them and say the problem is on their end. If I don’t keep their hardware in the loop they can just as easily lay blame on my hardware and refuse support.
This setup works really well, and unlike with the AT&T router I pick the DNS servers I want to use (Quad9 by my choosing).
1 Like
I have Ubiquiti router at home.
Excellent for their price
1 Like
The only thing with Ubiquiti routers I have found is that their ipv6 implementation as standard can be a bit fiddly with certain ISPs and you need to deploy specific code configurations to get it working. IPv4 is more straightforward and works out of the box.
These days ipv6 is pretty essential if you want performant internet services.
What performant internet services are you talking about?
Avoiding address translation chains and additional router hops … so end to end latency and on certain CDN services actual throughput … of course you might not need or notice these benefits, and so happy to run along on the older ipv4 for everything.
The faster your internet access, the more these can become beneficial, but the internet will support legacy ipv4 only accesses, albeit with a slight efficiency hit on some services. Basic WWW use is unlikely to be noticeable.
1 Like