I followed the steps in the OEM installation method, but when I try to connect via SSH it gives the following message Connection closed by 192.168.1.1 port 22.
Running with the -v flag gives more details:
OpenSSH_9.1p1, OpenSSL 3.0.7 1 Nov 2022
debug1: Reading configuration data /home/dudu/.ssh/config
debug1: /home/dudu/.ssh/config line 1: Applying options for 192.168.*
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 192.168.1.1 [192.168.1.1] port 22.
debug1: Connection established.
debug1: identity file /home/dudu/.ssh/id_rsa type -1
debug1: identity file /home/dudu/.ssh/id_rsa-cert type -1
debug1: identity file /home/dudu/.ssh/id_ecdsa type -1
debug1: identity file /home/dudu/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/dudu/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/dudu/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/dudu/.ssh/id_ed25519 type -1
debug1: identity file /home/dudu/.ssh/id_ed25519-cert type -1
debug1: identity file /home/dudu/.ssh/id_ed25519_sk type -1
debug1: identity file /home/dudu/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/dudu/.ssh/id_xmss type -1
debug1: identity file /home/dudu/.ssh/id_xmss-cert type -1
debug1: identity file /home/dudu/.ssh/id_dsa type -1
debug1: identity file /home/dudu/.ssh/id_dsa-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.1
debug1: Remote protocol version 2.0, remote software version dropbear_0.46
debug1: compat_banner: no match: dropbear_0.46
debug1: Authenticating to 192.168.1.1:22 as 'root'
debug1: load_hostkeys: fopen /home/dudu/.ssh/known_hosts: No such file or directory
debug1: load_hostkeys: fopen /home/dudu/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: diffie-hellman-group1-sha1
debug1: kex: host key algorithm: ssh-rsa
debug1: kex: server->client cipher: 3des-cbc MAC: hmac-sha1 compression: none
debug1: kex: client->server cipher: 3des-cbc MAC: hmac-sha1 compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
Connection closed by 192.168.1.1 port 22
Searching for the debug1: expecting SSH2_MSG_KEX_ECDH_REPLY I've found that some people managed to get it working by changing the adapter MTU. Tried with 1200, 1350 and 1400 but nothing changed.
P.S.: I've changed my SSH config file to enable some deprecated algorithms that the router seems to require.
Host 192.168.1.1
KexAlgorithms +diffie-hellman-group1-sha1
Ciphers +3des-cbc
HostKeyAlgorithms +ssh-rsa
Can you access the router from browser with 192.168.1.1...
Nope, so I assumed that the Web UI isn't installed by default.
I've flashed the one described on the router page, version 22.03.3
Currently snapshot is supported as far as i can see so i think you have bricked your devicehttps://openwrt.org/toh/tp-link/archer_c6_v3
You need to upbrick it and try again. With current firmware. I also have that same device as i have that same device and install it just a few days ago.
How you have installed did you have done that with upgrade option of tp link?
Preess
How far you have done like have you successfully flash
I assume that it was successful. After the file upload I let it do it's thing. After a while I got a black screen on the browser and tried to connect on the new IP, but nothing.
Waited for ~10 minutes before rebooting and nothing. The WAN and LAN LED's turn on and off when I plug and unplug the cables.
You need to upbrick it and try again. With current firmware
Damn...where can I start? I'm reading the debricking section of the router page, but never heard of UART before so...I'm a bit lost now
I also have a xiaomi router and bricked but ultimately unbricked and installed and had a awesome experience so don't worry.
Connect your router with your pc using a lan cable and see if you can get a ip whether dhcp works or not.
And see if you are in linux ip a if not check network and see if your device get an ip.
Can you show a picture of your router. And what are the lights working indicating so someone who have bricked that device can identify the issue.
If you are sure that it is tp link archer c6 v3 then you should install snapshot which was recommended.
To bring back the network again I picked up an old crappy router that was laying around to use as a main router for now.
I've connected the C6 into it to see if it shows up on the device list but it doesn't...
This router (the old crappy one) also seems to not support the 255.255.0.0 subnet mask. That might be why the C6 doesn't show up?
I've disconnected the C6 from the temporary router and the SSH command gives the same output instead of an error like a timeout or something...so something on the router must be using the 192.168.1.1... I think that I've messed up on something very dumb...
With out knowing that is on your end it is hard to predict
I find guide but don't do it right now.
https://www.tp-link.com/in/support/faq/1482/
I feel so stupid now... I've connected the router on my laptop only and no IP was given. Configured an static one and now I can SSH into the router 
.
The Web UI still does not show on the browser tho.
Run
opkg update
opkg install luci
for webUI.
Router will need internet access for it to work.
Also do the last part install the sys-upgrade from luci firmware upgrade.
The opkg update gave some errors:
Collected errors:
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/targets/ramips/mt7621/packages/Packages.sig, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/mipsel_24kc/luci/Packages.sig, wget returned 4.
* opkg_download: Check your network settings and connectivity.
* opkg_download: Failed to download https://downloads.openwrt.org/snapshots/packages/mipsel_24kc/packages/Packages.gz, wget returned 4.
* opkg_download: Check your network settings and connectivity.
The connection seems unstable for some reason, which is weird because it was fine on the temporary router...Can it be a problem on the router or is just the ISP instability?
root@OpenWrt:~# ping google.com
PING google.com (142.251.129.174): 56 data bytes
64 bytes from 142.251.129.174: seq=27 ttl=58 time=3.366 ms
64 bytes from 142.251.129.174: seq=28 ttl=58 time=7.206 ms
64 bytes from 142.251.129.174: seq=29 ttl=58 time=7.099 ms
64 bytes from 142.251.129.174: seq=30 ttl=58 time=7.132 ms
64 bytes from 142.251.129.174: seq=31 ttl=58 time=7.190 ms
64 bytes from 142.251.129.174: seq=32 ttl=58 time=7.124 ms
64 bytes from 142.251.129.174: seq=33 ttl=58 time=7.057 ms
64 bytes from 142.251.129.174: seq=34 ttl=58 time=7.035 ms
^C
--- google.com ping statistics ---
66 packets transmitted, 8 packets received, 87% packet loss
round-trip min/avg/max = 3.366/6.651/7.206 ms