Early Access ER605 V2_2.1.4_Build 20230727 Beta Firmware For Trial (Released on Aug 2nd, 2023)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi @Clive_A !
For my configuration, can I export it through the forum or via the ticket you opened for me ?
I joined to you the config in attached file.
For Wireshark, it's not possible because I switch back to my ER605 v1 for the moment and the v2 is off for the moment. Actually I need my network to work at home and probably do the swap to the ER605 v2 during the week-end when I'm alone.
Cheers, ElMajor76.
Hi @yavin
So, if you see the post I sent to ElMajor earlier, can you reply to me with the info I need? I need information about the mDNS.
https://community.tp-link.com/en/business/forum/topic/615998?replyId=1242992
If you can provide details about your mDNS, I can collect the backup of yours and see what I can do and help.
If you are able to provide the Wireshark capture of your mDNS, that would be great to check if your Bonjour Service is correct.
https://www.tp-link.com/en/support/faq/3235/
I want to find out if your device is actually broadcasting them DNS and whether your Bonjour Service is set correctly. Because the Wireshark can reflect the correct and full-service parameters.
e.g. airplay, its correct, and the full Bonjour Service protocol should be like _airplay_tcp.local
I tested Wireguard Connection (tplink as Wireguard client connected to wireguard server ) and i found BUG
Configuration
LAN1
192.168.42.1 simpley router with port redirect UDP 41820 to Linux Server
192.168.42.2 Linux Server with Wireguard Server WAN ip 91.X.X.X port 41820 , WG interface : 10.65.48.1 (NAT etc itp enable)
192.168.42.3 Windows OS
LAN2
192.168.30.1 Router Tplinka ER-605 V2 fw2.1.4 with wireguard WG interface 10.65.48.2
192,168.30.2 Windows - my machine where do i ping from
When Allow IP is set to .0.0.0.0/0 i can Ping 10.65.48.1 , 192.168.42.1, 192.168.42.2, 192.168.42.3 - everything works!
but when allow ip i set to 192.168.42.0/24 or 10.65.48.0/24 - I can't ping anything
In Wireguard Windows client config works without problem with AllowedIPs = 10.65.48.0/24, 192.168.42.0/24, ::/1, 8000::/1 (it passes traffic to lan2 through vpn but regular internet traffic does not go through vpn, and that's how it should work)
In addition, the endpoint does not allow you to enter the hostname, it only requires the ip address
what i understand him is that he is trying to say that you cannot use a port that has already been taken. if you enable remote management, the 80 and 443 are enabled for remote access. you can port forward 80 and 443 to a local service, but this is based on the precondition that 80 and 443 are not enabled by "remote management".
do you know this feature? is it enabled? if enabled, you type in the ip in the address bar and you access your router's web page by your public ip. 80 and 443 are used by default.
