Skip to main content
Forum FAQ's
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

mDNS, 4GEE Router and Home Connect - Siemens oven

BazzaUK
Visitor

‎02-01-2026 01:36 PM

I saw somebody else posted about this back in 2022 but there was no resolution. Anybody got any technical knowledge they can share?

Home Connect Oven Connectivity Failure

Issue

  • Siemens oven fails to connect (HC02‑2 error).
  • EE 4GEE WL1B625M01 router misclassifies oven multicast traffic as UDP port scans and blocks them.
  • Without multicast routing/IGMP proxy, the oven cannot complete handshake.

Wireshark Capture

  • Oven (192.168.8.192) is sending mDNS packets to 224.0.0.251.
  • Highlighted service: _homeconnect._tcp.local.
  • Oven repeatedly advertises itself via multicast DNS for Home Connect discovery.

Router IDS Log

  • EE router log entry:

Code

Detect UDP port scan attack, and the attack has been blocked, scan packet from 192.168.8.192

  • Router misclassifies oven’s multicast discovery as a port scan and blocks it.

It looks as if:

The Siemens oven is functioning correctly and consistently broadcasts multicast DNS announcements (_homeconnect._tcp.local) to advertise itself for Home Connect discovery. Packet captures confirm these announcements are sent, but the EE WL1B625M01 router misclassifies them as “UDP port scan attacks” and blocks the traffic.

Because the router does not appear to support multicast routing/IGMP proxy, the oven cannot complete the HC02‑2 handshake required for pairing. This appears to be a router limitation, not an appliance fault.

Resolution requires either enabling multicast routing/IGMP proxy on the EE WL1B625M01 (if supported by firmware) or replacing it with a router that supports multicast forwarding. Without this capability, Home Connect appliances will not be able to establish a connection.

 

0 Helpful
1 REPLY 1
bobpullen
Star Contributor
Star Contributor

‎06-01-2026 01:38 PM

Do you have a link to the thread from 2022?

If the cause is the lack of multicast support and/or aggressive port scan prevention - and there's no way to tweak the behaviour in the router settings - then I imagine your options are going to be limited 😕

Is this just the initial act of pairing with an app or similar that's impacted? If so, I wonder if there's any merit in you creating a hotspot using a spare mobile phone or similar that uses the same WiFi name/password as the 4GEE hub. Turn the EE router off, try discovery using the mobile phone hotspot, and then revert everything back to the hub and see if it 'sticks' 🤷