What's new

102.7 Alpha Builds available

If I login via HTTPS using my DDNS url: from a wired PC on the Main subnet. I see [info] [LOGIN][https][Web] successed an external IP address
This can happen if you login over the router’s IPv6 address. It maps the last 32 bits of the router’s client’s IPv6 address into an IPv4 address, which is silly to begin with. 10 pounds of crap in a 5 pound bag…
 
Last edited:
any benefit of withdrawing these jjust like the terms of trendmicro
Notice
Please be advised that disagreeing with ASUS PRIVACY NOTICE may result in the inability to update to the latest firmware version and unable to receive the most up-to-date protection on your ASUS networking products; However, to protect the security of your router and ensure the compliance with laws, for upgrades addressing important security issues or meeting legal/regulatory requirements , those upgrades will still be downloaded and installed automatically.
Declining certain information may limit the functionality of the following features that rely on that information.
  • Account Binding
  • Config transfer
  • DDNS
  • Alexa
  • IFTTT
  • Google Assistant
  • Remote Connection
  • Notification
 
any benefit of withdrawing these jjust like the terms of trendmicro
Notice
Please be advised that disagreeing with ASUS PRIVACY NOTICE may result in the inability to update to the latest firmware version and unable to receive the most up-to-date protection on your ASUS networking products; However, to protect the security of your router and ensure the compliance with laws, for upgrades addressing important security issues or meeting legal/regulatory requirements , those upgrades will still be downloaded and installed automatically.
Declining certain information may limit the functionality of the following features that rely on that information.
  • Account Binding
  • Config transfer
  • DDNS
  • Alexa
  • IFTTT
  • Google Assistant
  • Remote Connection
  • Notification
I withdrew from this and it killed my ddns. I learned from that however that I could enable ddns again without accepting any terms. I don't know if that would work for the other services.
 
Just to let you know that I have uploaded a new GT-BE19000AI build. This build is based on a newer GPL version (I was previously using a fairly early version, so it had a number of known issues). This new build also integrates a new version of the Ark engine which should be at least more stable.

AFC should in theory be functionnal - I cannot test it in Canada.

The current plan for 102.7 is to only have this one single GPL update (no time to get 15+ GPLs prepared before the Chinese New Year holiday, and there was very few changes to them anyway). The rest will mostly gain updated components, and the removal of AiCloud (for which yet another new vulnerability just got disclosed).
In my router, BE96u I came across an nvram varable labled "coordinate", with a LAT/Long value. I cut and pasted the variable to search for the location it points to in Google Maps. Based on it, my router is sitting in the middled of a lake, 1.5 miles (~2.41 km) away from me or where its accrually sitting 3ft (1m) behind me. I hope AFC is not depending on that nvram variable 🤷‍♂️ not that my router or I would/could use it...
 
Based on it, my router is sitting in the middled of a lake, 1.5 miles (~2.41 km) away from me or where its accrually sitting 3ft (1m) behind me.

The new router is trying to improve your user experience. In the middle of the lake fishing is seen as better place to be compared to sitting home and poking in router settings. Your old routers never told you that.
 
The current plan for 102.7 is to only have this one single GPL update (no time to get 15+ GPLs prepared before the Chinese New Year holiday, and there was very few changes to them anyway). The rest will mostly gain updated components, and the removal of AiCloud.
I was really hoping the three Beta Release 9006.102_37342 for the GT-AX6000, RT-AX88U Pro and RT-AX86U Pro (see Asus release thread) which seemed to be behaving well and have mesh improvements (ostensibly), would have come out of beta sufficiently for them to give you GPLs; but you’re right, probably won’t be until after CNY.
 
The domain may not have correct DNSSEC signatures.

If you trust Quad9 or Cloudflare to do the DNSSEC validation on your behalf, turn off DNSSEC on the router.

This wouldn't involve DNS Director at all. There were several changes in dnsmasq 2.92 related to DNSSEC, however. Maybe it's better at validating now.
 
Thanks, Dave & RMerlin. The excellent info resolves my issues.
 
Is this a bug the firmware on Asus BE98 Pro?
Anyone know what the limit is for the number of VLANs on the Asus BE98 Pro routers?

After hours of experimenting, I found that each radio can have a max of 5 VLAN/SSIDs. So in theory, I should be able to do 20 VLANs without issue. But in reality I'm discovering that after 15 VLANs, 16th VLAN and onwards doesn't broadcast the SSID. I've tried various band combinations, even tried creating VLANs on ethernet (not Wi-Fi).

I'm also running the 3006.102.7_alpha1 so not sure if this is a bug in the firmware or a router/firmware limit.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top