ASUS RT-AC1900P Firmware version 3.0.0.4.384.20287

[dieter]

Hi dieter,

I'm not sure. I checked for the update in the router and it wasn’t there. At the link above, choose “Others” from drop down tab and it’s there.

It has been there under Others and W10 64bit for days. That is why I was wondering why the router FW update does not see it. Asus says the FW has to be on other servers for the router to see it.
I'll way until Asus updates its servers.

 

[scjr]

It has been there under Others and W10 64bit for days. That is why I was wondering why the router FW update does not see it. Asus says the FW has to be on other servers for the router to see it.
I'll way until Asus updates its servers.

Okay.

I downloaded and updated via the router. All went well.

 

[dieter]

Okay.

I downloaded and updated via the router. All went well.

Thanks, Let us know about any issues, please. Someone posted that 2.4Ghz WiFi was not working.

 

[scjr]

Thanks, Let us know about any issues, please. Someone posted that 2.4Ghz WiFi was not working.

I upgraded right over 10007.

2.4GHz is working fine. 3 days of uptime thus far.

 

[Ronald Schwerer]

Someone posted that 2.4Ghz WiFi was not working.

One guy. And he had a configuration problem. His 2.4Ghz wasn't even working for him before installing 3.0.0.4.384.20287. He did a NVRAM reset (restored everything to factory) and the problem went away. You misread his post and now you're starting a rumor.

 

[dieter]

This morning, router was able to upgrade FW from Asus server. 2.4Ghz is working fine...

 

[Blinkyz]

Except Daylight Saving Time (DST) in most of the United States starts on the 2nd Sunday in March and ends on the 1st Sunday in November (11). So still wrong.

Switch to Greenwich time ---> Apply ----> and switch back to your time zone, it should fix it without manually enter the month

 

[scjr]

I’m curious if anyone is seeing the message below in your logs, when changing channels on 5GHz? I changed channels from 44 to 48 tonight and with the regular message that logs, this was part of it:

Jan 30 19:47:00 lldpd[292]: unable to send packet on real device for eth1: Network is down
Jan 30 19:47:00 lldpd[292]: unable to send packet on real device for eth2: No such device or address

Wireless is working fine. Nothing is wrong. Just curious if any others are seeing the same?

 

[Andreaz]

Updated to .20287 today on my two AC68U, in aimesh setup, with a eth backhaul. Running perfect with first version for 2 weeks.
Then I added a new ac68U to the system today, wireless node. (No eth backh.)
Put this in my garage, and it show up in the app as a active node. Looking good.
But my iPhone X ask for password on both 2.4 and 5 Ghz connection on this node. Is this normal?
I entered the same password as my main-router, and got connected, but I was under the impression that all units should see all nodes as 1?

 

[arthurlien]

Updated to .20287 today on my two AC68U, in aimesh setup, with a eth backhaul. Running perfect with first version for 2 weeks.
Then I added a new ac68U to the system today, wireless node. (No eth backh.)
Put this in my garage, and it show up in the app as a active node. Looking good.
But my iPhone X ask for password on both 2.4 and 5 Ghz connection on this node. Is this normal?
I entered the same password as my main-router, and got connected, but I was under the impression that all units should see all nodes as 1?

Can you send feedback with system log, wifi log and cfg file by Feedback function ? And please add your SNB Nickname in description field.

 

[Andreaz]

Can you send feedback with system log, wifi log and cfg file by Feedback function ? And please add your SNB Nickname in description field.

Sent by email. The internal feedback reported an error.

 

[scjr]

I’m curious if anyone is seeing the message below in your logs, when changing channels on 5GHz? I changed channels from 44 to 48 tonight and with the regular message that logs, this was part of it:

Jan 30 19:47:00 lldpd[292]: unable to send packet on real device for eth1: Network is down
Jan 30 19:47:00 lldpd[292]: unable to send packet on real device for eth2: No such device or address

Wireless is working fine. Nothing is wrong. Just curious if any others are seeing the same?

Just to update the thread, @arthurlien explained that this entry is normal and used for communication between the AiMesh nodes. See here:

https://www.snbforums.com/threads/o...-supported-products.43125/page-39#post-377459