TLS Error on OpenVPN - PIA

Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking
Goto page 1, 2  Next
Author Message
raid
DD-WRT Novice


Joined: 31 Jul 2020
Posts: 6

PostPosted: Fri Jul 31, 2020 21:08    Post subject: TLS Error on OpenVPN - PIA Reply with quote
I have a Linksys E4200 v.1 that I flashed DD-WRT firmware onto dd-wrt.v24-21676_NEWD-2_K2.6_mini-e4200.bin and upgraded to dd-wrt.v24-40559_NEWD-2_K3.x_mega-e4200.bin Firmware: DD-WRT v3.0-r40559 mega (08/06/19). I purchased Private Internet Access for VPN and entered all of their information for my router to set up the VPN. Everytime I try to connect to the VPN, I receive this error, can anyone please help me resolve this issue? I have been working on this for days now and getting more frustrated by the day. Thanks in advance for your help. I have attached Private Internet Account's step by step guide that I followed to enter the information for the VPN.

Client: RECONNECTING tls-error
Local Address:
Remote Address:

Status
VPN Client Stats
TUN/TAP read bytes 0
TUN/TAP write bytes 0
TCP/UDP read bytes 0
TCP/UDP write bytes 0
Auth read bytes 0

Log
Clientlog:
19691231 19:02:29 I SIGUSR1[soft tls-error] received process restarting
19691231 19:02:29 Restart pause 10 second(s)
19691231 19:02:39 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:39 D MANAGEMENT: CMD 'state'
19691231 19:02:39 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:02:39 I TCP/UDP: Preserving recently used remote address: [AF_INET]89.187.187.129:1198
19691231 19:02:39 Socket Buffers: R=[163840->163840] S=[163840->163840]
19691231 19:02:39 I UDPv4 link local: (not bound)
19691231 19:02:39 I UDPv4 link remote: [AF_INET]89.187.187.129:1198
19691231 19:02:39 MANAGEMENT: Client disconnected
19691231 19:02:39 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:39 D MANAGEMENT: CMD 'state'
19691231 19:02:39 MANAGEMENT: Client disconnected
19691231 19:02:39 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:39 D MANAGEMENT: CMD 'state'
19691231 19:02:39 MANAGEMENT: Client disconnected
19691231 19:02:39 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:39 D MANAGEMENT: CMD 'status 2'
19691231 19:02:39 MANAGEMENT: Client disconnected
19691231 19:02:39 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:40 D MANAGEMENT: CMD 'log 500'
19691231 19:02:40 TLS: Initial packet from [AF_INET]89.187.187.129:1198 sid=e38637d0 bc23009c
19691231 19:02:40 MANAGEMENT: Client disconnected
19691231 19:02:40 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=US ST=CA L=LosAngeles O=Private Internet Access OU=Private Internet Access CN=Private Internet Access name=Private Internet Access emailAddress=secure@privateinternetaccess.com
19691231 19:02:40 N OpenSSL: error:1416F086:lib(20):func(367):reason(134)
19691231 19:02:40 N TLS_ERROR: BIO read tls_read_plaintext error
19691231 19:02:40 NOTE: --mute triggered...
19691231 19:02:40 2 variation(s) on previous 3 message(s) suppressed by --mute
19691231 19:02:40 I SIGUSR1[soft tls-error] received process restarting
19691231 19:02:40 Restart pause 10 second(s)
19691231 19:02:48 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:48 D MANAGEMENT: CMD 'state'
19691231 19:02:48 MANAGEMENT: Client disconnected
19691231 19:02:48 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:48 D MANAGEMENT: CMD 'state'
19691231 19:02:48 MANAGEMENT: Client disconnected
19691231 19:02:48 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:48 D MANAGEMENT: CMD 'state'
19691231 19:02:48 MANAGEMENT: Client disconnected
19691231 19:02:49 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:49 D MANAGEMENT: CMD 'status 2'
19691231 19:02:49 MANAGEMENT: Client disconnected
19691231 19:02:49 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:02:49 D MANAGEMENT: CMD 'log 500'
19691231 19:02:49 MANAGEMENT: Client disconnected
19691231 19:02:50 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:02:50 I TCP/UDP: Preserving recently used remote address: [AF_INET]37.235.108.144:1198
19691231 19:02:50 Socket Buffers: R=[163840->163840] S=[163840->163840]
19691231 19:02:50 I UDPv4 link local: (not bound)
19691231 19:02:50 I UDPv4 link remote: [AF_INET]37.235.108.144:1198
19691231 19:02:50 TLS: Initial packet from [AF_INET]37.235.108.144:1198 sid=893b63bf 907393a6
19691231 19:02:51 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=US ST=CA L=LosAngeles O=Private Internet Access OU=Private Internet Access CN=Private Internet Access name=Private Internet Access emailAddress=secure@privateinternetaccess.com
19691231 19:02:51 N OpenSSL: error:1416F086:lib(20):func(367):reason(134)
19691231 19:02:51 N TLS_ERROR: BIO read tls_read_plaintext error
19691231 19:02:51 NOTE: --mute triggered...
19691231 19:02:51 2 variation(s) on previous 3 message(s) suppressed by --mute
19691231 19:02:51 I SIGUSR1[soft tls-error] received process restarting
19691231 19:02:51 Restart pause 10 second(s)
19691231 19:03:01 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:03:01 I TCP/UDP: Preserving recently used remote address: [AF_INET]89.187.187.162:1198
19691231 19:03:01 Socket Buffers: R=[163840->163840] S=[163840->163840]
19691231 19:03:01 I UDPv4 link local: (not bound)
19691231 19:03:01 I UDPv4 link remote: [AF_INET]89.187.187.162:1198
19691231 19:03:02 TLS: Initial packet from [AF_INET]89.187.187.162:1198 sid=1af2fbda a88d131e
19691231 19:03:03 N VERIFY ERROR: depth=1 error=certificate is not yet valid: C=US ST=CA L=LosAngeles O=Private Internet Access OU=Private Internet Access CN=Private Internet Access name=Private Internet Access emailAddress=secure@privateinternetaccess.com
19691231 19:03:03 N OpenSSL: error:1416F086:lib(20):func(367):reason(134)
19691231 19:03:03 N TLS_ERROR: BIO read tls_read_plaintext error
19691231 19:03:03 NOTE: --mute triggered...
19691231 19:03:03 2 variation(s) on previous 3 message(s) suppressed by --mute
19691231 19:03:03 I SIGUSR1[soft tls-error] received process restarting
19691231 19:03:03 Restart pause 10 second(s)
19691231 19:03:04 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:04 D MANAGEMENT: CMD 'state'
19691231 19:03:04 MANAGEMENT: Client disconnected
19691231 19:03:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:05 D MANAGEMENT: CMD 'state'
19691231 19:03:05 MANAGEMENT: Client disconnected
19691231 19:03:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:05 D MANAGEMENT: CMD 'state'
19691231 19:03:05 MANAGEMENT: Client disconnected
19691231 19:03:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:05 D MANAGEMENT: CMD 'status 2'
19691231 19:03:05 MANAGEMENT: Client disconnected
19691231 19:03:05 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:05 D MANAGEMENT: CMD 'log 500'
19691231 19:03:05 MANAGEMENT: Client disconnected
19691231 19:03:09 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:09 D MANAGEMENT: CMD 'state'
19691231 19:03:09 MANAGEMENT: Client disconnected
19691231 19:03:09 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:09 D MANAGEMENT: CMD 'state'
19691231 19:03:09 MANAGEMENT: Client disconnected
19691231 19:03:09 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:09 D MANAGEMENT: CMD 'state'
19691231 19:03:09 MANAGEMENT: Client disconnected
19691231 19:03:09 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:09 D MANAGEMENT: CMD 'status 2'
19691231 19:03:09 MANAGEMENT: Client disconnected
19691231 19:03:10 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19691231 19:03:10 D MANAGEMENT: CMD 'log 500'
19691231 19:00:00
Sponsor
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12889
Location: Netherlands

