← All guides

Matter network setup: IPv6, VLANs, mDNS and router settings for Apple Home, Google Home, Alexa, SmartThings and Home Assistant

Matter runs over IPv6 on your local network and finds devices with mDNS multicast, so router settings can affect it. You need IPv6 on the LAN, but not from your internet provider. Keep devices, the hub or controller, Thread border routers and the phone you pair with on the same network or VLAN, and watch out for mDNS forwarders, multicast "optimization" features and guest networks. Home Assistant's Matter docs and Google Home Developers both explain the local IPv6 and multicast requirements.

How Matter uses your home network

Google Home Developers says Matter uses IPv6 for its operational communications, with unicast addressing for reaching individual devices and multicast addressing for groups. In practice, that means your router and access points have to carry IPv6 traffic between devices on the same network — not to the internet, just locally.

Discovery happens over DNS-SD, which runs on mDNS over Wi-Fi. A device that's ready to be added advertises itself with the service type _matterc._udp, and once it's commissioned it's discovered as _matter._tcp — even though the actual transport may be UDP. Google Home Developers and the CSA Matter Handbook both document these service types, and the Matter SDK docs show them in mDNS scan commands. Thread border routers publish mDNS records on behalf of Thread devices so they can be discovered on the Wi-Fi or Ethernet network. Google Home Developers explains that border routers forward only packets relevant to the Thread network. The catch: Matter's link-local multicast doesn't cross LANs or VLANs, according to the Matter Server docs. Discovery traffic has to reach every device, border router and controller on the same network segment.

Router settings at a glance

These are the settings the sources call out, grouped by what they affect.

Work through these one at a time and test after each change. A setting that helps one network can hurt another, and none of the sources here promises a single fix.

Does Matter need IPv6?

Yes — on the local network. Google's help page says IPv6 must be enabled on your home wireless network, and warns that without it, setup may seem to succeed at first but control and other functions eventually fail. Google also notes that some Matter devices still work with IPv4, but they need IPv6 connectivity to communicate with all Matter-certified apps and devices.

The matter.js troubleshooting docs put it the same way: Matter requires IPv6, optionally also allows IPv4, and there's no requirement for an IPv6-enabled internet connection or a DHCPv6 server — all requirements are about the local network environment. Home Assistant's Matter docs agree: no IPv6 internet connection or DHCPv6 server is needed, but IPv6 support has to be enabled on Home Assistant itself under Settings > System > Network, set to Automatic or static. Devices often show several IPv6 addresses — link-local, unique local and global unicast.

Home Assistant's Thread docs say Thread is an IPv6-only protocol, and that Thread devices may join the mesh but fail to communicate beyond it if any required layer lacks IPv6. eero's IPv6 page explains the distinction clearly: local devices use link-local addresses assigned by the router, while global addresses come from your internet provider. IKEA's FAQ says to set your Wi-Fi router to IPv6, and only if problems persist, check the WAN settings and turn IPv6 off for WAN — never the local network.

Matter across VLANs and IoT networks

The Matter Server docs are direct: Matter uses link-local multicast protocols that don't work across different LANs or VLANs. They recommend either a completely flat network or making sure the machine running Matter Server is on the same (v)LAN as the devices, any border routers and the phone used for commissioning. Home Assistant's Matter docs say the same thing for Wi-Fi Matter devices and Thread border routers: they need to be on the same VLAN as Home Assistant. Thread-only devices should be joined to Thread networks that have at least one border router connected to the Home Assistant LAN. Home Assistant also says Matter may not integrate well with enterprise networking solutions like VLANs, and recommends keeping the topology as simple and flat as possible.

The matter.js docs add a practical detail: multiple LANs, VLANs and subnets can prohibit UDP routing from working. The hub needs to reach the device — the phone does the commissioning, but the hub talks to the device afterwards. None of these sources documents a supported cross-VLAN setup, so if you use an IoT VLAN, plan to put the Matter controller and any Thread border routers on it too.

mDNS forwarders, multicast optimizations and IGMP snooping

• mDNS forwarders. The Matter Server docs say not to enable mDNS forwarders on the network — they name the option called mDNS on UniFi — because they tend to corrupt or severely hinder Matter packets. Separately, UniFi's own page describes its mDNS Proxy as on by default for new networks, and UniFi's switch settings page lists "Matter Network" (_matterc._udp; _matterd._udp) among the services its Auto mode forwards. These are separate sources: UniFi's pages describe the feature, and don't say how it affects Matter.
• Multicast "optimizations." The Matter Server docs warn about professional gear such as UniFi or Omada that has options to filter multicast traffic, often called "Multicast optimizations" or similar. They say to disable such features because they kill domestic protocols that rely on multicast. Home Assistant also says a router or access point setting to "optimize" multicast traffic can harm discovery traffic from Matter devices.
• IGMP / MLD snooping. The Matter Server docs say IGMP/MLD snooping implementations may help or hinder Matter traffic, and suggest trying the options if your equipment offers them. Home Assistant lists "(malfunctioning) IGMP snooping" as a possible cause of devices becoming unavailable. UniFi's switch settings page notes that some IoT devices may expect multicast to be flooded regardless of group membership.
• UniFi airtime tools. UniFi's broadcast traffic page says Multicast & Broadcast Control blocks cross-AP device discovery, and Device Isolation prevents direct device-to-device communication including discovery and casting protocols. These are UniFi's general tools, not Matter-specific advice, but they affect the same discovery traffic Matter relies on.

