I just moved from 3004.388.9_2 to 3006.102.4, I didn't assume that an older, initial release contained a warning that is still relevant for the current version, but whatever, it's my fault, anyway, thank you for your hard work!There was a warning in the initial 3006 release changelog, and the devs were warned weeks ahead of time about it. It's been almost a year now since that initial 3006 release, I'm not going to keep repeating the same warning over and over again in every release. It's their developer's responsibility to either update their addons, warn their users, or have someone in the community warn other users if an addon dev is MIA/retired. I'm not going to personally keep track of 20+ addons myself, sorry.
Updated my GT-AX6000, update went smoot.
I can't untick b/g protection in N only mode, it doesn't stay.
View attachment 65621
View attachment 65620
Only the first yes, but for each radio's.even though it warned of only putting across one.
This firmware (by design of Asus) does not allow advanced firewall rules to be setup to allow traffic between VLANS. Each VLAN is separated and only has access to internet. witching tha access to main network on basically makes it part of the same subnet (so no FW/traffic restrictions between the VLANs/SSID's) so only usefull for a different SSID for a particular purpose (i.e. WPA2 TKIP support). Either configure a separate router or dedicated firewall to handle inter VLAN traffic (and switch off DHCP for these vlans on all ASUS nodes). Or re-install Yazfi (if supported on this firmware) to set it up as you liked.Dirty upgrade from 3004.388.8_4 to 3006.102.4 on a RT-AX88U Pro everything working great (20 wired/wifi devices) apart from connecting my doorbell camera on the new IoT network, using Onvif, to my Synology NAS Surveillance Station on my main network. This worked previously when I had used Yazfi to configure an IoT Guest Network the camera was previous;y connected to.
Have granted the new IoT Network "Access Intranet to Main Network" but camera not discovered when Surveillance Station scans the network or gets picked up when I configure manually; whereas my phone, using the camera's app, connects fine from my main network and I can view live/footage on the SDCard.
Not sure what's up but given the above assuming I'm the problem - does anyone have any suggestions what I might try to get it working please?
@mmjlmjl - Why are we given the option to connect the iot network to the main network then, see below? Or am I missing your point?This firmware (by design of Asus) does not allow advanced firewall rules to be setup to allow traffic between VLANS.
YazFi is not supported on 3006.102.x firmware. Instead people have been using scripting to setup IPTables entries to try and emulate some of YazFi's features. For example see the following post (and discussion) on using theOr re-install Yazfi (if supported on this firmware)...
firewall-start
file to create IPTables entries.Were you using the 3006.102.x firmware? Or the earlier 3004.x firmware?Like I said this worked previously so not sure why this would now be subject to needing stricter 'advanced' firewall rules.
Just tried a quick test on a RT-AX86U Pro (3006.102.4) that has a Guest Network Pro IoT Profile created that has Use same subnet as main network disabled and Access Intranet (Main Network) enabled, and the IoT client could access/ping several main LAN clients (both a wired client and a WiFi client). And a main LAN client could ping that Guest Network Pro IoT client.@bennor - Dirty upgrade from 3004.388.8_4 to 3006.102.4. It's the "built in" IoT Network rather than Guest but will try configuring a new one as you suggest and report back....thanks!
I did not enable, nor do I use, VPN on my Guest Network IoT profiles. All I can say is that the Access Intranet is working in my setup. I have two Guest Network Pro IoT profiles, both configured with Use same subnet as main network set to disable. Each IoT profile is configured for a single WiFi band (one for 2.4 GHz the other for 5 Ghz). I do not have Smart Connect enabled on my main WiFi bands. The attached images show that a Guest Network Pro WiFi client (192.168.52.175) can ping a wired main LAN client (192.168.2.50) and vice versa. And the IoT indicates Main LAN is selected for Access Intranet.I need a Guest Network Pro VPN Network that can connect to the main network and it does not work.
I have gone through the process as described by @bennor with no results.
I don’t see that it ever showed anything besides “Disabled” when in Passthrough mode. I suppose there is nothing to show in that mode.The only bug I found is that I'm using IPv6 Passthrough since my ISP (Verizon 5G Home) requires it. Under the IPv6 System Log, it shows "IPv6 Connection Type -- Disabled".
Bandwidth Monitor is a feature of Trend Micro. Trend Micro on ASUS WiFi7 routers has not been working properly. Perhaps we should expect RMerlin to merge the new GPL source code in the next version?RT-BE88U is still bugged for Bandwidth Monitor (Apps Analysis On) & Traffic Analyzer - Statistic.
It only started to happening in the previous version as well as this version (2006.102.4).
Bandwidth Monitor (Apps Analysis On) - In the past, if i was downloading at 100mbps, it would show 100mbps in real time. Now it takes 3-5 seconds to display which explodes into very high numbers than goes back down to 0 in a second when constant data is being download or upload.
Traffic Analyzer - Statistic - The details are 10 hours behind hence i'm in a GMT+10 time zone. It should currently say 2pm on the right side of the graph but it shows 4am as the latest.
I've done many clean factory resets on both versions where it hasn't fixed these problems.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!