PostPosted: Fri Jul 31, 2020 21:18    Post subject: Reply with quote
Read and follow the forum guidelines:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087

40599 is a crappy build

Your time is not set, do not enter a time server leave it blank

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
raid
DD-WRT Novice


Joined: 31 Jul 2020
Posts: 6

PostPosted: Fri Jul 31, 2020 22:28    Post subject: TLS Error on OpenVPN - PIA Reply with quote
I set the time settings to disable. Is there a better build for my router? I have only been able to find this build, is there some where else I need to look? Thank you for replying, I am new to this.
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6439
Location: UK, London, just across the river..

PostPosted: Sat Aug 01, 2020 8:12    Post subject: Re: TLS Error on OpenVPN - PIA Reply with quote
raid wrote:
I set the time settings to disable. Is there a better build for my router? I have only been able to find this build, is there some where else I need to look? Thank you for replying, I am new to this.


all builds here ftp://ftp.dd-wrt.com/betas/2020/

DO NOT DISABLE NTP TIME ITS VITAL FOR THE ROUTER OPERATIONS....!!

choose your time zone and you can add an IP NTP time server like ggl time or cloudlflare ntp time

162.159.200.123

or

216.239.35.4

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
raid
DD-WRT Novice


Joined: 31 Jul 2020
Posts: 6