Guest networks, one network name and 2.4 GHz vs 5 GHz

The CSA's primary Wi-Fi network article is explicit: Matter devices belong on your primary network. Guest networks isolate devices from each other and from controllers on the primary network, which blocks communication and causes setup to fail. The CSA says Matter was designed to have all devices on the same network so they can talk directly to each other. It also recommends a single SSID across 2.4 GHz, 5 GHz and 6 GHz bands, and warns that a second router can create two independent networks — if you use one, put it in bridged or AP mode. For homes with 10+ Matter over Wi-Fi devices, the CSA recommends a modern mesh Wi-Fi router with satellite routers supporting all three bands; that's the CSA's recommendation, not a requirement. See our Thread vs Wi-Fi guide for how transport choice affects this.

Amazon's troubleshooting page says Matter Wi-Fi devices must connect on the same 2.4 GHz Wi-Fi network as the compatible Matter controller. SmartThings says if a network shows "Network not compatible" during pairing, check whether the device is compatible with the 2.4 GHz vs 5 GHz frequency and the security type. IKEA's FAQ suggests setting your phone's Wi-Fi to 2.4 GHz for its products, since 2.4 GHz provides a larger range.

Thread border routers and your network

Thread border routers are the link between the Thread mesh and your Wi-Fi or Ethernet network. Google Home Developers explains that border routers forward only packets relevant to the Thread network, assign IPv6 prefixes and routes, and publish mDNS records on behalf of Thread nodes. SmartThings says a third-party border router must be on the same Wi-Fi/LAN network as the SmartThings hub to be used as a connection point.

Home Assistant's Thread docs add that your network router needs IPv6 forwarding enabled so IPv6 traffic can flow between the local network and the Thread mesh. If any layer lacks IPv6, Thread devices may join the mesh but fail to communicate beyond it. Home Assistant also notes that border routers from different vendors can create separate Thread networks with different credentials, which prevents devices from roaming between them. For more on hubs and border routers, see our hub and Thread border router guide.

What each platform says about your network

Every platform's Matter support runs through a hub or controller, and the network requirements differ by platform.

Google and Home Assistant say the most about networks in their public docs. Apple's page only covers connecting to the same Wi-Fi network as your accessories and checking VPN and third-party security software — it doesn't mention IPv6, VLANs or multicast. Amazon's page covers the 2.4 GHz rule and the 30 ft (9 m) distance to the Matter controller. SmartThings covers border router placement and its pairing checks: the controller is online, the Wi-Fi or Thread router is close enough, and the 2.4 GHz vs 5 GHz frequency and security type match. See our platform guides for Apple Home, Google Home, Alexa, SmartThings and Home Assistant.

UniFi, eero and TP-Link Deco: what their own pages say

UniFi

UniFi's mDNS Proxy page says the feature is on by default for new networks, with Auto, Off and Custom modes, and UniFi's switch settings page lists "Matter Network" (_matterc._udp; _matterd._udp) among the services its Auto mode forwards. The switch settings page also covers IGMP Snooping with Forward Unknown Multicast Traffic options — Drop is the default, and multicast in the 224.0.0.0/24 range is always flooded. UniFi's broadcast traffic page describes Multicast & Broadcast Control and Device Isolation as airtime tools. The Matter Server docs separately warn about mDNS forwarders and multicast optimizations on gear like UniFi.

eero

eero's Matter page says eero supports Matter as a controller only, with Alexa, and lists the compatible models: eero Pro 6E, Pro 6, 6+, 6, PoE 6, PoE Gateway, 7, Pro 7, PoE 7 and Max 7. eero's advanced networking page says the IPv6 toggle refers specifically to global IPv6 addresses from your ISP, and enabling or disabling it reboots the network. eero's IPv6 page says local devices use link-local addresses assigned automatically. Thread can be enabled or disabled with a toggle in Advanced networking.

TP-Link Deco

TP-Link's Deco Matter FAQ says Deco works as a central controller for Matter-certified devices in the Deco app, with control on the local network even when the home goes offline. TP-Link's Deco IPv6 FAQ says the IPv6 connection type must match what your ISP provides, configured under More > Internet Connection > IPv6.

