Did the BE98 Pro ever get it's AFC firmware update?

[GunSmoke]

I should offer my thoughts on this router since I know everyone here is likely to be interested in an AFC model... it's worked flawlessly so far, roughly 30 nodes. I like it. It doesn't give me any additional 2.4GHz range that I was hoping for (old model was wifi5), I'm going to have to use my old router in AI Mesh to get a consistent signal to my doorbell and front of the house. I plan on just extending my 2.4GHz network with it, and hopefully being able to rely on wifi7 MLO for my phone to reach around the property, retaining a single SSID for non IoT devices. I'm likely to keep it, my Asus DDNS alias has been transferred which usually seals the deal for me.

 

[jzchen]

I remember I got a AXE11000 then AXE16000, and finally got our first 6E enabled device, a MacBook. Could not get them to connect on 6 GHz. The eventual solution was I purchased a TP-Link 6E range extender, and copied the settings over! I haven't found anything that would indicate what needs to be changed, yet...:

Getting Started with AFC | TP-Link

This article provides comprehensive information about AFC (Automated Frequency Coordination) for Wi-Fi products. It covers key aspects, including its working principle, regulatory compliance, compatibility with Omada AP products, configuration steps, etc., and aims to assist users in...

www.tp-link.com

Currently only the Omada EAP772-Outdoor seems to have it enabled...

 

[jzchen]

One thing I forgot to ask, the router is getting a proper WAN address from the AT&T Gateway?

 

[GunSmoke]

One thing I forgot to ask, the router is getting a proper WAN address from the AT&T Gateway?

It's working as it was with the last router in IP pass-through mode. I'm not sure what a 'proper' WAN address is but given AT&T generally forces people to use pass-through which is double NAT, I believe the answer is no. If you mean Cascaded Router mode, that's disabled. I just cleared the device list and updated the DHCPS fixed MAC address to the new router. Unlike my RT-BE96U, this simple straightforward process that should just-work, did work. Very happy with how smooth and stable everything has been with this one. I get the feeling older router models served as the (expensive) betas.

I remember I got a AXE11000 then AXE16000, and finally got our first 6E enabled device, a MacBook. Could not get them to connect on 6 GHz. The eventual solution was I purchased a TP-Link 6E range extender, and copied the settings over! I haven't found anything that would indicate what needs to be changed, yet...:

Getting Started with AFC | TP-Link

This article provides comprehensive information about AFC (Automated Frequency Coordination) for Wi-Fi products. It covers key aspects, including its working principle, regulatory compliance, compatibility with Omada AP products, configuration steps, etc., and aims to assist users in...

www.tp-link.com

Currently only the Omada EAP772-Outdoor seems to have it enabled...

I enabled MLO in the GS-BE18000 in both locations, the "master switch" in Wireless, and then also fronthaul for my main (Wifi7) network. Along with Smart Connect. I am seeing devices connecting to 6GHz, but often choosing 5GHz. I'm just trusting the default connection strength settings are ideal. I never wanted to fuss with 6GHz until I could get it with AFC and Wifi 7 MLO, where I felt it started to make more sense. Obviously the range of 6GHz is nearly useless otherwise outside of a one bedroom apartment. But it is working on this model without any issue.

 

[jzchen]

Yes I'm afraid the IP Passthrough does not always work as it should. It should not create a double NAT, but sometimes, or a lot of times, it would. I do not know if this would affect AFC but I suspect it could.

Under Advanced Settings -> Network Map

towards the top center there is a "globe" you can click on it. It should show the WAN settings on the right side. Please verify that WAN IP is not 192.168.1.___ ? You don't have to share it (for your safety) but for example mine starts with 107.1zz.xxx.yyy

 

[GunSmoke]

Yes I'm afraid the IP Passthrough does not always work as it should. It should not create a double NAT, but sometimes, or a lot of times, it would. I do not know if this would affect AFC but I suspect it could.

Under Advanced Settings -> Network Map

towards the top center there is a "globe" you can click on it. It should show the WAN settings on the right side. Please verify that WAN IP is not 192.168.1.___ ? You don't have to share it (for your safety) but for example mine starts with 107.1zz.xxx.yyy

I've checked for double NAT before with a trace route, and it is. I have read that dhcps-dynamic can remove the double NAT on the BGW320. Which makes no sense, but I'm going to try it after work.
Found the thread referencing this- reddit.com/r/firewalla/comments/15koib1/comment/k8mtjpi/

Great point that it could affect AFC. Will definitely follow up on this one.

edit to add-
Hm, checking just now, my Asus WAN IP: 99.9*.***.***. But a tracert still hits the gateway for sure because it appears in its subnet 192.168.1.254.

From the gateway:
IP Passthrough Status On (public IP address)
IP Passthrough Address 99.9*.***.***

I think it is indeed not double NAT. My tracert is just hopping that node which is always going to be there. Darn, wish that were the issue with AFC. I still think they haven't enabled it yet but there are enough hoops to jump through for the feature, that it very well could be something like the Asus Router app location settings etc.

 

[jzchen]

Should be able to check on the ASUS router app -> Settings -> Router Information -> About My Router - WAN IP

 

[GunSmoke]

Should be able to check on the ASUS router app -> Settings -> Router Information -> About My Router - WAN IP

Yes it's the same there. I do have IPV6 enabled and the IPv6 WAN IP is similar to my IPv6 LAN IP, but I'm not sure if that's a concern. Pretty sure I'm good on WAN IP being passed correctly.

 

[jzchen]

The last thing I can see/guess might be the culprit, beyond just not being/living in an AFC enabled locale, is based on this statement from ASUS:

***AFC service included for the first 4 years; additional charges apply thereafter.

Not sure but guessing this may require you to register the router with ASUS? (Is that even separate from DDNS?...)

 

[cc666]

Eric,

Can you confirm if the GT-BE98 PRO is getting the AFC firmware upgrade?

CC

 

[RMerlin]

Eric,

Can you confirm if the GT-BE98 PRO is getting the AFC firmware upgrade?

CC

I have no additional info to share at this time.

 

[GunSmoke]

The last thing I can see/guess might be the culprit, beyond just not being/living in an AFC enabled locale, is based on this statement from ASUS:

***AFC service included for the first 4 years; additional charges apply thereafter.

Not sure but guessing this may require you to register the router with ASUS? (Is that even separate from DDNS?...)

I registered the router to my Asus account. No change yet. I have a feeling they haven't enabled AFC.

I said this before, but this wifi7 router did not improve much for me from my wifi5 model. I know people will balk at that, but I play Valorant and still have the same exact 3ms ping to the Chicago server. My 2.4GHz range has improved, but I think I will still need AI Mesh anyway as I've still noticed it not connected at a point. So I still need a solution for days with poor reception. Seems to be worse on rainy and overcast days.

Without wifi7 MLO and 6Ghz AFC, I see no reason to upgrade beyond a working wifi5 setup. I have 14 days from date of purchase to return it and will do so if AFC doesn't appear from a firmware update before then.