Lost Internet On And Off Last Few Days, Worst Today RT-AC68U V3

DanS

May 31, 2021 00:10

I have a ASUS RT-AC68U V3 running the latest firmware 3.0.0.4..386.43129 as of a few days ago. I use a Blue and it was very reliable over the last 6 months; it is on the most stable release 1.971. I have had to turn it off because it caused constant internet access problems. How can I get it working again?

Comments

18 comments

Firewalla

May 31, 2021 00:28

Edited
First, best to describe what kind of internet access problems are you facing? We always ask people to do this

1. ping 1.1.1.1

2. ping firewalla's IP address

3. ping your router

4. nslookup firewalla.com

And see which ones fails.

If you reboot the router, will the problem go away?
0

Comment actions Permalink
DanS

May 31, 2021 01:01
Intermitent internet access for Youtube TV, Youtube, Echo devices, and computers. I will do these tests tomorrow morning when I turn Blue back on. BTW I saw the RT-AC68R listed as a problem router and wonder how that model relates to the RT-AC68U V3.
0

Comment actions Permalink
Firewalla

May 31, 2021 06:32
Check out the notes here, and double-check if the NAT acceleration is off. Since you been operating the box for 6 month, it is likely something in the new firmware update may mess up a few things. Possible to roll back to the previous version?
0

Comment actions Permalink

DanS

May 31, 2021 11:26

Mac-OS-X-KUGS-C15:~ root# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=61 time=132.457 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=61 time=185.111 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=61 time=211.729 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=61 time=65.959 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=61 time=64.704 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=61 time=66.964 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=61 time=66.162 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=61 time=68.792 ms
^C--- 1.1.1.1 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 64.704/107.735/211.729/56.918 ms
Mac-OS-X-KUGS-C15:~ root# ping 192.168.1.193
PING 192.168.1.193 (192.168.1.193): 56 data bytes
64 bytes from 192.168.1.193: icmp_seq=0 ttl=64 time=2.350 ms
64 bytes from 192.168.1.193: icmp_seq=1 ttl=64 time=1.328 ms
64 bytes from 192.168.1.193: icmp_seq=2 ttl=64 time=1.523 ms
64 bytes from 192.168.1.193: icmp_seq=3 ttl=64 time=2.187 ms
64 bytes from 192.168.1.193: icmp_seq=4 ttl=64 time=1.917 ms
64 bytes from 192.168.1.193: icmp_seq=5 ttl=64 time=3.281 ms
64 bytes from 192.168.1.193: icmp_seq=6 ttl=64 time=3.612 ms
64 bytes from 192.168.1.193: icmp_seq=7 ttl=64 time=5.775 ms
^C--- 192.168.1.193 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.328/2.747/5.775/1.364 ms
Mac-OS-X-KUGS-C15:~ root# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=63 time=5.581 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=2.163 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=63 time=1.717 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=63 time=2.389 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=63 time=11.743 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=63 time=3.559 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=63 time=1.924 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=63 time=2.735 ms
^C--- 192.168.1.1 ping statistics ---
8 packets transmitted, 8 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.717/3.976/11.743/3.157 ms
Mac-OS-X-KUGS-C15:~ root# nslookup firewalla.com
Server: 198.18.8.9
Address: 198.18.8.9#53

Non-authoritative answer:
Name: firewalla.com
Address: 23.227.38.32

Mac-OS-X-KUGS-C15:~ root# nslookup firewalla.com
;; connection timed out; no servers could be reached

Mac-OS-X-KUGS-C15:~ root# ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=63 time=2.790 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=63 time=2.522 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=63 time=1.566 ms
^C--- 192.168.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.566/2.293/2.790/0.525 ms
Mac-OS-X-KUGS-C15:~ root# ping 192.168.1.193
PING 192.168.1.193 (192.168.1.193): 56 data bytes
64 bytes from 192.168.1.193: icmp_seq=0 ttl=64 time=2.971 ms
64 bytes from 192.168.1.193: icmp_seq=1 ttl=64 time=1.510 ms
64 bytes from 192.168.1.193: icmp_seq=2 ttl=64 time=2.228 ms
^C--- 192.168.1.193 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.510/2.236/2.971/0.596 ms
Mac-OS-X-KUGS-C15:~ root# ping 1.1.1.1
PING 1.1.1.1 (1.1.1.1): 56 data bytes
^C--- 1.1.1.1 ping statistics ---
9 packets transmitted, 0 packets received, 100% packet loss
Mac-OS-X-KUGS-C15:~ root#

DanS

May 31, 2021 12:23

Edited
NAT Acceleration is not a user selectable setting on 3.0.0.4..386.43129 nor on previous version and I am not using QoS. I reverted to Version 3.0.0.4.386.41634 however the problem remains. So could this recent problem relate to Firewalla Cloud interaction with Active Protect? The problem seems to more affect my Roku Ultra 2020 therfore I stopped mnonitoring on Roku and will see if problem spreads to other devices as day goes on.
0

Comment actions Permalink
DanS

May 31, 2021 15:21

Edited
Had to disable all Monitoring as Echo devices started to have internet access issues again.
0

Comment actions Permalink
Firewalla

May 31, 2021 15:47
From your ping stats, I assume the .1 is your router, it is up .. and .193 is firewalla, I assume, so it is up. The interesting part is 1.1.1.1 is not going through...

Possible to login to firewalla https://help.firewalla.com/hc/en-us/articles/115004397274-How-to-access-Firewalla-using-SSH-

and inside ping 1.1.1.1? just keep the ping there until you see problems. Want to see if your issue is somewhat related to ISP.

Also, feel free to open a case with us and refer to this thread email help@firewalla.com
0

Comment actions Permalink
DanS

May 31, 2021 16:24

Edited
Yes on router and blue ip addresses. Will try the ping 1.1.1.1 from blue when next home. My ticket is 31444.
0

Comment actions Permalink
DanS

May 31, 2021 19:48
I enabled Experimental Simple Mode. Seems to have resolved problems for now. What are the changes from
regular Simple Mode?
0

Comment actions Permalink
DanS

May 31, 2021 20:40
After a awhile Roku experienced buffering again so disabled Monitoring.
0

Comment actions Permalink
Firewalla

May 31, 2021 21:21
Is the problem just to roku, do you have problems with the PC/MAC? If everything still having issues, probably need to wait a bit for our support
0

Comment actions Permalink
DanS

May 31, 2021 22:28
No, other devices like iPhone Wifi YoutubeTV and Echo Music,
0

Comment actions Permalink
DanS

June 01, 2021 12:14
I enabled DHCP Mode as a possible remedy.
0

Comment actions Permalink
DanS

June 01, 2021 16:48
DHCP Mode after making some client ip address adjustments is reliable.
0

Comment actions Permalink
Firewalla

June 01, 2021 17:03
Nice. DHCP mode is a better mode for sure, it doesn't rely on our arp spoof trick.

Do you have a link to your router? we want to take note on this. Is it this one https://www.asus.com/Networking-IoT-Servers/WiFi-Routers/ASUS-WiFi-Routers/RTAC68U/
0

Comment actions Permalink
DanS

June 01, 2021 17:27
Have to turn off client VPN and then the link is

https://192.168.1.1:8443/Main_Login.asp
0

Comment actions Permalink
DanS

June 01, 2021 17:58
The RT-AC68U V3.
0

Comment actions Permalink
DanS

June 02, 2021 14:50
No problems so far. Upgraded firmware again on router last night. Problem looks solved. Why it happened is a mystery.
0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?