Some issues

[Yota]

1) Use the "computer" icon in the upper right corner of the GUI to disconnect the Internet and the GUI will freeze.
I found this Web GUI issue before, but I didn't find a way for everyone to reproduce this issue. now, I found the way.
Steps to reproduce:
Log in to the Web GUI via Wi-Fi using any modern desktop browser, then click on the “computer” icon in the upper right corner and disconnect the internet.
Actual results:
The internet was disconnected, but GUI just showed "Applying Settings ..." and then it just stays on this page.
Expected results:
Reload page.

This issue does not happen when you login to the configuration page using LAN, only with Wi-Fi, this is why only me and @oso2276 reproduced the issue.


2) the Connections page does not display ICMP protocol.
I remember maybe is 380 firmware, it will display the ICMP protocol, I don't know when it will no longer be displayed again.
Steps to reproduce:
Continuously ping any remote server from your computer and go to the router's Connections page.
Actual results:
You will not see any connections using the ICMP protocol, such as ping or traceroute.
Expected results:
Display ICMP protocol connection.


3) Wrong font color for VPN loading page.
Steps to reproduce:
On the OpenVPN page, enable or disable VPN.
Actual results:
"Please wait" is white, that's correct, and "70%" should be yellow, but "Applying settings" should also be white, like other pages.

Expected results:
I found that maybe I have OCD xD

 

[heysoundude]

Yeah you do: you're focused on the problem and haven't given us any pertinent details, like what router and the firmware version. also, you've assumed @RMerlin will see/reply to this thread, not having included it in the appropriate one. So, your OCD will go unsatisfied until you do...sorry.

 

[martinr]

Please confirm your router model and firmware version (number rather than “the latest”).

How long has the problem existed? Is it something you’ve only just tried and therefore noticed, or did everything work as expected until some event, such as a firmware update or script installation?

Did you try using a different browser and also from a different device?

 

[Yota]

Yeah you do: you're focused on the problem and haven't given us any pertinent details, like what router and the firmware version. also, you've assumed @RMerlin will see/reply to this thread, not having included it in the appropriate one. So, your OCD will go unsatisfied until you do...sorry.

Please confirm your router model and firmware version (number rather than “the latest”).

How long has the problem existed? Is it something you’ve only just tried and therefore noticed, or did everything work as expected until some event, such as a firmware update or script installation?

Did you try using a different browser and also from a different device?

Thanks for your quick response.

I think these issues are included in all models, so I did not indicate which model. and, I have ruled out browsers, browser extensions, operating systems, etc. in previous tests.
For the first and third issues, I don't know when they happened, but for a while. the second issue "I remember maybe is 380 firmware" but I'm not sure.

I'm sorry, if there is any disrespect, please forgive me.

Thank you all.

 

[L&LD]

1) Simple fix: reload the webpage. GUI is not frozen.

 

[Yota]

1) Simple fix: reload the webpage. GUI is not frozen.

Thanks for your reply, yes I have used this way for a long time.

 

[RMerlin]

Specifying the router model along with the firmware version is critical, because not all models are based on the same source code. Some issues are only present on certain models. For instance, the recent DDNS page issues were only present on AX models.

The Connection page probably hasn't shown ICMP entries since the page was re-implemented as a table, because the current backend parser can only recognize tcp and udp entries in the netstat-nat output. It will require reworking the parser to deal with the different format used by icmp entries.

 

[martinr]

.......
I'm sorry, if there is any disrespect, please forgive me.

Thank you all.

Nothing to apologise for: I can’t imagine anyone being offended by anything you wrote. I certainly hope you didn’t think anyone was.

 

[heysoundude]

Nothing to apologise for: I can’t imagine anyone being offended by anything you wrote. I certainly hope you didn’t think anyone was.

I certainly wasn’t. I was somewhat concerned that I offended OP, being as direct as I was at the top of the thread.


Sent from my iPhone using Tapatalk

 

[GHammer]

3) Wrong font color for VPN loading page.
Steps to reproduce:
On the OpenVPN page, enable or disable VPN.
Actual results:
"Please wait" is white, that's correct, and "70%" should be yellow, but "Applying settings" should also be white, like other pages.
View attachment 21857
Expected results:
I found that maybe I have OCD xD

Nice troubleshooting, just as it should be with the exception of router and firmware.
Include those and it's a good issue report. I can follow the steps to reproduce and reproducing issues is the key to solving them.

 

[Yota]

Specifying the router model along with the firmware version is critical, because not all models are based on the same source code. Some issues are only present on certain models. For instance, the recent DDNS page issues were only present on AX models.

The Connection page probably hasn't shown ICMP entries since the page was re-implemented as a table, because the current backend parser can only recognize tcp and udp entries in the netstat-nat output. It will require reworking the parser to deal with the different format used by icmp entries.

Thank you so much for your reply and your great work.

I always think they use the same source code in GUI, please forgive my ignorance and thanks tell me that.
The three issues I reported all occurred with the RT-AC68U model. I haven't tested other models, but I provided some steps to reproduce the issues, which should make it easy for everyone to test.
Model: RT-AC68U running 384.15 (but the issues has been around for some time, so it is not from this version of the firmware.)
Browser: I tested almost all major browsers except Chrome, However, I'm using Firefox 74.0 in macOS 10.14 more.

Thanks again.

 

[Yota]

Nothing to apologise for: I can’t imagine anyone being offended by anything you wrote. I certainly hope you didn’t think anyone was.

I certainly wasn’t. I was somewhat concerned that I offended OP, being as direct as I was at the top of the thread.

Nice troubleshooting, just as it should be with the exception of router and firmware.
Include those and it's a good issue report. I can follow the steps to reproduce and reproducing issues is the key to solving them.

I've been hit hard recently at work, so I always respond carefully, maybe a little paranoid sometimes, please forgive me.

Thanks for your suggestions, they are very helpful, thank you.

 

[martinr]

I've been hit hard recently at work, so I always respond carefully, maybe a little paranoid sometimes, please forgive me.

Thanks for your suggestions, they are very helpful, thank you.

Nothing to forgive! Responding carefully is always a good idea anyway, and one I try to practice after similar experiences.

 

[RMerlin]

Thank you so much for your reply and your great work.

I always think they use the same source code in GUI, please forgive my ignorance and thanks tell me that.
The three issues I reported all occurred with the RT-AC68U model. I haven't tested other models, but I provided some steps to reproduce the issues, which should make it easy for everyone to test.
Model: RT-AC68U running 384.15 (but the issues has been around for some time, so it is not from this version of the firmware.)
Browser: I tested almost all major browsers except Chrome, However, I'm using Firefox 74.0 in macOS 10.14 more.

Thanks again.

1) is probably caused by part of the networking stack getting restarted on the router, so not much can be done about it.
2) Fixed
3) That's been there since day 1. I once tried to track it down and couldn't. I might have another shot at it, but it's not a priority.

 

[Yota]

1) is probably caused by part of the networking stack getting restarted on the router, so not much can be done about it.
2) Fixed
3) That's been there since day 1. I once tried to track it down and couldn't. I might have another shot at it, but it's not a priority.

Thank you so much for trying to reproduce these issues and fix it. do you think the first issue I should report to upstream? to the Asus?
for the third issue, I may be able to provide the page source code. If this is good for reproduction. and I don't think it really matters, because not so many people are OCD. lol

Thanks.

 

[Yota]

Nothing to forgive! Responding carefully is always a good idea anyway, and one I try to practice after similar experiences.

Thank you.

 

[Yota]

3) That's been there since day 1. I once tried to track it down and couldn't. I might have another shot at it, but it's not a priority.

I may be able to provide the page source code.

This is the webpage source code when it happens.

<td>
	<span id="proceeding_main_txt">Please wait,</span>
	<span id="proceeding_txt" style="color:#FFFFCC;">10% Applying Settings</span>
</td>

Google searched for this code and it looks from this file.

Thank you.

 

[RMerlin]

This is the webpage source code when it happens.

<td>
    <span id="proceeding_main_txt">Please wait,</span>
    <span id="proceeding_txt" style="color:#FFFFCC;">10% Applying Settings</span>
</td>

Google searched for this code and it looks from this file.

Thank you.

That's just the dict file, that does not show where the code is generating the page, or how the CSS cascade is being applied (which is the actual tricky part).

Thank you so much for trying to reproduce these issues and fix it. do you think the first issue I should report to upstream? to the Asus?

For something so minor it's most likely a waste of time - there are far more glaring issues for their engineers to resolve than this very minor niche case. As I said, it's probably just a timing issue caused by service restarts. Just refresh your page.

 

[Yota]

That's just the dict file, that does not show where the code is generating the page, or how the CSS cascade is being applied (which is the actual tricky part).

I will try to find the truly source code, but I don't know much about HTML and CSS, however if I find it, I will tell you the first time.

For something so minor it's most likely a waste of time - there are far more glaring issues for their engineers to resolve than this very minor niche case. As I said, it's probably just a timing issue caused by service restarts. Just refresh your page.

I will do that.


Thanks again for everything.

 

[Yota]

3) Wrong font color for VPN loading page.

That's just the dict file, that does not show where the code is generating the page, or how the CSS cascade is being applied (which is the actual tricky part).
For something so minor it's most likely a waste of time - there are far more glaring issues for their engineers to resolve than this very minor niche case. As I said, it's probably just a timing issue caused by service restarts. Just refresh your page.

@RMerlin I saw you fixed this issue, thank you!