TL-WR-710N USA with DD-WRT Firmware: DD-WRT v3.0-r44715 std

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Author Message
ppgg
DD-WRT Novice


Joined: 07 Nov 2023
Posts: 3

PostPosted: Fri Nov 10, 2023 13:33    Post subject: TL-WR-710N USA with DD-WRT Firmware: DD-WRT v3.0-r44715 std Reply with quote
Good morning. I am new to this, so forgive me if I make mistakes when posting. I also assume that each hardware is different and, after looking and searching the forum for similar issues to what I am dealing with, I gave up and decided to open a new thread.
AS in the subject I have a TP-LINK TL-710N, with Firmware: DD-WRT v3.0-r44715 std (11/03/20). TO be noted, the NTP Client doesn't work: I tried several different servers, and time zones, and yet the time changes (according to the time zone but in a wrong way) and it is never accurate as it should be.
Having said that, this is how I did the setup: PLEASE SEE ATTACHMENT BELOW.

And following, the State, Status, LOG I get:

State
Client: RECONNECTING init_instance
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:
19700103 07:23:45 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:23:50 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:23:56 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:23:56 W Could not determine IPv4/IPv6 protocol
19700103 07:23:56 I SIGUSR1[soft init_instance] received process restarting
19700103 07:23:56 Restart pause 5 second(s)
19700103 07:24:01 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:24:01 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:24:01 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:24:06 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:24:11 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:24:11 W Could not determine IPv4/IPv6 protocol
19700103 07:24:11 I SIGUSR1[soft init_instance] received process restarting
19700103 07:24:11 Restart pause 5 second(s)
19700103 07:24:16 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:24:16 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:24:16 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:24:21 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:24:26 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:24:26 W Could not determine IPv4/IPv6 protocol
19700103 07:24:26 I SIGUSR1[soft init_instance] received process restarting
19700103 07:24:26 Restart pause 10 second(s)
19700103 07:24:36 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:24:36 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:24:36 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:24:41 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:24:46 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:24:46 W Could not determine IPv4/IPv6 protocol
19700103 07:24:46 I SIGUSR1[soft init_instance] received process restarting
19700103 07:24:46 Restart pause 20 second(s)
19700103 07:25:06 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:25:06 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:25:06 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:25:11 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:25:16 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:25:16 W Could not determine IPv4/IPv6 protocol
19700103 07:25:16 I SIGUSR1[soft init_instance] received process restarting
19700103 07:25:16 Restart pause 40 second(s)
19700103 07:25:56 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:25:56 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:25:56 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:26:01 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:26:06 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:26:06 W Could not determine IPv4/IPv6 protocol
19700103 07:26:06 I SIGUSR1[soft init_instance] received process restarting
19700103 07:26:06 Restart pause 80 second(s)
19700103 07:27:26 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:27:26 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:27:26 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:27:31 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:27:36 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:27:36 W Could not determine IPv4/IPv6 protocol
19700103 07:27:36 I SIGUSR1[soft init_instance] received process restarting
19700103 07:27:36 Restart pause 160 second(s)
19700103 07:30:16 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:30:16 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:30:16 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:30:21 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:30:26 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:30:26 W Could not determine IPv4/IPv6 protocol
19700103 07:30:26 I SIGUSR1[soft init_instance] received process restarting
19700103 07:30:26 Restart pause 300 second(s)
19700103 07:35:26 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:35:26 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:35:26 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:35:31 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:35:36 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:35:36 W Could not determine IPv4/IPv6 protocol
19700103 07:35:36 I SIGUSR1[soft init_instance] received process restarting
19700103 07:35:36 Restart pause 300 second(s)
19700103 07:40:36 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:40:36 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:40:36 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:40:41 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:40:47 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:40:47 W Could not determine IPv4/IPv6 protocol
19700103 07:40:47 I SIGUSR1[soft init_instance] received process restarting
19700103 07:40:47 Restart pause 300 second(s)
19700103 07:45:47 W NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
19700103 07:45:47 Outgoing Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:45:47 Incoming Control Channel Authentication: Using 512 bit message hash 'SHA512' for HMAC authentication
19700103 07:45:52 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:45:57 N RESOLVE: Cannot resolve host address: usa-atlanta-ca-version-2.expressnetw.com:1195 (Try again)
19700103 07:45:57 W Could not determine IPv4/IPv6 protocol
19700103 07:45:57 I SIGUSR1[soft init_instance] received process restarting
19700103 07:45:57 Restart pause 300 second(s)
19700103 07:48:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700103 07:48:55 D MANAGEMENT: CMD 'state'
19700103 07:48:55 MANAGEMENT: Client disconnected
19700103 07:48:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700103 07:48:55 D MANAGEMENT: CMD 'state'
19700103 07:48:55 MANAGEMENT: Client disconnected
19700103 07:48:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700103 07:48:55 D MANAGEMENT: CMD 'state'
19700103 07:48:55 MANAGEMENT: Client disconnected
19700103 07:48:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700103 07:48:55 D MANAGEMENT: CMD 'status 2'
19700103 07:48:55 MANAGEMENT: Client disconnected
19700103 07:48:55 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
19700103 07:48:55 D MANAGEMENT: CMD 'log 500'
19700101 08:00:00

