How To: Block Wii U updates with DD-WRT

Discussion in 'Wii U - Hacking & Backup Loaders' started by BinaryShrub, Mar 8, 2016.

  1. BinaryShrub
    OP

    BinaryShrub Member

    Newcomer
    23
    13
    Mar 8, 2016
    United States
    I decided to write a quick guide to blocking the nintendo update urls with DD-WRT.

    WARNING: You should ALWAYS use 107.211.140.065 (TubeHax DNS) on your Wii U, the steps below add two more layers of protection that I have personally tested independently -- however I do not guarantee anything.

    Note: You do not have to perform both Configuration 1 and Configuration 2, they are both separate layers of protection and should work independently, however I'd advice both to be extra safe.

    Configuration 1) Reroute All Requests for the URLs to localhost:
    In a nutshell, this will tell your router, that when any computer/client requests to connect to any of the nintendo update urls (listed below), repoint them to themselves -- stoping all hopes of an update.

    1. Open a browser and navigate to your DD-WRT Control Panel (e.g. 192.168.1.1)
    2. Open Services > Services and make sure DNSMasq is Enabled
    3. Paste the text below into Additional DNSMasq Options:
      Code:
      address=/nus.c.shop.nintendowifi.net/127.0.0.1
      address=/nus.cdn.c.shop.nintendowifi.net/127.0.0.1
      address=/nus.cdn.shop.wii.com/127.0.0.1
      address=/nus.cdn.wup.shop.nintendo.net/127.0.0.1
      address=/nus.wup.shop.nintendo.net/127.0.0.1
      address=/c.shop.nintendowifi.net/127.0.0.1
      address=/cbvc.cdn.nintendo.net/127.0.0.1
      address=/cbvc.nintendo.net/127.0.0.1
    4. Now scroll to the bottom and click Apply Settings
    5. Verify by attempting an nslookup on your computer with any of the urls, you should get 127.0.0.1
    6. DONE

    Configuration 2) Block All Requests for the URLs
    This will/should block all connections to the urls (however nslookup will still resolve a correct IP unless you perform Configuration 1 above).

    1. Open a browser and navigate to your DD-WRT Control Panel (e.g. 192.168.1.1)
    2. Open Access Restrictions
    3. Select Policy 1() -- This is assuming you have no policies set.
    4. Set Status to Enabled
    5. Set A Policy Name to something meaningful -- mine is Nintendo Update Block
    6. Click Edit List of clients, scroll down to the bottom
    7. Insert a IP range from 1 to 254 (e.g. 192.168.1.1 to 192.168.1.254)
    8. Click Apply Settings and then Close
    9. You should now be back on the original Access Restrictions page
    10. Scroll down to Website Blocking by URL Address and Website Blocking by Keyword
    11. Enter the following into both:
      Code:
      nus.c.shop.nintendowifi.net
      nus.cdn.c.shop.nintendowifi.net
      nus.cdn.shop.wii.com
      nus.cdn.wup.shop.nintendo.net
      nus.wup.shop.nintendo.net
      c.shop.nintendowifi.net
      cbvc.cdn.nintendo.net
      cbvc.nintendo.net
    12. Now scroll to the bottom and click Apply Settings
    13. DONE

    You should be good to go!

    If you are feeling dangerous and want to verify all is good, try to attempt a manual System Update. If it fails you are good! If it doesn't, CANCEL IT IMMEDIATELY.
     
  2. Kohmei

    Kohmei GBAtemp Advanced Fan

    Member
    758
    457
    Feb 17, 2013
    United States
    Simply adding:
    Code:
    address=/.shop.nintendowifi.net/127.0.0.1
    address=/.shop.wii.com/127.0.0.1
    address=/.shop.nintendo.net/127.0.0.1
    under dnsmasq does the trick.

    Access restrictions does not work for me. I'm pretty sure it only blocks html access, so different ports/protocols will not trigger the blocks.
     
    SrTommy likes this.
  3. CosmoCortney

    CosmoCortney The Hacker Furry

    Member
    1,538
    1,462
    Apr 18, 2013
    Germany
    on the cool side of the pillow
    Awesome, I was going to do this last August but I don't know shit about WRT, so I ended up selfhosting everything :P
    however, thank you for this guide :)
     
  4. BinaryShrub
    OP

    BinaryShrub Member

    Newcomer
    23
    13
    Mar 8, 2016
    United States
    Interesting... I was able to try a self update and it failed with the same error code as Configuration 2, as far as I saw it was working...

    Also thanks for your addition!