![]() ![]() # It means the VPN connection will firstly connect to the VPN Server # default network gateway through the VPN. Tunnelblick: NOTE: The DNS servers include one or more free public DNS servers known to Tunnelblick and one or more DNS servers not known to Tunnelblick.Tunnelblick: Warning: DNS server address fe80::1 is not a public DNS server known to Tunnelblick and is not being routed through the VPN.Synology "Router configuration": not enabled since it cannot recognise my modem.Synology "External access": enabled via.Using a valid Let's Encrypt certificate.Did not install a DNS server in the NAS.Modem: I also added a static lease in the modem to reserve the ip 192.168.0.220 to the NAS.Modem: Local Network settings and Modem DNS servers settings Modem Port forwarding: UDP, 1194 to 1194 of the NAS local IP Synology firewall: allowed IP ranges equal to the OpenVPN server's range Synology firewall: allowed port 1194, UDP protocol # "proto udp6" in UDP mode or "proto tcp6-client" in TCP mode # If you want to connect by Server's IPv6 address, you should use # Repeat this option to set secondary DNS server addresses.ĭhcp-option DNS 192.168.0.1 # Modem's local IP # dhcp-option DNS: To set primary domain name server address. ![]() ![]() If used, the DNS servers not known to Tunnelblick may cause DNS queries to fail or be intercepted or falsified even if they are directed through the VPN. Specify only known public DNS servers or DNS servers located on the VPN network to avoid such problems. Not sure if this is related, but the following modem's diagnostics consistently fail. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |