[jetspeed]

TODO wrote:

What I meant by the DHCP bug is that the whole modem becomes inaccessible, can’t navigate to it with the browser and every device connected to it basically loses internet connection.

Technically, that is not a “DHCP” bug. That’s due to the unit locking up, either due to the memory leak, or a DNS bug.

If you don’t require any of the features of the new builds, go back to FW503. I was able to get 149 days of uptime, until there was a power outage in my area.

You need to login in order to vote

[jetspeed]

After a nervous few days of stormy weather, the day has come – 130+ days and counting.

Nice try @pavlf, your rain dance brought the rains, but luckily the DSL connection has been rock solid!

No doubt you’ll be back to wrestle the crown off me, but for now sound the trumpets and bring on the fanfare. Let the coronation begin! 😉

Attachments:

1. 

   Screenshot_2020-05-05.png
   

You need to login in order to vote

[jetspeed]

Argh, you still hold the crown – my modem bows down to yours 😂

Just three more days before I match it.

It’s very interesting that your memory usage doesn’t ramp up much. So theoretically it would last forever, unlike mine. Maybe the ADSL code doesn’t have memory leaks like VDSL…

Liked by:

You need to login in order to vote

[jetspeed]

@pavlf buddy, where art thou? Hope you are doing well.

Just reporting in regarding our friendly comp.

After several power outages, I’ve finally managed to get my 88U back to 123 days uptime. It’s at 306MB RAM used, so I’ll probably get 2 months more till it becomes unstable due to memory exhaustion.

How’s yours going?

Liked by:

You need to login in order to vote

[jetspeed]

Mine’s been rock solid since I’ve offloaded DNS to a PiHole. There’s definitely a DNS bug in there which may be the cause of the lockups.

You need to login in order to vote

[jetspeed]

Mrk26 wrote:

Got another more general question, does anyone experience asus dsl-ac88u freezing? I mean it shows wifi booth 2.4 and 5g but intermet not working, no access to router, all lights flashing as usually, also wired connection not working. Once disconnected from Wi-Fi can’t reconnect.

I used to have that problem. I think it’s related to the memory leak and/or DNS bug.

Since I’ve rolled back to FW503, no problems and stable.

You need to login in order to vote

[jetspeed]

Hey pavlf, had a power outage today after 105 days! Your record still stands. 😭

You need to login in order to vote

[jetspeed]

Gianluca wrote:

i’m still having an issue with WiFi 2.4Ghz

all my devices connected are losing the signal

Try increasing the Group Key Rotation Interval. I think by default it’s set as hourly, but I find that if you increase this to say 12 or 24 hours it helps with the frequency of disconnection.

You need to login in order to vote

[jetspeed]

Hey @pavlf, buddy ol pal. Just letting you know, I’ve reached the 90 day uptime mark and still going strong. Memory usage is at 261MB (57%) and ticking up slowly.

You need to login in order to vote

[jetspeed]

pavlf wrote:

OK, you’re on! I’m at 10 days 22 hours at the moment. I’m sure to make it to February without any new firmware appearing so I might be get past 120 days! The trick, as far as I can tell, is to turn everything off. No AI. No VPN & hardly any wifi devices. I do use it to stream music and to run torrents, but other than that it doesn’t do anything complicated.

I agree, except I have a tonne of WiFi devices, which is why FW503 is the only stable release for me. Leaks only 1MB per day as opposed to the 6MB of later releases.

I have also offloaded DNS to a Pi Hole, so this can only add to the stability of the whole system.

I’m on 59 days and may surpass your record around Christmas time. The only dilemma now is whether to go for the record or apply new firmware (if it ever gets released).

You need to login in order to vote

[jetspeed]

pavlf wrote:

Yes, that was me. I went to something like 120 or so in the end.

It seems like we’re the only ones left using this. Let’s have a friendly competition. I’ll let you know when I break your record ;)

You need to login in order to vote

[jetspeed]

UK Sentinel wrote:

56 days, that is a first for the DSL-AC3100 / 88U

No, it’s my own record, but I think another of your regular users did something like 90??

You need to login in order to vote

[jetspeed]

UK Sentinel wrote:

That is disappointing, try a different browser. and try newer firmware – Version 1.10.06_Build591 I managed to get it to work on RT-AC86U and an RT-AX88U simulator online not sure if 0.0.0.0 would work for Source IP address ? http://demoui.asus.com/ If these options does not work, then alas no other option available to block port 56 from UI, hopefully ASUS will fix also in next firmware (big list they have)

No go captain, I’m on record 56 days online streak with FW503! All the later ones, I couldn’t get a few weeks before it would lock up or have DNS failures.

Tried Chrome and Firefox, same deal.

I put my own PC’s as the source and tried a nslookup but it seemed to resolve fine and didn’t appear to block anything?

Anyway, I think I give up and wait for the next FW.

Thank you for the assist.

You need to login in order to vote

[jetspeed]

UK Sentinel wrote:

@jetspeed – Ok, I believe the following will block all port 53 requests from LAN to WAN, but never tested this on the DSL-AC88U. Go to Firewall > Network Services Filter to block port 53 TCP and UDP. as Network Services Filter only impacts LAN to WAN traffic and this should create entries in the iptables automatically. For ASUS, I believe all ports from WAN to LAN are closed by default, so ports are only opened by LAN traffic heading to default gateway , (UPnP – Port Forwarding) etc. Let us know how this goes ?

Thank you! This looks like what I’m after, but somehow can’t add port 53 without first adding a source IP? When adding port 53, it just disappears – no error message, no nothing.

I’m using FW503 and screen looks slightly different?

Attachments:

1. 

   Screenshot_2019-10-18.png
   

You need to login in order to vote

[jetspeed]

UK Sentinel wrote:

Does this work. or are you looking to create a singular static route ? Not sure if the DSL-AC88U has this option, but under LAN > DHCP Server is there an option to set DNS and WINS Server setting. this should then configure DNS queries obtained via DHCP to the DNS IP address of your Pi Hole IP Address. Then block port 53 ?

I’ve already have set the DNS server of the router to my Pi Hole, but how do I block port 53?

You need to login in order to vote

[Author]

Posts