Now, something for the more tech savy among us. You may have read about setting up a virtual private network on your Windows 7/8/8.1 PC. When following the instructions correctly, you are able to use the WiFi adapter of your PC as an actual WiFi hotspot. It (the WiFi adapter) can even stay connected with the router while doing so, so it handles both the internet connection and the 3DS. We can use that for Homepass, using MACycle along with it. Instructions for setting up the virtual WiFi adapter are found here. We can also block certain domains using the hosts file on your computer (this is f.e. also used by SpyBots 'immunize' function). Instruction for blocking domains via hosts file are found here. Now, we may use the instructions above to add these lines to our hosts file: Code: # hosts file block entries to stop 3DS update by d0k3 # explanations: # NUS -> Nintendo Update Server or Net Update SOAP # CDN -> Content Delivery Network # ECS -> ECommerce SOAP # IAS -> Identity Authification SOAP # CAS -> CAtaloging SOAP # SOAP -> Simple Object Access protocol, http://en.wikipedia.org/wiki/SOAP # NintendoWifi.net -> Nintendos dedicated 3DS domain # this domain checks for an update (important!) 127.0.0.1 nus.c.shop.nintendowifi.net # this domain hosts the update content (important!) 127.0.0.1 nus.cdn.c.shop.nintendowifi.net # seems to be another significant one (according to Yifan Lu) 127.0.0.1 ecs.c.shop.nintendowifi.net # this blocks eShop authentication (might as well get rid of that too) 127.0.0.1 cp3s-auth.c.shop.nintendowifi.net # this is a connection test (what will happen if we disable this?) # 127.0.0.1 http://conntest.nintendowifi.net/ # what follows is the overkill list, this might disable stuff you actually # wanted to keep using. Uncomment if you're feeling adventurous. #127.0.0.1 cas.c.shop.nintendowifi.net #127.0.0.1 ccs.c.shop.nintendowifi.net #127.0.0.1 ccs.cdn.c.shop.nintendowifi.net #127.0.0.1 ias.c.shop.nintendowifi.net #127.0.0.1 pls.c.shop.nintendowifi.net #127.0.0.1 npul.c.app.nintendowifi.net #127.0.0.1 cp3s.cdn.nintendowifi.net #127.0.0.1 eou.cdn.nintendowifi.net #127.0.0.1 npdl.cdn.nintendowifi.net The list above is updated from this post, but you may find the original list, inside the spoiler below. It will also work, but use the one above, it's more precise. Warning: Spoilers inside! Code: 127.0.0.1 nus.c.shop.nintendowifi.net 127.0.0.1 nus.cdn.c.shop.nintendowifi.net 127.0.0.1 nus.cdn.wup.shop.nintendo.net 127.0.0.1 c.shop.nintendowifi.net 127.0.0.1 nus.cdn.shop.wii.com 127.0.0.1 nus.wup.shop.nintendo.net 127.0.0.1 ecs.wup.shop.nintendo.net 127.0.0.1 ccs.wup.shop.nintendo.net 127.0.0.1 ias.wup.shop.nintendo.net 127.0.0.1 tagaya.wup.shop.nintendo.net Lifted from this thread. May block too much / too little, no guarantees. And, en voilà, a safe internet connection / homepass relay for your 3DS, using hardware almost everyone has access to and without the need to install any additional tools. At least in theory. At the moment I'm too scared to even accept the Nintendo Network agreement on my shiny new N3DS. So, will that work? My experiments with other hardware in a virtual network say yes, but then the 3DS might somehow circumvent this by accessing the DNS server directly. Maybe someone with EmuNAND can try (I'm a Sky3DS user atm, sorry)?