At this point I have been trying for several days, let alone the time spent attempting to change the firmware, and I feel like I am at a dead end. Any help will be extremely appreciated.
Sponsor
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12921
Location: Netherlands

PostPosted: Fri Nov 10, 2023 13:43    Post subject: Reply with quote
Welcome to the forum.

You posted in the right forum so bonus points earned Smile
But unfortunately you are using an old and outdated build.

See the forum guidelines with helpful pointers about how to research your router, where and what firmware to download, where and how to post and many other helpful tips:
https://forum.dd-wrt.com/phpBB2/viewtopic.php?t=324087

Latest build is 53915.

One of the problems is that your time is not working and thus your VPN will not work either.

My suggestion upgrade to a recent build, coming from such an old build a reset *after* upgrading is recommended and you have to put settings in manually, never restore a backup (to a different build).

For time settings leave the Server IP/ Name box empty only set your time zone.

If it is not working post screenshots of the Basic Setup page, Services page, OpenVPN setup page and OpenVPN status page.

For VPN consider using WireGuard instead of OpenVPN, three times faster than OpenVPN and easier to setup.

Both OpenVPN and WireGuard docs are stickies (first few threads) in the Advanced Networking Forum

_________________
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
dale_gribble39
DD-WRT Guru


Joined: 11 Jun 2022
Posts: 1958

PostPosted: Fri Nov 10, 2023 14:14    Post subject: Reply with quote
Which version of the 710? x2 for advise to upgrade as the infamous router database is not current.
I won't quote the expletive-laced rant from the other room, but I'm sure there's going to be a request
to move the disclaimer on the landing page since people seem to refuse to read or acknowledge it <lol>

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/11-07-2023-r53915/tplink_tl-wr710nv1/

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/11-07-2023-r53915/tplink_tl-wr710nv2/

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/11-07-2023-r53915/tplink_tl-wr710nv2.1/

Current is 53939, but you should be okay with the above.

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/11-09-2023-r53939/tplink_tl-wr710nv1/

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/11-09-2023-r53939/tplink_tl-wr710nv2/

https://ftp.dd-wrt.com/dd-wrtv2/downloads/betas/2023/11-09-2023-r53939/tplink_tl-wr710nv2.1/

_________________
"The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost

"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio

<fact>code knows no gender</fact>

This is me, knowing I've ruffled your feathers, and not giving a ****
Some people are still hard-headed.

--------------------------------------
Mac Pro (Mid 2012) - Two 2.4GHz 6-Core Intel Xeon E5645 processors 64GB 1333MHz DDR3 ECC SDRAM OpenSUSE Leap 15.5
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12921
Location: Netherlands

PostPosted: Fri Nov 10, 2023 14:25    Post subject: Reply with quote
Good idea moving the disclaimer and make it more visible.
_________________
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
ppgg
DD-WRT Novice


Joined: 07 Nov 2023
Posts: 3

PostPosted: Fri Nov 10, 2023 15:00    Post subject: Great help Reply with quote
Thank you all for your quick answers. i will start reading....and I will keep you posted.
ppgg
DD-WRT Novice


Joined: 07 Nov 2023
Posts: 3

