What's new

[Release 384/NG] Asuswrt-Merlin 384.4 is now available

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
After reset to factory defaults wait 10 minutes before configuring or importing from @john9527 utility.

I will. Can you tell me if that 10-minute delay is for the sake of the freshly-wiped NVRAM (letting something settle?), or is just to give all software/radios a chance to spool up completely before configuring?

I ask both because I want to understand, and because, for some reason I don't grasp, I have to power-cycle the RT-AC3200 before I can get SSH to work.

So, should I give it another 10-minute rest after power cycling?
 
I will. Can you tell me if that 10-minute delay is for the sake of the freshly-wiped NVRAM (letting something settle?), or is just to give all software/radios a chance to spool up completely before configuring?

I ask both because I want to understand, and because, for some reason I don't grasp, I have to power-cycle the RT-AC3200 before I can get SSH to work.

So, should I give it another 10-minute rest after power cycling?
Ten minutes without drives allows the router to complete the reset. Power cycling after this is done your normal way (no 10 minute wait) so when you enable ssh in the webui apply the settings and connect via ssh. The reset to factory defaults is a big task.
 
Just a quick question. Was the usb drive plugged in during the flash and reset phase? I would remove all drives and try again.

Okay, done. I did the following:
  1. Unplugged the USB flash drive from the RT-AC3200

  2. Re-Uploaded 384.4

  3. Initiated a Factory Reset from the GUI

  4. Waited for 10 minutes after reboot

  5. Turned SSH on, then turned the power switch off (I have no idea why I have to power-cycle to make SSH accept a connection, but even a Reboot from the GUI doesn't get the job done)
  6. With the power switch off, unplugged the power supply, turned power switch back on for five seconds, turned power switch off, plugged the power back up, and turned the power switch back on.

  7. Plugged in a USB flash drive containing my NVRAM settings backup

  8. Restored Settings and rebooted
Sadly, I'm back to having all sorts of problems, as before: the Ecobee thermostat, Ubuntu laptop, some Chromecasts, and some LIFX bulbs now can't connect to Wi-Fi.

So, I'll be returning to 384.3 shortly, and will report back. Thanks again for your help, skeal.
 
Last edited:
Some people are having trouble with this NG update from the older code base and others upgrading from beta.
I wrote a quick check list if this happens to you to try before flashing back to what you had before.
Understand that most will not have to do this but if you are having trouble try the bellow procedure.
Code:
Steps when flashing results in problems:
1. remove any connected usb devices
2. reboot without the usb drives connected
3. flash new firmware
4. reset to factory defaults and power back up
5. wait 10 minutes for the reset to complete
6. configure or import at this point
7. reboot but pull the power cord and turn the power button on (if equiped) for 10 seconds while unplugged
8. while the router is powered off plug in the usb drives and turn on the router
9. Hopefully this works for you as it works for me
 
Okay, done. I did the following:
  1. Unplugged the USB flash drive from the RT-AC3200

  2. Re-Uploaded 384.4

  3. Initiated a Factory Reset from the GUI

  4. Waited for 10 minutes after reboot

  5. Turned SSH on and cycled the power (I have no idea why I have to power-cycle to make SSH accept a connection, but even a Reboot from the GUI doesn't get the job done)

  6. Plugged in a USB flash drive containing my NVRAM settings backup

  7. Restored Settings and rebooted
Sadly, I'm back to having all sorts of problems, as before: the Ecobee thermostat, Ubuntu laptop, some Chromecasts, and some LIFX bulbs now can't connect to Wi-Fi.

So, I'll be returning to 384.3 shortly, and will report back. Thanks again for your help, skeal.
You may have to skip this step:
Code:
7. Restored Settings and rebooted
and manually configure as something in the nvram could be screwed up.
 
Those are the interfaces from my two routers:

main router:
Code:
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
    link/ether d6:1c:b4:dd:8e:0a brd ff:ff:ff:ff:ff:ff
3: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
    link/ether aa:02:1c:cd:ab:f1 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:70:c2:7a:44:85 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.100/24 brd 192.168.1.255 scope global eth0
5: dpsta: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:70:c2:7a:44:85 brd ff:ff:ff:ff:ff:ff
7: eth2: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:22:15:a5:03:04 brd ff:ff:ff:ff:ff:ff
8: vlan1@eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 00:70:c2:7a:44:85 brd ff:ff:ff:ff:ff:ff
9: vlan2@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 00:70:c2:7a:44:85 brd ff:ff:ff:ff:ff:ff
10: br0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:70:c2:7a:44:85 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.1/24 brd 10.0.0.255 scope global br0
11: wds1.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:22:15:a5:03:04 brd ff:ff:ff:ff:ff:ff

media bridge:
Code:
1: lo: <LOOPBACK,MULTICAST,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: ifb0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
    link/ether 86:e4:a3:fb:87:c9 brd ff:ff:ff:ff:ff:ff
3: ifb1: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN qlen 32
    link/ether 6a:09:cd:93:14:f1 brd ff:ff:ff:ff:ff:ff
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:0e:ca:7a:58:83 brd ff:ff:ff:ff:ff:ff
5: dpsta: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: eth1: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:0e:ca:7a:58:83 brd ff:ff:ff:ff:ff:ff
7: eth2: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:22:15:a5:03:04 brd ff:ff:ff:ff:ff:ff
8: vlan1@eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 00:0e:ca:7a:58:83 brd ff:ff:ff:ff:ff:ff
9: vlan2@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 00:0e:ca:7a:58:83 brd ff:ff:ff:ff:ff:ff
10: br0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:0e:ca:7a:58:83 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.2/24 brd 10.0.0.255 scope global br0

As you can see I got 00:22:15:a5:03:04 that is repeated on eth2 interface on both routers and on wdsl.1 on the main router. There are other mac address which are repeated. Is it normal? Can I do something?
 
you can read everywhere here to setup manually after major firmware changes, as soon as you load previous config you will load same troubles which the newer firmware cant handle.
 
You may have to skip this step:
Code:
7. Restored Settings and rebooted
and manually configure as something in the nvram could be screwed up.

Since I'm using john9527's famous User NVRAM Save/Restore Utility, and this same set of settings works with 384.3, I like to think that's not the case, but I fully appreciate you could be right on that.

Sadly, I don't have the free time to configure all my port forwarding and DHCP reservations from scratch right now, so I'll have to live with 384.3 for the time being, which is reinstalled and working just great. Thank you, skeal!
 
380.69 worked well, but after flashing 384.4 I tried to flash back to 380.69 and it doesn't work anymore. I tried to set 380.69 restoring my settings previously saved, and also resetting everything and manually setting it again with very basic configuration. As soon as I set the second router as media bridge over 5G wifi I can't connect to 5G with any other device, while media bridge works well. If I turn off media bridge I can connect again.
If I connect media bridge to 2.4G wifi all works well but I need 5G to get full bandwidth internet to devices connected to the media bridge with cables.
 
I don't recommend using John's script to make a backup of a 384 firmware, until he had the chance to officially implement support for it. A backup taken of a router running 384.xx (or 382.xx) might possibly not be correct.

As usual, when facing stability issues, proceed with a real factory default reset, without restoring any kind of backup. It's the only way to be 100% certain of the resulting configuration.
 
As usual, when facing stability issues, proceed with a real factory default reset, without restoring any kind of backup. It's the only way to be 100% certain of the resulting configuration.

As soon as I have a chance to do that, I'll report back. Thanks, RMerlin!
 
and make a reset with reset-button on backside or pressing WPS while power on some seconds.
 
@RMerlin: I tried factory reset through web GUI, nvram erase command through SSH and 30 30 30 reset. What else?
Don't do 30 30 30 asuswrt-merlin doesn't support that function.
 
and make a reset with reset-button on backside or pressing WPS while power on some seconds.
You can reset in the webui.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top