R605 beta firmware 1.1.0 causes strange behavior that appears in system log
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
First I had issue with my router (Archer C6 v2), in access point mode, showing orange led and partly loosing internet. It is connected to an easy smart switch that is connected to the R605.
So I went to investigate and found strange notices in system log.
First a firewall warnings:
[...mac address...] detected Large Ping attack and dropped 3 packets.
It appears sometimes.
But what appears repeatedly is:
"DHCP Server allocated IP address 192.168.51.184 for the client[MAC: ...address...]"
For many IP addresses, repeatedly in sequence.
Also, a LOGGER notice about the two wan ports being down and up.
and
"WAN: DHCP client lease expired. Began renewing the lease."
What is going on?
Tried to set up static IP on the R605 to connect to the the ISP modems. After that, one ISP stayed desconnected, the other connected.
It makes the whole network instable. Devices are getting internet mostly but with some interruption.
I tried to reserve address of my C6 router to see if the R605 keep wanting to reallocate it, it seems it stopped showing that line for that IP but continues for others. And what is more scary, it leases address for the wan quite often.
"WAN: DHCP client lease expired. Began renewing the lease."
Is it some kind of attack from outside, or is it a bug in this beta firmware?
I need to know if I have to replace is temporarely with the previous R470T+ because the last official firmware of the R605 can't stop intervlan.
"WAN: DHCP client lease expired. Began renewing the lease."
You should connect a PC to replace the R605 and see if the network come stable again. This seems is a problem on the ISP side.
[...mac address...] detected Large Ping attack and dropped 3 packets.
This one is quick normal, which means the firewall is protecting your network and works fine.
Today I had issues mostly about websites not loading, while speedtest worked. And some other sites loaded, too.
I ruled all LAN to WAN1 port to avoid traffic to go to the WAN2 that is a 4G modem. And these issues vanished, so far.
However the web UI of the R605 seems to have a bug, in WAN2 tab there was no Connect and Disconnect button, only Save. So, I couldn't even disconnect it. The missing buttons reappeared only when I changed Static IP to Dynamic for WAN2.
Other strange thing is, I reserved address for some devices, later decided to remove the reservation.
After that, in the DHCP Client list tab for those devices reappeared the icon of the floppy disk, so you have the option to reserve that.
But in the same time it still says Permanent when they should have the count down.
Another screenshot from the System Log.
There are several routers in either router mode or AP mode connected to the R605 via switches.
However... why is that one specific router (with IP ends with .173) that appears in system log so frequently? It's an Archer C6 v2, currently in AP mode and with beta firmware.
It appears even when there is no devices connected to the C6.
It bothers me a lot, WTF is happening?
Dear @Arion,
No, there is no Connect and Disconnect button when the WAN is configured with Static IP. Unlike Dynamic IP or other connection types, Static IP doesn't need to click Connect to activate the connection, and the gateway can use the static IP addresses to initiate the connection directly.
If you want to disconnect the WAN connection from the web UI, you may clear the WAN setup or input invalid WAN IP addresses.
You'll know It's normal if you understand how the DHCP works. Those clients showing with Permanent haven't renewed the DHCP IP addresses, it will change once they renew the IP address from the DHCP server before the address lease expires.
Another screenshot about odd behaviour of the R605 in beta firmware.
Look at the timestamps! The same device appearing with the same timestamp multiple times.
Or is this just multiple gadgets connecting in the same time via a router or hub?
I haven't recognized that connected device but its MAC address started with 70:c9:4e
