New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Router page loading indefinitely #1042

Closed
ameshkov opened this Issue Apr 15, 2016 · 25 comments

Comments

Projects
None yet
8 participants
@ameshkov
Member

ameshkov commented Apr 15, 2016

@ameshkov ameshkov added the bug label Apr 15, 2016

@ameshkov ameshkov added this to the 6.1 milestone Apr 15, 2016

@Aokromes

This comment has been minimized.

Show comment
Hide comment
@Aokromes

Aokromes Apr 15, 2016

I confirm this bug :(

Aokromes commented Apr 15, 2016

I confirm this bug :(

@vozersky

This comment has been minimized.

Show comment
Hide comment
@vozersky

vozersky Apr 15, 2016

Member

Two users confirm:

  1. ASUS RT-N12E (2.0.0.37 firmware)
  2. ASUS RT-N14U

At least in the first case switching to TDI has fixed the issue.

Member

vozersky commented Apr 15, 2016

Two users confirm:

  1. ASUS RT-N12E (2.0.0.37 firmware)
  2. ASUS RT-N14U

At least in the first case switching to TDI has fixed the issue.

@ameshkov ameshkov modified the milestones: 6.0 R2, 6.1 Apr 17, 2016

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov
Member

ameshkov commented Apr 17, 2016

@ameshkov ameshkov self-assigned this Apr 17, 2016

@Aokromes

This comment has been minimized.

Show comment
Hide comment
@Aokromes

Aokromes Apr 17, 2016

No luck for me.

Aokromes commented Apr 17, 2016

No luck for me.

@BooBerry

This comment has been minimized.

Show comment
Hide comment
@BooBerry

BooBerry Apr 18, 2016

Logs incoming!

Logs.zip

BooBerry commented Apr 18, 2016

Logs incoming!

Logs.zip

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Apr 18, 2016

Member

Oh, nice, now I see what's the problem. Routers servers are full of surprises as always. It was invalid HTTP in TP-Link case, now it is wrong TCP implementation.

Member

ameshkov commented Apr 18, 2016

Oh, nice, now I see what's the problem. Routers servers are full of surprises as always. It was invalid HTTP in TP-Link case, now it is wrong TCP implementation.

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@Aokromes

This comment has been minimized.

Show comment
Hide comment
@Aokromes

Aokromes commented Apr 18, 2016

Works :)

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Apr 18, 2016

Member

Ah, nice, thank you for checking it:)

Member

ameshkov commented Apr 18, 2016

Ah, nice, thank you for checking it:)

@Aokromes

This comment has been minimized.

Show comment
Hide comment
@Aokromes

Aokromes commented Apr 18, 2016

NP.

@ameshkov ameshkov closed this Apr 18, 2016

@Bohdan-SUP

This comment has been minimized.

Show comment
Hide comment
@Bohdan-SUP

Bohdan-SUP May 9, 2016

Member

Looks like we have the issue back with ASUS RT-AC68U and Zyxel Keenetic 4G III.
Disabling WFP helps.
Ticket DTQ-668-32516

Member

Bohdan-SUP commented May 9, 2016

Looks like we have the issue back with ASUS RT-AC68U and Zyxel Keenetic 4G III.
Disabling WFP helps.
Ticket DTQ-668-32516

@Bohdan-SUP Bohdan-SUP reopened this May 9, 2016

@e13bb4dac2

This comment has been minimized.

Show comment
Hide comment
@e13bb4dac2

e13bb4dac2 May 22, 2016

In case you want more models; Asus RT-AC3200 router was also affected. The issue was resolved with the first live update

e13bb4dac2 commented May 22, 2016

In case you want more models; Asus RT-AC3200 router was also affected. The issue was resolved with the first live update

@vgavrish

This comment has been minimized.

Show comment
Hide comment
@vgavrish

vgavrish Jul 14, 2016

Zyxel Keenetic 4g II
a problem in Yandex browser (16.7.0.3342), in Chrome (51.0.2704.106 m) it's ok
Disabling WFP helps
Adguard 6.0
id 1056877

vgavrish commented Jul 14, 2016

Zyxel Keenetic 4g II
a problem in Yandex browser (16.7.0.3342), in Chrome (51.0.2704.106 m) it's ok
Disabling WFP helps
Adguard 6.0
id 1056877

@e13bb4dac2

This comment has been minimized.

Show comment
Hide comment
@e13bb4dac2

e13bb4dac2 Jul 27, 2016

Hi,

I just updated to 6.1.249.1233 from the previous beta and it seems like the issue is back with my Asus RT-AC3200 router.

Just before the install, I was configuring my NAS settings in the router GUI with no issues. Immediately after the update, continuing the NAS setup, router browsing is well..like it's covered with hot glue. More or less exactly like when this happened some time back in april/may. (I haven't restarted computer or router yet, just tried another browser - no change.) I'll report back if rebooting router and PC does indeed helt. I just tried 'disabling protection' in adguard options but no change.

e13bb4dac2 commented Jul 27, 2016

Hi,