Firewalls and ports

IANA's port registry lists port 5540 (both tcp and udp) as "matter", assigned to the Connectivity Standards Alliance. The matter.js docs say Matter uses mDNS, a UDP-based protocol, to discover devices, and that firewalls or network settings can block it. They suggest checking that your network allows UDP traffic on port 5540 and the mDNS port 5353, and note that routers normally don't route UDP packets between network segments. Apple's support page says to check VPN and third-party security software for connectivity issues.

Running your own Matter controller (Home Assistant and Linux hosts)

If you run Home Assistant OS with the Matter Server app, you're on the supported path — Home Assistant's Matter docs say standalone Docker is unsupported, and Thread devices need Home Assistant OS 10 and above. Home Assistant's Thread docs walk through the layers to check: the host, the network router, the hypervisor if you use a VM, and the Docker daemon. On Home Assistant OS, Docker IPv6 may need enabling from the command line with ha docker options --enable-ipv6=true.

For people running a Matter controller on their own Linux host, the Matter Server docs and matter.js docs have specific requirements: the host must process ICMPv6 Router Advertisements correctly, IPv6 forwarding should be disabled on the controller host (net.ipv6.conf.all.forwarding) — otherwise outages up to 30 minutes can occur — and NetworkManager should be version 1.42 or newer. Home Assistant OS 10 and newer handles these correctly out of the box.

Frequently asked questions

Does Matter need IPv6?

Yes. Google's help page says IPv6 must be enabled on your home wireless network, and matter.js says Matter requires IPv6 but optionally also allows IPv4. Some devices work with IPv4, but they need IPv6 to reach all Matter-certified apps and devices.

Do I need IPv6 from my internet provider for Matter?

No. Home Assistant and matter.js both say there's no requirement for an IPv6-enabled internet connection or DHCPv6 server. The IPv6 requirement is local only.

Can Matter work across VLANs?

The Matter Server docs say Matter's link-local multicast doesn't work across different LANs or VLANs, and Home Assistant says Wi-Fi Matter devices and Thread border routers need to be on the same VLAN as the controller. No source here documents a supported cross-VLAN setup.

Should I put Matter devices on a guest or IoT network?

The CSA says Matter devices belong on your primary network, not a guest network — guest isolation blocks communication with controllers and causes setup to fail. If you use an IoT VLAN, the controller and border routers need to be on it too.

Should I turn off IGMP snooping for Matter?

Not necessarily. The Matter Server docs say IGMP/MLD snooping may help or hinder Matter traffic, and suggest trying the options. Home Assistant lists malfunctioning IGMP snooping as a possible cause of devices becoming unavailable.

What ports does Matter use?

IANA lists port 5540 (tcp and udp) as "matter". The matter.js docs also name the mDNS port 5353 for discovery.

Do Matter devices work on 5 GHz Wi-Fi?

No source here gives a general rule. Amazon says Matter Wi-Fi devices must be on the same 2.4 GHz network as the controller for Alexa. SmartThings says to check the device's 2.4 GHz vs 5 GHz compatibility. The CSA recommends a single SSID across bands.

More MatterCheck guides

• Matter device not pairing — first-time setup failures and pairing codes.
• Matter device offline or not responding — devices that drop off after setup.
• Matter hubs and Thread border routers — which hub each platform needs.
• Thread vs Wi-Fi for Matter — how the transport choice changes your network needs.
• Matter without internet — what works locally and what doesn't.
• How to add a Matter device — the pairing flow across platforms.
• Multi-admin and sharing Matter devices — using one device with several ecosystems.
• Matter bridges for Zigbee devices — bringing existing Zigbee gear into Matter.
• Thread credentials: share, sync and combine Thread networks — how phones keep Thread credentials and how to share, sync or combine Thread networks.
• Matter on TVs: TV hubs and Matter Casting — which TVs and streamers are Matter hubs and what Matter Casting is.
• Matter on Hubitat, Homey and openHAB — which Hubitat, Homey and openHAB models support Matter, Thread and bridging.

How we checked

Pages fetched 2026-10-20 — Google's help page 12391458 and two Google Home Developers Matter primer pages (last updated 2022-07-13 UTC); Home Assistant's Matter and Thread docs (2026.10.2); the Matter Server and matter.js project docs; the Matter SDK docs and the CSA's Matter Handbook; IANA's port registry; the CSA's primary Wi-Fi network article; Apple's support page 102056; Amazon's and SmartThings' Matter troubleshooting pages; UniFi's, eero's and TP-Link's support pages; and IKEA's FAQ. Router menus and defaults change with firmware; maker pages apply to that maker's gear. See our methodology for how MatterCheck sources and checks facts.

Last reviewed 2026-10-20. If a setting here doesn't match your router, follow your router maker's or platform's own page linked above.