Closed iyra closed 6 years ago
The parameter -gw
tells subnet to change the default route of all network traffic to flow through the VPN. This is not what you want if you only want to link up a virtual LAN.
My best guess is that your DNS server is on your physical LAN, and because all your traffic is going through the VPN your DNS server is unreachable. Either:
-gw 192.168.69.1
parameter to stop routing all of your traffic through the VPN.8.8.8.8
(google's fast DNS resolver).If you are intentionally routing all your traffic through the VPN, the easiest solution to get it working is to update your DNS server to 8.8.8.8
. This is what I did.
You said, "The parameter -gw tells subnet to change the default route of all network traffic to flow through the VPN. This is not what you want if you only want to link up a virtual LAN."
If I want to connect myself (a client) and another client to the server such that I can communicate with the other client, would I need the -gw
option? Thanks for the input, you are right, my DNS is going through my router at home, I'll try and change it to 8.8.8.8
.
Go ahead and remove -gw yes.
Closing as I think this solved your issue. Future readers:
-gw
switch. This will route all your traffic through the gateway specified. If your DNS is not accessible from this gateway, DNS will break.8.8.8.8
, which should be accessible anywhere on the internet.
Hi, I am following the guide to accessing a LAN from a client; running this command:
sudo go/bin/subnet -gw 192.168.69.1 -network 192.168.69.4/24 -cert Downloads/client.certPEM -key Downloads/client.keyPEM -ca Downloads/ca.certPEM my.server.ip
does not report any error, however while it is running I can't ping any domains, however I can access them via IP alone.I am on Gentoo Linux with openrc and using Go version 1.8.3 amd64. This issue does not seem to happen on the server. What can I do to get my DNS working again while I use subnet?