Hello guys, I realize that there is already another post with this same issue, but it is old and for open VPN.
I have a Flint 3 as wireguard server, and using a Slate 7 as client. The fisrt day I setted it up, everything worked perfect behind the client, I could see my mapped drives and use windows remote desktop using computer names as if I was at home locally. But the next day after a few tests with Tailscale and Astrowarp to see which would be faster (wireguard is), I was not able to resolve anything behid the server by name, only by IP address. Could any of you smart people help?
Thank you for the reply Bruce, they are not on, my tests were made with each turned on on its own, right now the only service is the Wireguard server, using DDNS by gl.inet. Do you have other suggestions? by the way someone mentioned on reddit to edit the host file, but that is also not working for me, maybe I just did it wrong, can you suggest on that? for context, this reddit will show what I've tried so far:
" First.. make sure your Server router and Travel router use different LAN IP ranges to avoid IP conflicts. Next, in the Wireguard client profile for the Travel router, make sure the "DNS =" line is set only to WG IP address of the Server router (e.g. 10.0.0.1 by default). This should ensure the DNS queries of devices attached the travel router VPN network are sent through the VPN tunnel to be resolved by the DNS server on the Server router. Also set the travel router as the authoritative DNS server (NETWORK > DNS > Override DNS Settings of All Clients = on). Hopefully this should resolve your issue.
If not, then you could go the extra step of setting fixed a DHCP IP for your device on the Server router's LAN (NETWORK > LAN > Address Reservation), and then setup a hostname/IP mapping in the Server router's /etc/hosts file (NETWORK > DNS > Edit Hosts). "
Weird. I hate to say it but I'd nuke it all & start over. It ain't much but here's something handy to help save states as you build up a clean config:
#!/bin/sh
HOST="$(uci show system.@system[0].hostname | cut -d "'" -f '2')"
DOMAIN="$(uci show dhcp.@dnsmasq[0].domain | cut -d "'" -f '2')"
timestamp="$(env TZ=UTC date +'%Y%m%dT%H%M%Z')"
sysupgrade --create-backup /tmp/backup-"${HOST}"."${DOMAIN}"-"${timestamp}".tar.gz
exit 0
Throw that into a script file & run it as a check point any time you need it. It'll output a tarball in /tmp/ for you to pull down via SFTP (opkg update && opkg install openssh-server). You can always restore via LuCI -> System -> Backup/flash firmware (LuCI is found under System -> Advanced Settings).
LOL I've been trying to delay the nuke as much as I could, mostly because I really want to figure this out. I'm new but very interested in all this "magic" world of networking... But I guess you just gave me the bump to blast it all to hell as somebody that does not want to loose more time on it would. Thank you
No sweat. That resulting tarball is nothing but a collection of .conf files... glorified text files. Even 120kB would be a massive overestimation for the resulting tarball. It ain't exactly like these routers have a native checkpoint/snapshot capability but a shell script is the next best thing.
You could always pull the current state & put it aside as a 'known bad', slowly comparing & reinstating ea. change until it's broken again. Then 'roll back'/restore via LuCI.