NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New - RAX120 / RAX120v2 Firmware Version 1.2.8.40 Released
New Features:
Supports the XunYou gaming feature (for China only)
Removes the gaming feature, Funjsq (was supported for China only)
Enhancements:
Improves system stability. <Maybe a fix...
I reverted back to firmware version 1.2.3.28 from 1.2.8.40 on my RAX120 v1 router and factory reset it. The logging is now working once again the way it should have in the newer version. I do not know what the firmware developer fixed in version 1.2.8.40 but the logging issue in it was reprehensible in my opinion. I like NetGear's hardware but they need to put way more resources into their firmware development. I am a software engineer and if I had this many bugs in my code I would be fired. Maybe they should actually test their firmware with a smaller group of knowledgeable users before releasing it to the general public. Version control is another issue I have seen. They have fixed bugs in the past then later reintroduce them back into the firmware. I will upgrade to the next version when it comes out and cross my fingers.
Did you factory reset and setup from scratch after you applied v.40?
mudbone wrote:
I reverted back to firmware version 1.2.3.28 from 1.2.8.40 on my RAX120 v1 router and factory reset it. The logging is now working once again the way it should have in the newer version. I do not know what the firmware developer fixed in version 1.2.8.40 but the logging issue in it was reprehensible in my opinion. I like NetGear's hardware but they need to put way more resources into their firmware development. I am a software engineer and if I had this many bugs in my code I would be fired. Maybe they should actually test their firmware with a smaller group of knowledgeable users before releasing it to the general public. Version control is another issue I have seen. They have fixed bugs in the past then later reintroduce them back into the firmware. I will upgrade to the next version when it comes out and cross my fingers.
Yes. Both on V1.2.3.28 and V1.2.8.40 plus I manually entered all the settings for each. I do not trust backups to always restore the settings correctly. Below is a sample of all the "DoS Attack" entries I had in the log over a roughly 23 hour period. I want to see this stuff and I do not want it suppressed. Even if they are not actual DoS Attack's I can see what is scanning my router.
[DoS Attack: ACK Scan] from source: 14.191.135.46, port 17729, Wednesday, November 23, 2022 21:53:57
[DoS Attack: ACK Scan] from source: 14.191.135.46, port 17729, Wednesday, November 23, 2022 21:53:53
[DoS Attack: ACK Scan] from source: 14.191.135.46, port 17729, Wednesday, November 23, 2022 21:53:49
[DoS Attack: SYN/ACK Scan] from source: 95.217.30.172, port 443, Wednesday, November 23, 2022 21:16:09
[DoS Attack: SYN/ACK Scan] from source: 95.217.30.172, port 443, Wednesday, November 23, 2022 21:16:09
[DoS Attack: ACK Scan] from source: 185.224.128.7, port 30569, Wednesday, November 23, 2022 20:35:42
[DoS Attack: TCP/UDP Echo] from source: 8.8.8.8, port 53, Wednesday, November 23, 2022 19:55:09
[DoS Attack: SYN/ACK Scan] from source: 5.75.245.238, port 443, Wednesday, November 23, 2022 18:54:31
[DoS Attack: SYN/ACK Scan] from source: 107.149.2.16, port 80, Wednesday, November 23, 2022 18:50:07
[DoS Attack: ACK Scan] from source: 180.248.8.52, port 53185, Wednesday, November 23, 2022 18:14:49
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 17:57:01
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 17:57:01
[DoS Attack: ACK Scan] from source: 185.224.128.7, port 11213, Wednesday, November 23, 2022 17:40:37
[DoS Attack: NULL Scan] from source: 60.161.81.116, port 404, Wednesday, November 23, 2022 17:09:56
[DoS Attack: SYN/ACK Scan] from source: 5.75.245.238, port 443, Wednesday, November 23, 2022 17:02:10
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 14:47:32
[DoS Attack: ACK Scan] from source: 185.224.128.7, port 3491, Wednesday, November 23, 2022 14:45:18
[DoS Attack: SYN/ACK Scan] from source: 195.208.6.1, port 53, Wednesday, November 23, 2022 14:41:22
[DoS Attack: TCP/UDP Chargen] from source: 172.105.189.111, port 30219, Wednesday, November 23, 2022 14:14:16
[DoS Attack: ACK Scan] from source: 208.85.46.22, port 443, Wednesday, November 23, 2022 13:34:14
[DoS Attack: ACK Scan] from source: 208.85.46.22, port 443, Wednesday, November 23, 2022 13:32:13
[DoS Attack: ACK Scan] from source: 208.85.46.22, port 443, Wednesday, November 23, 2022 13:31:10
[DoS Attack: ACK Scan] from source: 208.85.46.22, port 443, Wednesday, November 23, 2022 13:30:38
[DoS Attack: SYN/ACK Scan] from source: 5.75.245.238, port 443, Wednesday, November 23, 2022 13:21:49
[DoS Attack: SYN/ACK Scan] from source: 149.20.190.19, port 1972, Wednesday, November 23, 2022 12:25:15
[DoS Attack: ACK Scan] from source: 185.224.128.7, port 23427, Wednesday, November 23, 2022 11:49:32
[DoS Attack: SYN/ACK Scan] from source: 51.79.163.159, port 30120, Wednesday, November 23, 2022 11:35:50
[DoS Attack: Ascend Kill] from source: 8.8.8.8, port 53, Wednesday, November 23, 2022 11:30:44
[DoS Attack: TCP/UDP Echo] from source: 94.102.61.29, port 44918, Wednesday, November 23, 2022 10:58:33
[DoS Attack: RST Scan] from source: 103.167.159.250, port 18189, Wednesday, November 23, 2022 10:10:29
[DoS Attack: TCP/UDP Chargen] from source: 192.46.221.241, port 32356, Wednesday, November 23, 2022 09:49:04
[DoS Attack: ACK Scan] from source: 185.224.128.7, port 15171, Wednesday, November 23, 2022 08:54:28
[DoS Attack: SYN/ACK Scan] from source: 5.75.245.238, port 443, Wednesday, November 23, 2022 08:47:47
[DoS Attack: SYN/ACK Scan] from source: 91.218.213.49, port 8000, Wednesday, November 23, 2022 08:23:31
[DoS Attack: SYN/ACK Scan] from source: 91.218.213.49, port 8000, Wednesday, November 23, 2022 08:23:31
[DoS Attack: WinNuke Attack] from source: 60.30.162.22, port 59779, Wednesday, November 23, 2022 07:58:15
[DoS Attack: SYN/ACK Scan] from source: 40.113.105.173, port 443, Wednesday, November 23, 2022 07:21:15
[DoS Attack: SYN/ACK Scan] from source: 195.208.6.1, port 53, Wednesday, November 23, 2022 05:54:47
[DoS Attack: SYN/ACK Scan] from source: 195.208.6.1, port 53, Wednesday, November 23, 2022 05:54:47
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 05:47:50
[DoS Attack: SYN/ACK Scan] from source: 5.75.245.238, port 443, Wednesday, November 23, 2022 05:36:05
[DoS Attack: SYN/ACK Scan] from source: 195.208.6.1, port 53, Wednesday, November 23, 2022 04:52:43
[DoS Attack: SYN/ACK Scan] from source: 88.198.21.103, port 29825, Wednesday, November 23, 2022 03:58:15
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 03:01:35
[DoS Attack: SYN/ACK Scan] from source: 40.77.45.24, port 30208, Wednesday, November 23, 2022 02:49:36
[DoS Attack: SYN/ACK Scan] from source: 195.208.6.1, port 53, Wednesday, November 23, 2022 01:27:26
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:10:14
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:09:59
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:09:43
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:09:28
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:09:13
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:08:57
[DoS Attack: ACK Scan] from source: 162.247.241.14, port 443, Wednesday, November 23, 2022 01:08:42
[DoS Attack: SYN/ACK Scan] from source: 51.81.82.90, port 22, Wednesday, November 23, 2022 00:50:57
[DoS Attack: SYN/ACK Scan] from source: 51.81.82.90, port 22, Wednesday, November 23, 2022 00:50:47
[DoS Attack: SYN/ACK Scan] from source: 45.95.55.236, port 80, Wednesday, November 23, 2022 00:39:39
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 00:04:07
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 00:04:06
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 00:04:06
[DoS Attack: SYN/ACK Scan] from source: 35.214.109.143, port 443, Wednesday, November 23, 2022 00:04:06
[DoS Attack: ACK Scan] from source: 8.240.217.254, port 80, Tuesday, November 22, 2022 23:43:54
[DoS Attack: ACK Scan] from source: 8.240.217.254, port 80, Tuesday, November 22, 2022 23:43:24
[DoS Attack: ACK Scan] from source: 199.187.116.122, port 30106, Tuesday, November 22, 2022 23:20:39Do a lookup on those IP addresses to see where they are coming from. The logs are just indicating of what the router is preventing.
