Hi everybody!
Yesterday i bought my n3ds (9.9.0-26) but i wasn't aware about the update nag thing and now my n3ds is aware of a new update available and even with the DNS that blocks nintendo servers i can't load browserhax fast enough to run it before the *network error* appears.
So I was thinking about running the a web server locally with the browserhax code (taken from repos) to lowering download time (i successfully to loaded google homepage) but I think that while redirect nintendo's domain to 127.0.0.1 we have also to delay the DNS answer, simulating a slow DNS response for that domain.
I can manage the first task without problem (running local web server) but for the second point I need to improve my knowledge about DNS server.
So, I was wondering if some of you think that the added delay could be of any help (and I will start to figure out a way to do it)...
P.S.: I still don't know how n3ds treats update requests (it stores update availability in his memory but it seems that every time you fire up the browser it always do a check on nintendo's server), so if you have info about it, please share them.
Thank you for your contributes.
Yesterday i bought my n3ds (9.9.0-26) but i wasn't aware about the update nag thing and now my n3ds is aware of a new update available and even with the DNS that blocks nintendo servers i can't load browserhax fast enough to run it before the *network error* appears.
So I was thinking about running the a web server locally with the browserhax code (taken from repos) to lowering download time (i successfully to loaded google homepage) but I think that while redirect nintendo's domain to 127.0.0.1 we have also to delay the DNS answer, simulating a slow DNS response for that domain.
I can manage the first task without problem (running local web server) but for the second point I need to improve my knowledge about DNS server.
So, I was wondering if some of you think that the added delay could be of any help (and I will start to figure out a way to do it)...
P.S.: I still don't know how n3ds treats update requests (it stores update availability in his memory but it seems that every time you fire up the browser it always do a check on nintendo's server), so if you have info about it, please share them.
Thank you for your contributes.