I have a network wired connected heatpump with a static IP address on my LAN, my son's Nintendo Switch has an identical MAC address.
Even though it connects via Wi-Fi from an access point, it refuses to connect to the internet. I can get it to see the local network and it appears briefly in the access point log but will not connect out to the internet. It would seem impossible to alter either bit of kit's MAC address.
Any ideas how I can get them working?
I have turned off MAC filtering but all that achieved was enabling the Switch to connect to the network, it could not make the next step to the internet.
Update: The MAC in question is 98:e8:fa:53:c1:01 and is the same on both the Nintendo Switch and the Nibe Heat pump. I keep all my permanent devices locked on static IP addresses (from a reserved list) and hardwired back to the router, there is a uplink to my wireless Access point (Ubiquiti) which then serves both main and guest WiFi networks with its own DHCP server function using a specified range not used anywhere else on my networks. I had thought that giving the switch its own static IP address might work but although it appears in the WiFi log it refuses to connect and it looks like the MAC id takes precedence over the static IP address I assigned it.
@Tonny, the VLAN option might work as the Ubiquiti has this capability, although I have never explored it before – so will give that a try, wish me luck. Otherwise I agree with you about changing the NSwitch although it is over three months since we got it (this Christmas was the first time we tried the internet connected aspect of it) so Currys may not play ball. (Sorry for the duplication of the question but the original was not showing up on my account and was very hard to search for every time.)
Best Answer
Use a router to create a second subnet for your heatpump (or alternatively, for the Wi-Fi devices). MAC addresses are only relevant within the same L2 network they're on.
If you insist on having everything on a single subnet, the only other option which could help is a switch/bridge with "layer-2 NAT" function, placed like a firewall between the heatpump and the rest of the network. For example a Linux software bridge could probably achieve this via 'ebtables', and most Mikrotik RouterOS devices have L2 NAT under '/interface bridge nat' as well.
Without doing either of the above, trying to keep both devices in the same subnet will be nearly impossible, as every single switch or Wi-Fi access point will be constantly changing its mind about where to deliver the packets, and whenever they get delivered to the wrong device it will kill the unrecognized TCP connection (which is normal behavior).
(Note: Even with two subnets, if you try to do this using VLANs, it can still cause trouble if the network switches don't have IVL...)