Lan connection lost wont reconnect by creating a weird port forward rule BUG

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Lan connection lost wont reconnect by creating a weird port forward rule BUG

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Lan connection lost wont reconnect by creating a weird port forward rule BUG
Lan connection lost wont reconnect by creating a weird port forward rule BUG
2021-02-06 20:49:11 - last edited 2021-04-18 09:34:16
Model: ER605 (TL-R605)  
Hardware Version: V1
Firmware Version: 1.0.0 Build 20200930 Rel.36519


my setup: WAN -> TL-r605 only 1 LAN port connected to switch -> T1500G-8T v2.0 -> computers and waps

So I was tinkering with tl-r605 through omada v4.2.8 controller
interface: wan only
source port: all of it
destination IP: to my test pc
destination ports: all of it

after creating and applying the rule the tl-r605 LAN port just gave up on connecting. the lan port on tl-r605 would light up for 4 seconds then disappear for another 4 seconds. it just keep doing that forever. my switch t1500g-8t v2.0 on lan port would not even light up anymore (connected to tl-r605) all other ports working fine. I restarted / re-adopt / restore previous configuration in the controller and the tl-r605 and the lan connection works but after how many hours the lan port would just stop working and the same 4 seconds green light on 4 second off would repeat forever. all devices connected had gateways connected to some random IP as tl-r605 could not be found

well I reset the tl-r605 and made it my third party router with a raspberry-pi behind just to see if the lan ever gives up again.so i replaced my tl-r605 it with my old stable tomato router and everything works just fine. am afraid to put it back to my main network

these are the only logs I could salvage during the whole time from 5:49 am to 7:45 am there is no internet

VFS-MAIN-ROUTER was disconnected.

Feb 06, 2021 09:02:15  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 2 packets.

Feb 06, 2021 08:04:14  am

VFS-MAIN-ROUTER was disconnected.

Feb 06, 2021 07:45:15  am

VFS-MAIN-ROUTER was disconnected.

Feb 06, 2021 07:15:05  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 3 packets.

Feb 06, 2021 07:10:46  am

VFS-MAIN-ROUTER was disconnected.

Feb 06, 2021 06:09:05  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 5 packets.

Feb 06, 2021 05:59:28  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 6 packets.

Feb 06, 2021 05:49:26  am

VFS-MAIN-ROUTER was disconnected.

Feb 06, 2021 05:44:25  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 20 packets.

Feb 06, 2021 05:27:41  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 7 packets.

Feb 06, 2021 05:11:04  am

VFS-MAIN-ROUTER detected Ping of Death attack and dropped 23 packets.

Feb 06, 2021 04:56:00  am


hope tp-link fixes this bug crying

  0      
  0      
#1
Options