Issue with XT9 after upgrading to 3.0.0.4.388_24709-g15d5e47

[03397]

I have a mesh XT9 with one router with 3 other nodes for a total of 4. One of them is connected with an ethernet cable and the other 3 over WIFI.
After upgrading to the firmware above I have disconnections all over the place between the nodes, I cannot make bindings to the nodes and when I setup a device even when next to a specific node the device fails connect.

Even binding of a node to another node refuses to connect.
Also an error keeps appearing in the logs but I am not sure if this is related.

Register interface [wds2.0.1] MAC: c8:7f:54:e5:23:08

br0: port 12(wds2.0.1) entered blocking state
br0: port 12(wds2.0.1) entered disabled state
device wds2.0.1 entered promiscuous mode
br0: port 12(wds2.0.1) entered blocking state
br0: port 12(wds2.0.1) entered forwarding state
Flushing net_device wds0.0.1.
br0: port 10(wds0.0.1) entered disabled state
device wds0.0.1 left promiscuous mode
br0: port 10(wds0.0.1) entered disabled state
br0: port 10(wds0.0.1) entered blocking state
br0: port 10(wds0.0.1) entered disabled state
device wds0.0.1 entered promiscuous mode
br0: port 10(wds0.0.1) entered blocking state
br0: port 10(wds0.0.1) entered forwarding state
Can't add zero mac!

Can't add zero mac!

Can't add zero mac!

Can't add zero mac!

 

[OzarkEdge]

I have a mesh XT9 with one router with 3 other nodes for a total of 4. One of them is connected with an ethernet cable and the other 3 over WIFI.
After upgrading to the firmware above I have disconnections all over the place between the nodes, I cannot make bindings to the nodes and when I setup a device even when next to a specific node the device fails connect.

Even binding of a node to another node refuses to connect.
Also an error keeps appearing in the logs but I am not sure if this is related.

Register interface [wds2.0.1] MAC: c8:7f:54:e5:23:08

br0: port 12(wds2.0.1) entered blocking state
br0: port 12(wds2.0.1) entered disabled state
device wds2.0.1 entered promiscuous mode
br0: port 12(wds2.0.1) entered blocking state
br0: port 12(wds2.0.1) entered forwarding state
Flushing net_device wds0.0.1.
br0: port 10(wds0.0.1) entered disabled state
device wds0.0.1 left promiscuous mode
br0: port 10(wds0.0.1) entered disabled state
br0: port 10(wds0.0.1) entered blocking state
br0: port 10(wds0.0.1) entered disabled state
device wds0.0.1 entered promiscuous mode
br0: port 10(wds0.0.1) entered blocking state
br0: port 10(wds0.0.1) entered forwarding state
Can't add zero mac!

Can't add zero mac!

Can't add zero mac!

Can't add zero mac!

You haven't said what you have done to troubleshoot. Me, I'd recommission the network and then take it from there... remove the nodes to auto reset, Hard Reset the router firmware, and then reconfigure the router from scratch. Don't add any more nodes than you need to extend coverage to where you need it.

FW Reset FAQ

Reset button/webUI Restore/node removal clears settings in NVRAM; reboot restores fw defaults from CFE

Hard Reset via WPS button/webUI Restore+Initialize also clears data logged in /jffs partition

OE

 

[03397]

I have removed all the nodes one by one and added them back. I do no want to recommission the network since I have a lot of customizations and I will loose everything.

 

[AvengerBB]

I have the same issue, my mesh is nearly unusable now

 

[OzarkEdge]

I have the same issue, my mesh is nearly unusable now

Maybe you'll take the same advice to troubleshoot the issue? Doing nothing won't fix it... twiddling a setting is not going to fix it, imo... posting about it ain't gonna fix it... what's left, reverting to previous firmware? If you do that, you should be prepared to take the same advice anyway.

OE

 

[AvengerBB]

Not sure why the attitude. I posted to let that person know they are not alone, and I'm sure there are more since the firmware just came out. It's poor that a firmware update would require a hard reset, especially with no advance notice or guidance in the release notes. Now I have to plan out a couple hours worth of my time to work on it in the hopes it will become usable again.

 

[OzarkEdge]

Not sure why the attitude. I posted to let that person know they are not alone, and I'm sure there are more since the firmware just came out. It's poor that a firmware update would require a hard reset, especially with no advance notice or guidance in the release notes. Now I have to plan out a couple hours worth of my time to work on it in the hopes it will become usable again.

I agree it's not a welcome task, but it is what it is. Experience has proven many times over that it is sometimes necessary to recommission ASUSWRT when a firmware upgrade produces weird behavoir with no other option to troubleshoot. The premise is to assume the release is generally usable and then go about proving it... or not. Any other troubleshooting can be a waste of time. Take your pick.

OE

 

[03397]

@AvengerBB
What I have done to help you that fixed my issue is the following. Downgraded all the nodes to previous version. Export the configuration. Then, reset to factory settings and then import the configuration. I have tried to reset but keeping the new version but the problem resurfaced.

If you revert back without resetting the problem will be there with the older firmware.

PS Bad attitude also won't fix anything.

 

[OzarkEdge]

I have tried to reset but keeping the new version but the problem resurfaced.

Can you clarify... did you save the new version configuration to .cfg file, reset the new version, and then restore that .cfg file? Or, did you reset the new version and configure it from scratch?

OE

 

[03397]

I have not configured anything from scratch. Reset new version + imported the configuration problem appeared. Downgraded to previous version+imported the configuration+problem solved.

 

[OzarkEdge]

I have not configured anything from scratch. Reset new version + imported the configuration problem appeared. Downgraded to previous version+imported the configuration+problem solved.

That makes sense. The only way to properly evaluate the new version is to bite the bullet and install it from scratch... not my rules. What you did would simply restore the suspected problem. This is explained in the FAQ linked in post #2 above.

Reverting the firmware to the previous version didn't solve anything... you are back where you started... maybe. The way to prepare for possible reversion is to save the configuration to .cfg file before upgrading to new firmware.

OE