Views: 31,308,365 Homepage | Main | Rules/FAQ | Memberlist | Active users | Last posts | Calendar | Stats | Online users | Search 05-12-26 06:24 AM
Guest:

Main - Posts by zakski


zakski
Posted on 03-29-26 09:38 AM, in Testing Query: libslirp localhost forward address for DNS? (rev. 3 of 04-09-26 01:10 PM) Link | #8520
Am currently setting up a local testing env for server-side shenanigans

Can someone point me to what IP I should be using for the DS/DSi DNS settings, If I'm running a DNS server against 127.0.0.1:53?

I have tried the default route for libslirp, and will next try the DNS forward IP I found, and will report back if that works, but I am also putting the question out in case I am wrong.

default route: 10.0.2.2/24
DNS forward: 10.0.2.3
DHCP addresses: 10.0.2.15 - 10.0.2.31
default route ipv6: fe80::2/64
DNS forward IPv6: fe80::3


10.0.2.2 10.64.0.1 works, also using
netstat -tulpn | grep LISTEN
to find the docker container IP and pointing to that does.


Issue was secondary DNS was set to 0.0.0.0, changing it to 1.1.1.1 resolved it, which is interesting, because pointing directing to the original WFC DNS did not require it.

zakski
Posted on 04-08-26 07:09 PM, in Testing Query: libslirp localhost forward address for DNS? Link | #8537
No such luck. I'm running windows.

This issue is still occurring actually. looks like its somewhere on the melon end, since if I supply a non 127.0.0.1 ip it connects fine, but 127.0.0.1 is verboten by the firmware. Need to now see if I can get some form of logging to find out what is occurring

zakski
Posted on 04-09-26 01:10 PM, in Testing Query: libslirp localhost forward address for DNS? Link | #8539
10.64.0.1 is the winner, its not setup the exact same as qemu


Main - Posts by zakski

Page rendered in 0.028 seconds. (2048KB of memory used)
MySQL - queries: 22, rows: 71/71, time: 0.024 seconds.
[powered by Acmlm] Acmlmboard 2.064 (2018-07-20)
© 2005-2008 Acmlm, Xkeeper, blackhole89 et al.