PostPosted: Sun Aug 02, 2020 0:13    Post subject: Re: TLS Error on OpenVPN - PIA Reply with quote
Alozaros wrote:
all builds here ftp://ftp.dd-wrt.com/betas/2020/

DO NOT DISABLE NTP TIME ITS VITAL FOR THE ROUTER OPERATIONS....!!

choose your time zone and you can add an IP NTP time server like ggl time or cloudlflare ntp time

162.159.200.123

or

216.239.35.4


I upgraded my build to dd-wrt.v24-41813_NEWD-2_K3.x_mega-e4200.bin and configured the VPN and used the IPs you gave me and also tried IPs from pool.ntp.org.

I am now getting an error that says: Client: RECONNECTING network-unreachable

I see that it thinks it is Dec. 31, 1969 how do I change the date and time manually? Is there a way to command the router to update the date and time?



Clientlog:
19691231 19:00:12 W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
19691231 19:00:12 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
19691231 19:00:12 I OpenVPN 2.4.8 mipsel-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Dec 29 2019
19691231 19:00:12 I library versions: OpenSSL 1.1.1d 10 Sep 2019 LZO 2.09
19691231 19:00:12 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
19691231 19:00:12 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19691231 19:00:12 I TCP/UDP: Preserving recently used remote address: [AF_INET]89.187.187.129:1197
19691231 19:00:12 Socket Buffers: R=[163840->163840] S=[163840->163840]
19691231 19:00:12 I UDPv4 link local: (not bound)
19691231 19:00:12 I UDPv4 link remote: [AF_INET]89.187.187.129:1197
19691231 19:00:15 N write UDPv4: Network unreachable (code=128)
19691231 19:00:15 I Network unreachable restarting[/quote]
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 9157

PostPosted: Sun Aug 02, 2020 0:22    Post subject: Reply with quote
Any chance you configured this router as a WAP (LAN to LAN wrt your primary router)? You typically disable the WAN in such a configuration. Along w/ settings an IP and netmask in the LAN section, sometimes ppl forget they also need to set a default gateway IP and DNS server in order for the router to carry out its operations, like setting the time.
_________________
ddwrt-ovpn-split-basic.sh (UPDATED!) * ddwrt-ovpn-split-advanced.sh (UPDATED!) * ddwrt-ovpn-client-killswitch.sh * ddwrt-ovpn-client-watchdog.sh * ddwrt-ovpn-remote-access.sh * ddwrt-ovpn-client-backup.sh * ddwrt-mount-usb-drives.sh * ddwrt-blacklist-domains.sh * ddwrt-wol-port-forward.sh * ddwrt-dns-monitor.sh (NEW!)
raid
DD-WRT Novice


Joined: 31 Jul 2020
Posts: 6

PostPosted: Sun Aug 02, 2020 0:54    Post subject: Reply with quote
eibgrad wrote:
Any chance you configured this router as a WAP (LAN to LAN wrt your primary router)? You typically disable the WAN in such a configuration. Along w/ settings an IP and netmask in the LAN section, sometimes ppl forget they also need to set a default gateway IP and DNS server in order for the router to carry out its operations, like setting the time.


I have both LAN and WAN enabled under DHCP server. I do not have a default gateway address under Basic settings, so are you saying to disable WAN (where?) add my primary routers default gateway under Basic settings,and I have Local DNS enabled as well.

I have been working on this for days, and I an not a networking guru, would you mind helping me remotely?
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 9157

PostPosted: Sun Aug 02, 2020 1:08    Post subject: Reply with quote
Having a router that refuses to update the time is unusual. As long as you keep the time feature enabled and choose a timezone, it should work. It doesn't even need a time server to be specified. If left blank, it will use its own default servers.

The one time I have seen this type of problem is when someone configures their router as a WAP (LAN to LAN wrt the primary router). In that configuration, you typically have the WAN disabled, and therefore it's critical that the LAN section be fully configured (IP, netmask, default gateway, DNS server) in order for the router to be able to carry out its administrative functions, which includes updating the time.

I am *NOT* suggesting you configure the router as a WAP! I'm merely speculating if perhaps you did for some reason, and given the above, it *might* explain why the time is not being set. In a routed configuration (i.e., active WAN), the router is configured w/ an IP, netmask, default gateway, and DNS server(s) from the ISP. And now it becomes possible for the router to carry out its administrative functions over that WAN.

_________________
ddwrt-ovpn-split-basic.sh (UPDATED!) * ddwrt-ovpn-split-advanced.sh (UPDATED!) * ddwrt-ovpn-client-killswitch.sh * ddwrt-ovpn-client-watchdog.sh * ddwrt-ovpn-remote-access.sh * ddwrt-ovpn-client-backup.sh * ddwrt-mount-usb-drives.sh * ddwrt-blacklist-domains.sh * ddwrt-wol-port-forward.sh * ddwrt-dns-monitor.sh (NEW!)
raid
DD-WRT Novice


Joined: 31 Jul 2020
Posts: 6

PostPosted: Sun Aug 02, 2020 1:30    Post subject: Reply with quote
eibgrad wrote:
Having a router that refuses to update the time is unusual. As long as you keep the time feature enabled and choose a timezone, it should work. It doesn't even need a time server to be specified. If left blank, it will use its own default servers.

The one time I have seen this type of problem is when someone configures their router as a WAP (LAN to LAN wrt the primary router). In that configuration, you typically have the WAN disabled, and therefore it's critical that the LAN section be fully configured (IP, netmask, default gateway, DNS server) in order for the router to be able to carry out its administrative functions, which includes updating the time.

I am *NOT* suggesting you configure the router as a WAP! I'm merely speculating if perhaps you did for some reason, and given the above, it *might* explain why the time is not being set. In a routed configuration (i.e., active WAN), the router is configured w/ an IP, netmask, default gateway, and DNS server(s) from the ISP. And now it becomes possible for the router to carry out its administrative functions over that WAN.


Under my WAN settings I see the attached. So does that mean that I need to input my ISPs default gateway IP of 192.168.1.1 and how do I find my ISP DNS server? Would it be under my primary routers settings?

Sorry for having so many questions, I have never set up a VPN before.
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 14222
Location: Texas, USA

