Posted: Fri Apr 28, 2023 22:48 Post subject: Linksys WRT1900ACS V2 wifi cannot connect to network
I've installed the stock firmware, downloaded a 2023 build for DD-WRT, flashed successfully, named the wifi SSIDs. All is fine until I apply wireless securuty (WPA3 personal, AES), after which I cannot connect to the wifi.
I'm a newbie.
Thanks
For other to help with no internet connection problems you will need to post your settings.
Without them I can only suggest you re-boot your modem. Some modems are very sensitive to changes made to connected devices and need to re-negotiate the connection. My old Zoom modem was like that . . . my Moto modem is not.
Try re-booting modem and router and if no joy you will need to post setting to attract more help. =)
I tried that but have the same problem.
I'm connecting to my Private Internet Access acount.
Here is the VPN status log, if that is of any help.
Client Log:
19700101 01:16:49 W WARNING: Using --management on a TCP port WITHOUT passwords is STRONGLY discouraged and considered insecure
19700101 01:16:49 W WARNING: file '/tmp/openvpncl/credentials' is group or others accessible
19700101 01:16:49 I OpenVPN 2.6.3 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [MH/PKTINFO] [AEAD]
19700101 01:16:49 I library versions: OpenSSL 1.1.1t 7 Feb 2023 LZO 2.10
19700101 01:16:49 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:16
19700101 01:16:49 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700101 01:16:54 N RESOLVE: Cannot resolve host address: us-california.privacy.network:1198 (Try again)
19700101 01:16:59 NOTE: --mute triggered...
19700101 01:16:59 1 variation(s) on previous 3 message(s) suppressed by --mute
19700101 01:16:59 W Could not determine IPv4/IPv6 protocol
19700101 01:16:59 I SIGUSR1[soft Could not determine IPv4/IPv6 protocol] received process restarting
19700101 01:16:59 Restart pause 1 second(s)
19700101 01:17:00 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700101 01:17:05 N RESOLVE: Cannot resolve host address: us-california.privacy.network:1198 (Try again)
19700101 01:17:10 NOTE: --mute triggered...
As I am unfamiliar with the Plusnet modem/router I will ask if this is two separate devices or one combo modem/router device?
If a combo device is the router on the Plusnet modem/router disabled or . . are you connecting your 1900 router directly to the active Plusnet router?
I also assume you are NOT trying to connect wireless to wireless but are connecting the devices via wire.
If connecting via wire to your Plusnet router it may be the operating mode you selected on your DD-WRT Setup/Advanced Routing/Operating Mode setting.
I don't use "Router" mode but other users can advise you on the proper setup depending on the above info. Post more info about your current setup (router to router? or router to modem?) and I feel sure others here can advise you on the proper settings you need. =)
Joined: 18 Mar 2014 Posts: 12883 Location: Netherlands
Posted: Sun Apr 30, 2023 16:12 Post subject:
That is all wrong
Gateway is the next hop.
But just leave gateway and Local DNS at their default 0.0.0.0
The DNS servers of PIA are only available if there is a VPN connection.
But without DNS you will no be able to get time or resolve an url so you will not get an vpn/internet connection.
UPDATE: On other advice, I changed the ethernet cable from Internet to an ethernet port and now have internet with the Linksys router but failing to tunnel through Private Internet Access. Here is the latest log. Seems like progress. I might start again, using the pdf suggested above.
20230501 16:07:01 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20230501 16:07:01 I TCP/UDP: Preserving recently used remote address: [AF_INET]102.129.145.229:1198
20230501 16:07:01 Socket Buffers: R=[180224->180224] S=[180224->180224]
20230501 16:07:01 I UDPv4 link local: (not bound)
20230501 16:07:01 I UDPv4 link remote: [AF_INET]102.129.145.229:1198
20230501 16:07:01 TLS: Initial packet from [AF_INET]102.129.145.229:1198 sid=ebb63c0f b407e858
20230501 16:07:01 N VERIFY ERROR: depth=1 error=self signed certificate in certificate chain: 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 serial=11996199170155461251
20230501 16:07:01 NOTE: --mute triggered...
20230501 16:07:01 4 variation(s) on previous 3 message(s) suppressed by --mute
20230501 16:07:01 I SIGUSR1[soft tls-error] received process restarting
20230501 16:07:01 Restart pause 16 second(s)
20230501 16:07:17 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
20230501 16:07:17 I TCP/UDP: Preserving recently used remote address: [AF_INET]191.96.106.167:1198
20230501 16:07:17 Socket Buffers: R=[180224->180224] S=[180224->180224]
20230501 16:07:17 I UDPv4 link local: (not bound)
20230501 16:07:17 I UDPv4 link remote: [AF_INET]191.96.106.167:1198
20230501 16:07:17 TLS: Initial packet from [AF_INET]191.96.106.167:1198 sid=d7efc890 2bc7530a
20230501 16:07:17 N VERIFY ERROR: depth=1 error=self signed certificate in certificate chain: 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 serial=11996199170155461251
20230501 16:07:17 NOTE: --mute triggered...
20230501 16:07:17 4 variation(s) on previous 3 message(s) suppressed by --mute
20230501 16:07:17 I SIGUSR1[soft tls-error] received process restarting
20230501 16:07:17 Restart pause 16 second(s)
20230501 16:07:23 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:39630
20230501 16:07:23 D MANAGEMENT: CMD 'state'
20230501 16:07:23 MANAGEMENT: Client disconnected
20230501 16:07:23 NOTE: --mute triggered...
20230501 16:07:23 1 variation(s) on previous 3 message(s) suppressed by --mute
20230501 16:07:23 D MANAGEMENT: CMD 'state'
20230501 16:07:23 MANAGEMENT: Client disconnected
20230501 16:07:23 NOTE: --mute triggered...
20230501 16:07:23 1 variation(s) on previous 3 message(s) suppressed by --mute
20230501 16:07:23 D MANAGEMENT: CMD 'state'
20230501 16:07:23 MANAGEMENT: Client disconnected
20230501 16:07:23 NOTE: --mute triggered...
20230501 16:07:23 1 variation(s) on previous 3 message(s) suppressed by --mute
20230501 16:07:23 D MANAGEMENT: CMD 'status 2'
20230501 16:07:23 MANAGEMENT: Client disconnected
20230501 16:07:24 NOTE: --mute triggered...
20230501 16:07:24 1 variation(s) on previous 3 message(s) suppressed by --mute
20230501 16:07:24 D MANAGEMENT: CMD 'log 500'
19700101 00:00:00