Recent content by Shasoosh

Thank you for your response; that's a great suggestion. Next time it happens, I'll try reconnecting it to the same port to rule out the possibility of a faulty WAN port.

I have a main ASUS RT-AC86U router that is wired to several TUF-AX3000 V2 units, which all function as access points (not using AiMesh). Today, I noticed that one of the access points stopped responding when I tried to access it via 192.168.1.7. Restarting the access point didn’t help, so I...

I've went with B and it worked. No idea how I missed that. Thank you very much!

I've also tried flashing one of the APs with gnuton fork of AsusWrt Merlin but I'm getting the same issue.

The DNS in the AP was empty. (hoping it will use the ISP DNS like the main router does.) After settings the DNS to 8.8.8.8 pinging google.com also works. (I didn't use nslookup google.com 192.168.1.1) Unforthently, like mentioned above, restarting the router reverts the fix. How can I make it...

Cool. This made some progress. Ping to 8.8.8.8 works after the commands above. Ping to google.com still fails with ping: bad address 'google.com' Before the commands above pinging 8.8.8.8 also failed: PING 8.8.8.8 (8.8.8.8): 56 data bytes --- 8.8.8.8 ping statistics --- 5 packets...

user@TUF-AX3000_V2-GAMING:/tmp/home/root# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 0.0.0.0 0.0.0.0 U 0 0 0 br0 127.0.0.0 0.0.0.0 255.0.0.0 U...

Thanks @rung I also tried searching the forum for a similar bug but couldn't find anything.

Thanks for the help. That didn't help. Tried to assign a couple of DNS to the 192.168.1.7 AP, still no go. I've also reseted the main router a couple of times when configured the network without touching the settings. The APs still can't reach the internet.

The APs doesn't have a WAN page. I've tried adding 8.8.8.8 and 1.1.1.1 to the LAN page under DNS but it didn't help. I've also noticed that the "Network Tools" in the GUI that will let you ping, trace route etc' will not work. For a ping to google.com I get If I try to traceroute google.com I...

No problem. Here's one from a few moments ago. * Note that the date is off and set to Sat, May 05 08:13:40 2018 because the router can't reach the NTP server. (I've tried a few, it can't reach anything) There's a 10000 characters limit here so here's a pastebin link: https://pastebin.com/48y868ex

They appear as regular clients. I don't see an option to block internet access for them. Also, when hovering over the 'internet' icon in the Internet column next to each AP, there's a tooltip saying 'Allow internet access.' I've also tried configuring 192.168.1.7 in the main router's DHCP...

Thanks. All APs are connected to the main router via the WAN port.

Hey, I have 3 access points (APs), all of the same model mentioned above. Everything is working fine - clients connected to the APs can access the web both wired and wirelessly. The only issue is that the APs themselves, as seen in the router GUI, cannot access the internet. For example...