PostPosted: Sun Aug 02, 2020 1:34    Post subject: Reply with quote
It looks like your E4200 is on the wrong subnet if it's not getting a WAN IP. If your ISP router / modem is on 192.168.1.x, then you need to set your E4200 local IP to 192.168.2.1. Or, you need to change what subnet your ISP equipment is on, either or.
_________________
"Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT
Pogo - A minimal level of ability is expected and needed...
DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)

----------------------
Linux User #377467 counter.li.org / linuxcounter.net
eibgrad
DD-WRT Guru


Joined: 18 Sep 2010
Posts: 9157

PostPosted: Sun Aug 02, 2020 1:49    Post subject: Reply with quote
For some reason, your WAN is not being configured. Normally when the WAN is configured w/ DHCP and connected to the ISP's modem/modem+router, it responds by automatically setting the IP, netmask, gateway, and DNS servers. For some reason, all that's there is DNS servers.
_________________
ddwrt-ovpn-split-basic.sh (UPDATED!) * ddwrt-ovpn-split-advanced.sh (UPDATED!) * ddwrt-ovpn-client-killswitch.sh * ddwrt-ovpn-client-watchdog.sh * ddwrt-ovpn-remote-access.sh * ddwrt-ovpn-client-backup.sh * ddwrt-mount-usb-drives.sh * ddwrt-blacklist-domains.sh * ddwrt-wol-port-forward.sh * ddwrt-dns-monitor.sh (NEW!)
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12889
Location: Netherlands

PostPosted: Sun Aug 02, 2020 8:16    Post subject: Reply with quote
Reset to defaults. Do not restore from a backup.

First make your internet and time working before starting vpn

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 6439
Location: UK, London, just across the river..

PostPosted: Sun Aug 02, 2020 13:18    Post subject: Reply with quote
if you use anything in NTP time box it must be either left blank like eibgrad suggested or IP, do not use names like ntp.time.org..
as egc suggested first sort your WAN connection than...
its easy, PIA have very decent guide how to set your VPN the few things to add are
https://www.privateinternetaccess.com/helpdesk/guides/routers/dd-wrt-3/dd-wrt-v40559-openvpn-setup

by egc recommendation use those settings

tls certificate must be TLS-DHE-RSA-WITH-AES-256-GCM-SHA384

for PIA, add those to advanced VPN box

persist-key
persist-tun
tls-client
remote-cert-tls server
ncp-disable

also as your router is very low specs use: SHA1 AES-128-GCM ca.rsa.2048.crt UDP 1198
make sure you have in advanced DNSmasq box
no-resolv
server=209.222.18.222
server=209.222.18.218

or any other DNS server you want
I personally have 9.9.9.9

do not expect VPN performance more than 5-10 Mbit max

_________________
Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
raid
DD-WRT Novice


Joined: 31 Jul 2020
Posts: 6

PostPosted: Mon Aug 03, 2020 3:24    Post subject: Reply with quote
Thanks everyone for the advice. I finally got the WAN settings for my router (I didn't have it plugged into my ISP modem, Rolling Eyes).

I also have my VPN connecting successfully, but when doing an IP check, it shows my ISP's public ip and not my VPN IP. I looked in my WAN settings and for some reason, it shows the 2 DNS IPs from PIA and then one that is the same IP as my primary router, and I am not sure how to remove it or how it got in there.

I have attached pics to give a visual.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12889
Location: Netherlands

PostPosted: Mon Aug 03, 2020 6:21    Post subject: Reply with quote
See the guide about DNS problems :
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=321686

Upcoming build maybe has an option to ignore the WAN DNS

_________________
Routers:Netgear R7000, R6400v1, R6400v2, EA6900 (XvortexCFE), E2000, E1200v1, WRT54GS v1.
Install guide R6400v2, R6700v3,XR300:https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=316399
Install guide R7800/XR500: https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=320614
Forum Guide Lines (important read):https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Index -> Advanced Networking All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum