380.57 Possible port forwarding issue

[Soul--Reaver]

Hi

I've been running Asuswrt-merlin 378.56_2 with a new configuration on a AC87U for a while until the SMB logging issue popped up and upgraded to 380.57_alpha4 and a couple days ago to 380.57

I haven't been monitoring my router properly or my running applications on my server since i got sick soon after the upgrade to 380.57_alpha4.

The thing is i seem to have an issue with port forwarding. They work somewhat but every now and then they don't seem to work properly.

uptimerobot (which is monitoring my http dev server) seems to spam me quite a bit (50 emails of up and down events a day) which is not normal unless something is wrong.

I'm posting here to see whether other users have this issue (or similar) as well

For the moment I've downgraded to 378.56_2 to see if the issue persists

Kind regards

Soul--Reaver

 

[Soul--Reaver]

Weird that nobody else seems to have issues.

Tried the 380.57 firmware again and got the same issues again immediately after the upgrade.

Anybody know how i could best handle this and provide proper information to find the cause of the issue?

 

[popxunga]

Hello... I don't have anything monitoring but my ac87u has 380.57 and port forwarding seems to be working fine since ever. Just a shot in the dark... if you don't have a fixed ip service, how often is your public ip changing? Have you checked if your ddns service is working fine?

 

[Soul--Reaver]

its not ddns. Its direct ip connections from outside to inside that seem to fail roughly 25% of the times so not all of them

 

[popxunga]

If for some reason your public ip changes very frequently, the connection will fail until the ddns service gets updated with the new ip each time it changes. So you may want to check how often your public ip is changed.

 

[ozzed]

Hi

I've been running Asuswrt-merlin 378.56_2 with a new configuration on a AC87U for a while until the SMB logging issue popped up and upgraded to 380.57_alpha4 and a couple days ago to 380.57

I haven't been monitoring my router properly or my running applications on my server since i got sick soon after the upgrade to 380.57_alpha4.

The thing is i seem to have an issue with port forwarding. They work somewhat but every now and then they don't seem to work properly.

uptimerobot (which is monitoring my http dev server) seems to spam me quite a bit (50 emails of up and down events a day) which is not normal unless something is wrong.

I'm posting here to see whether other users have this issue (or similar) as well

For the moment I've downgraded to 378.56_2 to see if the issue persists

Kind regards

Soul--Reaver

Did you do a full factory reset and manual reconfiguration afterwards? I learned myself this weekend that making such big jumps in the code will basically store the old NVRAM-values so you still have to do a full reset. In my case Jumbo-frames didn't work and NAT-loopback wasn't working because My bittorrent client on my NAS didn't pick up a torrent I was seeding on my lan.. But doing a full factory reset and reconfiguring by the script in the forums (not by backup from the GUI) fixed my issues.

 

[paztelu]

Hi Soul--Reaver, I got the same exact problem with the 380.57 firmware on Asus RT-N66U, to clarify after upgrading to this firmware I did a Clear NVRAM so any old values were deleted and to do a clean start, I then proceeded to manually configure setting from the GUI . The problem was the same, external connections did not work correctly and packets were dropped. I did some tests and found out that when I applied DMZ the applications worked correctly, so I did the simple, downgraded directly to 378.56_2 and everything worked correctly. I hope this bug is fixed because it is very annoying, or If anyone found a solution please explain so that I can use the latest firmware correctly.


Thank you

 

[Soul--Reaver]

It's 380.57 not 378.57 just to clarify

Finally somebody else with this issue. Thank you. At least i'm not the only one, though i admit this issue is really problematic to monitor
I'm planning on trying a factory reset tomorrow for my AC87U

Though i must say. I experience this issue mostly with port forwarding but it might be dropping packets/connections at random and therefore have nothing to do with port forwarding

 

[paztelu]

Thanks Soul--Reaver, I corrected the old post with the correct version. For now Ill stay on 378.56_2 where this problem is not present and Ill wait for another firmware to try on my router where this bug is corrected. Let´s wait if anyone else reports this problem so it can be corrected soon.

 

[Daniel Hansson]

I have a similiar (maye the same) issue as you guys: http://www.snbforums.com/threads/time-to-first-byte-increased-with-380_57.30406/

 

[Soul--Reaver]

Based on your story i expect the same issue. I mostly detected the issue also with a webserver i host behind the router

 

[RMerlin]

Try disabling NAT acceleration, in case CTF interferes (it relies on packet marking to allow forwarded port traffic to bypass it, but it could be broken - it's a Broadcom blackbox after all...)

 

[Soul--Reaver]

Tried that a couple weeks ago with the NAT Acceleration -> Disable option

Made no difference

 

[Daniel Hansson]

Try disabling NAT acceleration, in case CTF interferes (it relies on packet marking to allow forwarded port traffic to bypass it, but it could be broken - it's a Broadcom blackbox after all...)

Thanks! Will try this later, maybe tomorrow. Downside is that sites will be slower on my server. Will this be fixed in upcoming versions?

 

[Daniel Hansson]

Tried that a couple weeks ago with the NAT Acceleration -> Disable option

Made no difference

Ok, already tested. I won't then.

 

[Soul--Reaver]

It made no difference for me. If you would be willing please test it as well so that we are 100% sure thats not the problematic part

 

[Daniel Hansson]

It made no difference for me. If you would be willing please test it as well so that we are 100% sure thats not the problematic part

Ok then. This is the steps I will take.

1. Reset
2. Update FW
3. Reset
4. Add ports and stuff manually
5. Disable NAT Acceleration
6. Reboot
7. Test if problem persists.

I'll post the output here.

 

[CiscoX]

Hi,
Have you tried to change your NAT Loopback from Merlin to ASUS under Firewall - General

 

[Soul--Reaver]

Said webserver was externally tested. NAT loopback only affects accessing the webserver when both are internally... correct? or might it also affect external sources?

NAT loopback was set to Asus for me.

 

[CiscoX]

I do remember I had problem to access my server sometimes, then I fixed it by changing the NAT Loopback. You can try, change it and restart router.
Also use static IP on your server, and use Port Forwarding.