Tools_WOL

[scottegos2]

Observed on rt-ac66u with with 246.20 firmware: in Tools_WOL.asp, I have severl WOL targets from the dropdown which all, for some reason, have the same name associated with them! There are no problems on the actual machines or errors in the error log (i.e. no hostname collisions AFAICT). So, I have two problems: 1. that the hostname comes up wrong and 2 (much more important to me) I can't edit the target name field

 

[RMerlin]

Observed on rt-ac66u with with 246.20 firmware: in Tools_WOL.asp, I have severl WOL targets from the dropdown which all, for some reason, have the same name associated with them! There are no problems on the actual machines or errors in the error log (i.e. no hostname collisions AFAICT). So, I have two problems: 1. that the hostname comes up wrong and 2 (much more important to me) I can't edit the target name field

The edit problem is a compatibility issue with Firefox. Use a different browser for now, this will be fixed in the next version.

 

[scottegos2]

Well, I tried it with IE9 and now it's MUCH WORSE. I deleted an entry that had a duplicate/bogus target name (all different MACs), then added that MAC back in and edited the name and did apply. Now the whole WOL page is completely shot -- doesn't show ANY entries or even the header/sidebar. Rebooting the router didn't help. I also can't do the dropdown or anything else. I suppose I will have to get it back by restoring to defaults.

 

[scottegos2]

Just to confirm: The really squirrely behavior must have had something to do with deleting and re-adding. After I reset to defaults, I reloaded my settings -- fortunately saved before I started adding WOL targets. As you suggested, editing the target name worked ok with IE. So, now everything is fine (though the bug above seems pretty ugly).

 

[RMerlin]

Have you been using that list for many firmware versions? A few versions ago that list could be saved in a corrupted state (some HTML tags were saved along with the names). It's possible that you might have carried that corrupted list over many firmware updates, and only recently ran into issues as you tried to edit an already corrupted list.

In the future, you can easily delete that list through telnet using this command:

nvram unset wol_list
nvram commit