PostPosted: Thu Dec 07, 2023 14:33    Post subject: Connected but chosen location not working Reply with quote
In other words, thank to all the suggestions I was able to fix the time and it finally worked and connected to the VPN. However, when I do a Whats my IP I get a location that is NOT the location I chose. I read a lot of other threads, made some adjustments as indicated, but still no luck. Any suggestion will be appreciated. This is what I see in STATUS:
State
Client: CONNECTED SUCCESS
Local Address: 10.98.0.206
Remote Address: 10.98.0.205

Status
VPN Client Stats
TUN/TAP read bytes 5446741
TUN/TAP write bytes 28018242
TCP/UDP read bytes 29556356
TCP/UDP write bytes 6833082
Auth read bytes 28118434
pre-compress bytes 0
post-compress bytes 0
pre-decompress bytes 0
post-decompress bytes 0

Log
Clientlog:
20231206 12:35:55 W WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
20231206 12:35:55 VERIFY KU OK
20231206 12:35:55 Validating certificate extended key usage
20231206 12:35:55 ++ Certificate has EKU (str) TLS Web Server Authentication expects TLS Web Server Authentication
20231206 12:35:55 NOTE: --mute triggered...
20231206 12:35:56 3 variation(s) on previous 3 message(s) suppressed by --mute
20231206 12:35:56 I [Server-10764-0a] Peer Connection Initiated with [AF_INET]216.24.212.192:1195
20231206 12:35:56 PUSH: Received control message: 'PUSH_REPLY redirect-gateway def1 dhcp-option DNS 10.98.0.1 comp-lzo no route 10.98.0.1 topology net30 ping 10 ping-restart 60 ifconfig 10.98.0.206 10.98.0.205 peer-id 47 cipher AES-256-GCM'
20231206 12:35:56 OPTIONS IMPORT: timers and/or timeouts modified
20231206 12:35:56 OPTIONS IMPORT: compression parms modified
20231206 12:35:56 NOTE: --mute triggered...
20231206 12:35:56 6 variation(s) on previous 3 message(s) suppressed by --mute
20231206 12:35:56 Data Channel: using negotiated cipher 'AES-256-GCM'
20231206 12:35:56 NCP: overriding user-set keysize with default
20231206 12:35:56 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
20231206 12:35:56 NOTE: --mute triggered...
20231206 12:35:56 1 variation(s) on previous 3 message(s) suppressed by --mute
20231206 12:35:56 net_route_v4_best_gw query: dst 0.0.0.0
20231206 12:35:56 net_route_v4_best_gw result: via 192.168.1.254 dev br0
20231206 12:35:56 I TUN/TAP device tun1 opened
20231206 12:35:56 I net_iface_mtu_set: mtu 1500 for tun1
20231206 12:35:56 I net_iface_up: set tun1 up
20231206 12:35:56 I net_addr_ptp_v4_add: 10.98.0.206 peer 10.98.0.205 dev tun1
20231206 12:35:56 net_route_v4_add: 216.24.212.192/32 via 192.168.1.254 dev [NULL] table 0 metric -1
20231206 12:35:56 net_route_v4_add: 0.0.0.0/1 via 10.98.0.205 dev [NULL] table 0 metric -1
20231206 12:35:56 net_route_v4_add: 128.0.0.0/1 via 10.98.0.205 dev [NULL] table 0 metric -1
20231206 12:35:56 net_route_v4_add: 9.9.9.9/32 via 10.98.0.205 dev [NULL] table 0 metric -1
20231206 12:35:56 net_route_v4_add: 149.112.112.112/32 via 10.98.0.205 dev [NULL] table 0 metric -1
20231206 12:35:56 net_route_v4_add: 8.8.8.8/32 via 10.98.0.205 dev [NULL] table 0 metric -1
20231206 12:35:56 net_route_v4_add: 10.98.0.1/32 via 10.98.0.205 dev [NULL] table 0 metric -1
20231206 12:35:57 I Initialization Sequence Completed
20231206 12:36:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231206 12:36:19 D MANAGEMENT: CMD 'state'
20231206 12:36:19 MANAGEMENT: Client disconnected
20231206 12:36:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231206 12:36:19 D MANAGEMENT: CMD 'state'
20231206 12:36:19 MANAGEMENT: Client disconnected
20231206 12:36:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231206 12:36:19 D MANAGEMENT: CMD 'state'
20231206 12:36:19 MANAGEMENT: Client disconnected
20231206 12:36:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231206 12:36:19 D MANAGEMENT: CMD 'status 2'
20231206 12:36:19 MANAGEMENT: Client disconnected
20231206 12:36:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231206 12:36:19 D MANAGEMENT: CMD 'log 500'
20231206 12:36:19 MANAGEMENT: Client disconnected
20231206 13:32:16 VERIFY KU OK
20231206 13:32:16 Validating certificate extended key usage
20231206 13:32:16 ++ Certificate has EKU (str) TLS Web Server Authentication expects TLS Web Server Authentication
20231206 13:32:16 NOTE: --mute triggered...
20231207 07:40:18 157 variation(s) on previous 3 message(s) suppressed by --mute
20231207 07:40:18 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 07:40:19 D MANAGEMENT: CMD 'state'
20231207 07:40:19 MANAGEMENT: Client disconnected
20231207 07:40:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 07:40:19 D MANAGEMENT: CMD 'state'
20231207 07:40:19 MANAGEMENT: Client disconnected
20231207 07:40:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 07:40:19 D MANAGEMENT: CMD 'state'
20231207 07:40:19 MANAGEMENT: Client disconnected
20231207 07:40:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 07:40:19 D MANAGEMENT: CMD 'status 2'
20231207 07:40:19 MANAGEMENT: Client disconnected
20231207 07:40:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 07:40:19 D MANAGEMENT: CMD 'log 500'
20231207 07:40:19 MANAGEMENT: Client disconnected
20231207 08:18:57 VERIFY KU OK
20231207 08:18:57 Validating certificate extended key usage
20231207 08:18:57 ++ Certificate has EKU (str) TLS Web Server Authentication expects TLS Web Server Authentication
20231207 08:18:57 NOTE: --mute triggered...
20231207 08:38:50 5 variation(s) on previous 3 message(s) suppressed by --mute
20231207 08:38:50 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:38:50 D MANAGEMENT: CMD 'state'
20231207 08:38:50 MANAGEMENT: Client disconnected
20231207 08:38:50 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:38:50 D MANAGEMENT: CMD 'state'
20231207 08:38:50 MANAGEMENT: Client disconnected
20231207 08:38:50 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:38:50 D MANAGEMENT: CMD 'state'
20231207 08:38:50 MANAGEMENT: Client disconnected
20231207 08:38:50 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:38:50 D MANAGEMENT: CMD 'status 2'
20231207 08:38:50 MANAGEMENT: Client disconnected
20231207 08:38:50 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:38:50 D MANAGEMENT: CMD 'log 500'
20231207 08:38:50 MANAGEMENT: Client disconnected
20231207 08:46:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:46:19 D MANAGEMENT: CMD 'state'
20231207 08:46:19 MANAGEMENT: Client disconnected
20231207 08:46:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:46:19 D MANAGEMENT: CMD 'state'
20231207 08:46:19 MANAGEMENT: Client disconnected
20231207 08:46:19 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:46:19 D MANAGEMENT: CMD 'state'
20231207 08:46:19 MANAGEMENT: Client disconnected
20231207 08:46:20 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:46:20 D MANAGEMENT: CMD 'status 2'
20231207 08:46:20 MANAGEMENT: Client disconnected
20231207 08:46:20 MANAGEMENT: Client connected from [AF_INET]127.0.0.1:16
20231207 08:46:20 D MANAGEMENT: CMD 'log 500'
19691231 19:00:00


Furthermore, this is the settings:

Don't really know why: I chose Atlanta USA as location and yet I get Milano IT when I do the whats my IP. Any idea? Thank you in advance.
egc
DD-WRT Guru


Joined: 18 Mar 2014
Posts: 12921
Location: Netherlands

PostPosted: Thu Dec 07, 2023 14:50    Post subject: Reply with quote
Your screenshot shows you are still using an outdated build current build is 54475.

Furthermore your WAN ip is the same as your routers IP not sure what you really want with this router.
Usually the WAN ip is set to automatic DHCP and the routers IP is outside the subnet of the upstream router. If the router is directly connected to the internet you can leave the routers IP at 192.168.1.1 in case it is not, use something like 192.168.131.1 for router IP

_________________
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
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware 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