Port forwarding stops working after reboot

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

Port forwarding stops working after reboot

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Port forwarding stops working after reboot
Port forwarding stops working after reboot
2024-04-29 13:32:21 - last edited 2024-05-01 22:15:12
Model: Archer AX3000  
Hardware Version: V1
Firmware Version: 1.2.6 Build 20231130 rel.36135(5553)

Port forwarding stops working on my router after a reboot. Additionally every week or so it will stop forwarding by itself without a reboot.

 

Port forwarding will start to work, when I go into the NAT Forwarding page and disable and immediately enable the rule using the "status" slider button.

 

Configuration:

  • Router is directly connected to the cable modem. No other routers are present. No static routes. No Port triggering rules, or DMZ. 
  • Router UPnP is enabled but not used by the target device.  There are no external port conflicts.
  • Target Device: DHCP with a reserved IP address on the router, wifi on the IoT network,  External port 4355, internal port 80, TCP and UDP enabled (All protocol setting)
  • Only one port forwarding rule:4355 to 80. No other forwarding rules are present.

---------------------------------------

 

Update: Router was automatically reboot at 3AM, but the "virtual server" was not setup until 6:23AM when I manually disabled/enabled the port forwarding.

 

 

####################################################################
#                  Archer AX55 System Log
# Time = 2024-04-29 08:03:09
# H-Ver = 1.0.0 ; S-Ver = 1.2.6 Build 20231130 rel.36135
# LAN: I = 10.0.0.1 ; M = 255.255.255.0 ; MAC = 5C:62:8B:A8:0C:0C 
# WAN: W = dhcp ; I = 98.245.???.??? ; M = 255.255.248.0 ; MAC = 5C:62:8B:???:???:???
#      G = 98.245.208.1 ; D1 = 75.75.75.75 ; D2 = 75.75.76.76 
# Clients connected: 27 ; WI-FI : 23 
####################################################################
2024-04-29 07:27:50 usbshare[27539]: <5> 291254 MiniDLNA start
2024-04-29 07:27:50 usbshare[27539]: <5> 291252 ProFTPd start
2024-04-29 07:27:50 usbshare[27539]: <5> 291250 Samba start
2024-04-29 07:27:50 usbshare[27539]: <5> 291255 MiniDLNA stop
2024-04-29 07:27:50 usbshare[27539]: <5> 291253 ProFTPd stop
2024-04-29 07:27:50 usbshare[27539]: <5> 291251 Samba stop
2024-04-29 07:27:50 usbshare[27556]: <5> 291254 MiniDLNA start
2024-04-29 07:27:50 usbshare[27556]: <5> 291252 ProFTPd start
2024-04-29 07:27:50 usbshare[27556]: <5> 291250 Samba start
2024-04-29 07:27:50 usbshare[27556]: <5> 291255 MiniDLNA stop
2024-04-29 07:27:50 usbshare[27556]: <5> 291253 ProFTPd stop
2024-04-29 07:27:50 usbshare[27556]: <5> 291251 Samba stop


2024-04-29 06:23:35 nat[15899]: <5> 211054 Virtual server created succeeded[ex-port:4355 ip:10.0.0.89 in-port:80 protocol:all]

 

2024-04-29 06:23:33 nat[15899]: <6> 211501 Initialization succeeded
2024-04-29 06:23:32 nat[15899]: <6> 211501 Initialization succeeded
2024-04-29 06:23:30 nat[15593]: <6> 211501 Initialization succeeded
2024-04-29 06:23:29 nat[15593]: <6> 211501 Initialization succeeded
2024-04-29 03:05:55 led-controller[1118]: <6> 288051 Start to run WAN1_ON
2024-04-29 03:05:55 led-controller[1118]: <6> 288051 Start to run WAN0_OFF
2024-04-29 03:05:55 led-controller[1118]: <6> 288051 Start to run LAN_ON
2024-04-29 03:05:35 led-controller[1118]: <6> 288051 Start to run WAN1_ON
2024-04-29 03:05:35 led-controller[1118]: <6> 288051 Start to run WAN0_OFF
2024-04-29 03:05:35 led-controller[1118]: <6> 288051 Start to run LAN_ON
 

  0      
  0      
#1
Options

Information

Helpful: 0

Views: 298

Replies: 0

Related Articles