I just updated to 6.1.249.1233 from the previous beta and it seems like the issue is back with my Asus RT-AC3200 router.

Just before the install, I was configuring my NAS settings in the router GUI with no issues. Immediately after the update, continuing the NAS setup, router browsing is well..like it's covered with hot glue. More or less exactly like when this happened some time back in april/may. (I haven't restarted computer or router yet, just tried another browser - no change.) I'll report back if rebooting router and PC does indeed helt. I just tried 'disabling protection' in adguard options but no change.

@BooBerry

This comment has been minimized.

Show comment
Hide comment
@BooBerry

BooBerry Jul 27, 2016

Confirmed, it's back here too.

BooBerry commented Jul 27, 2016

Confirmed, it's back here too.

@e13bb4dac2

This comment has been minimized.

Show comment
Hide comment
@e13bb4dac2

e13bb4dac2 Jul 27, 2016

BB, thanks for confirmation. In case it speeds up things, I just sent a in app bug report pointing to this thread

e13bb4dac2 commented Jul 27, 2016

BB, thanks for confirmation. In case it speeds up things, I just sent a in app bug report pointing to this thread

@ameshkov ameshkov modified the milestones: 6.1, 6.0 R2 Jul 28, 2016

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Jul 28, 2016

Member

@BooBerry @e13bb4dac2
Could you please send "debug"-level logs?

Member

ameshkov commented Jul 28, 2016

@BooBerry @e13bb4dac2
Could you please send "debug"-level logs?

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Jul 28, 2016

Member

@BooBerry @e13bb4dac2
Please check this build:
https://cdn.adguard.com/public/Adguard/github/AdguardForWindows/issue1042/Setup3.exe

You will need to reinstall AG as its version is the same as in the latest beta

Member

ameshkov commented Jul 28, 2016

@BooBerry @e13bb4dac2
Please check this build:
https://cdn.adguard.com/public/Adguard/github/AdguardForWindows/issue1042/Setup3.exe

You will need to reinstall AG as its version is the same as in the latest beta

@BooBerry

This comment has been minimized.

Show comment
Hide comment
@BooBerry

BooBerry Jul 28, 2016

Yep, fixed now. :)

BooBerry commented Jul 28, 2016

Yep, fixed now. :)

@e13bb4dac2

This comment has been minimized.

Show comment
Hide comment
@e13bb4dac2

e13bb4dac2 Jul 28, 2016

@BooBerry @e13bb4dac2
Could you please send "debug"-level logs?

It's probably sorted now but if you still want my log I can do it when i get home later today. In any case, I'll try out the new version and report in a few hours edit works now, thanks

e13bb4dac2 commented Jul 28, 2016

@BooBerry @e13bb4dac2
Could you please send "debug"-level logs?

It's probably sorted now but if you still want my log I can do it when i get home later today. In any case, I'll try out the new version and report in a few hours edit works now, thanks

@BooBerry

This comment has been minimized.

Show comment
Hide comment
@BooBerry

BooBerry Jul 28, 2016

What was the underlying issue that brought this one back?

BooBerry commented Jul 28, 2016

What was the underlying issue that brought this one back?

@ameshkov ameshkov modified the milestones: 6.1 R2, 6.1, 6.0 R2 Jul 28, 2016

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Jul 28, 2016

Member

What was the underlying issue that brought this one back?

I just forgot about that issue with routers and returned the old part of the code:)

When we finish processing connection, we send a "closing" packet to the server and finish processing this connection. Server responds with its own "closing" packet and after that browser understands that connection is closed.

However, this router has weird TCP stack implementation and it simply ignored "closing" packet and was not sending anything in response.

Member

ameshkov commented Jul 28, 2016

What was the underlying issue that brought this one back?

I just forgot about that issue with routers and returned the old part of the code:)

When we finish processing connection, we send a "closing" packet to the server and finish processing this connection. Server responds with its own "closing" packet and after that browser understands that connection is closed.

However, this router has weird TCP stack implementation and it simply ignored "closing" packet and was not sending anything in response.

@ameshkov ameshkov closed this Jul 28, 2016

@vgavrish

This comment has been minimized.

Show comment
Hide comment
@vgavrish

vgavrish Aug 6, 2016

the same problem with Dlink switches:
des-3200-10
des-3200-18
des-3200-28
dgs-3000-10tc
dgs-3120-24tc(sc)
Disabling WFP helps
6.1.251.1269

id 1373720

vgavrish commented Aug 6, 2016

the same problem with Dlink switches:
des-3200-10
des-3200-18
des-3200-28
dgs-3000-10tc
dgs-3120-24tc(sc)
Disabling WFP helps
6.1.251.1269

id 1373720

@vgavrish vgavrish reopened this Aug 6, 2016

@ameshkov

This comment has been minimized.

Show comment
Hide comment
@ameshkov

ameshkov Aug 8, 2016

Member

@vgavrish I think we should open a separate issue for these D-Link issues:
#1219

Member

ameshkov commented Aug 8, 2016

@vgavrish I think we should open a separate issue for these D-Link issues:
#1219

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment