Closed renatopancheri closed 3 years ago
Thanks for finding this bug. Unfortunately your fix is not quite correct, because the part of the code you're trying to put a condition to is responsible for handling routes to the original DNS server. The bug lies in l.resolvHandler
initialization:
https://github.com/kayrus/gof5/blob/da6e8ac2b33ddd4cc16d545055f6a54994b97e62/pkg/link/link.go#L295-L301
E.g. when wifi provides a DNS server, which is not a part of the current subnet. I already have a new-tuncfg
WIP branch to fix this. Also need to provide a case, when there is a wifi's DNS and a primary VPN dns (wifi->wireguard->gof5).
gof5 needs to get current DNS setup anyway, even when DNS is disabled. I'll take a closer look into this problem and provide a fix.
Hi!
i think i've found a small bug when setting
disableDNS: true
inconfig.yaml
:looking at the code in
pkg/link/link.go:326
seems to me pretty straight forward that there is an if statement missing in that block,adding the
if !cfg.DisableDNS {
seems to fix the issue.