0

Issue with IKEA Home Smart Gateway

Whenever I am using NextDNS with default settings,  my Ikea HomeSmart Gateway refuses to work after a couple of minutes. Restarting it helps to get it running again for a while.

Issue is, that neither homekit nor cell phone app are able to reach the Ikea Gateway anymore in the same intranet 192.168.x.x.
After changing back the DNS servers to provider‘s defaults everything works fine again.

Any help would be appreciated.

14 replies

null
    • Pro subscriber ✓
    • DynamicNotSlow
    • 4 yrs ago
    • Reported - view

    Did you look at Logs?

      • ChrisK
      • 4 yrs ago
      • Reported - view

      DynamicNotSlow 

      Yes, but there was no relevant entry regarding Ikea domains or websites indicating blocking, unfortunately.

    • Calvin_Hobbes
    • 4 yrs ago
    • Reported - view

    Try disabling rebinding protection 

      • ChrisK
      • 4 yrs ago
      • Reported - view

      Calvin Hobbes 

      Thanks for your advice. 
      No effect, unfortunately.

    • Pro subscriber ✓
    • DynamicNotSlow
    • 4 yrs ago
    • Reported - view

    Is "bypass blocking" in your settings activated? Maybe IKEA use own DNS or use such as fallback which would result in such problems.

      • ChrisK
      • 4 yrs ago
      • Reported - view

      DynamicNotSlow : Ok, where do I find this setting? You mean in my PL router or at Nextdns?

      • Pro subscriber ✓
      • DynamicNotSlow
      • 4 yrs ago
      • Reported - view

      ChrisK you find that in your NextDNS account settings on NextDNS website

    • ChrisK
    • 4 yrs ago
    • Reported - view

    I disabled bypass setting and dns-rebinding. Now it works. Thank you. 🔝 🙋🏻‍♂️

      • Calvin_Hobbes
      • 4 yrs ago
      • Reported - view

      ChrisK 

      It makes sense that BOTH settings were necessary.   Glad it's working.

    • ChrisK
    • 4 yrs ago
    • Reported - view

    As the problem occured after several day again, that the Gateway was not reachable from intranet anymore, I researched the network traffic and IKEA related forums deeper. 

    After analyzing my router's logs, I discovered, that the IKEA Tradfri Gateway retries to reach Google DNS (8.8.8.8) and Amazon Servers (e.g. 3.121.30.16, 18.195.46.8 and 52.57.42.77), periodically.

    But no matter what I try for NEXTDNS settings (already mentioned in posts above --> disabled rebind protection / DNS bypass blocking as well as adding those servers to Allow-List), the device becomes unreachable from intranet after approx. 2 days in operation.  Seems like it blocks access from internal.

    So I found in some IKEA related forums that this behavior seems to be a bug by the device itself.
    The suggestion is to completely disable the Tradfri Gateway's WWW (internet access) by the Main router (so intranet LAN access remains active). This is what I am trying currently, seems to be successfull. This doesn't interfere with the IKEA app's or Tradfri Gateway's functionality, as anyhow now Internet-Access to the device is possible (only by Apple's Homekit or Amazon Alexa).

    However, I can conclude, that the "no connect issue" of IKEA's Tradfri gateway doesn't occur that regular with using my Internet provider's DNS default servers, but occurs approx. evers 2 days with using NEXTDNS's DNS servers (and default profile settings). Turning off internet access of this device seems to help. Unclear for me, what the technical reason is?

    • eMa_bIe
    • 3 yrs ago
    • Reported - view

    Hi. I have same issues . How can fix it ???

    • Nope_Negatory
    • 3 yrs ago
    • Reported - view

    The Tradfri gateway really, really wants to talk to webhook.logentries.com and goes catatonic if it can't. Put logentries.com on your Allowlist and it'll work fine. Hope this helps.

    • mito
    • 2 yrs ago
    • Reported - view

    I just want to share the same experience, blocking webhook.logentries.com will break the Tradfri from working. This morning my entire home Tradfri just stopped responding due to last night I changed to a new tracking filter in NextDNS. It was blocking the device.

    Make sure to put on Allowlist like @nope_negatory said.

    • jcrueter
    • 1 yr ago
    • Reported - view

    Hopefully useful addition: I’ve had pretty tight DNS filtering set up for quite a while already (combining the powers of AdGuard Home and pfBlocker-NG internally, and using NextDNS as the only allowed external resolver), and never had any trouble with Trådfri gateway. But as soon as I turned on “block page” in NextDNS: Crash! BOOM! and Trådfri gateway doesn’t even respond to Ping anymore.

    So: responding “0.0.0.0” to webhook.logentries.com works fine, but when the NextDNS block page is returned the unit crashes. Soon.

Login to reply

Content aside

  • 1 yr agoLast active
  • 14Replies
  • 487Views
  • 7 Following