Found a couple issues that I don't know if they are contributed to this fork or basic ASUS firmware.
- BE96U doesn't appear to have a PHY 30 device. Currently Im seeing scans periodically which produce an error.
- kernel: enet_ioctl_compat_ethctl:L1984 No PHY type PHY_TYPE_UNKNOWN at address 30 has been found.
- iPhone 13 does not like and even rejects at times, band steering.
- bsd: bsd: wl0.1 Sending act Frame to REDACTED with transition target wl2.1 ssid REDACTED
bsd: bsd: BSS Transit Response: ifname=wl0.1, event=156, token=1, status=1, mac=00:00:00:00:00:00
bsd: bsd: BSS Transit Response: STA reject
Neither one of these are huge issues. I used a command to eliminate the iPhone 13 from even getting band steering requests at all by putting it on a deny / exempt list. Possible idea for a GUI feature for older devices putting them on a band steering exempt list when there are like 10 more more rejects for the device?
For the PHY 30 issue it comes and goes and can be suppressed with some simple SSH commands. Ultimately, the PHY 30 should be tagged to the debug log not the warnings logs.
Other than that this beta is actually going well. No major problems, no connections issues, and no crashes. I'm curiously looking into the ddosmem errors on start up and seeing what exactly they mean and if they can or need to be suppressed or moved to "debug" logging tags. Over all I'm more of a power user than a true developer but I have a good amount of experience working with OpenWRT and designing custom micro routers out of SBCs. I really am a stickler for clean logging as logging is, IMO, the best way to troubleshoot or monitor device environments.
Hey, side bar question the newish feature of MAC randomization, is there anyway in the negotiating process for the network to force that feature to OFF? Apple has OFF, Fixed, RANDOM and Android has something similar. I have had to get clever with my home internet control for my kids so that when a previously unknown MAC address is on the router it's automatically puts the device into the most restrictive access group and I have to manual pull it out after checking the device has this feature off. Chrome, while an internet browser, has the external Safe search API feature than can be enforced from the DNS filter, such as Ad Guard Home, or PiHole.
Correcting one statement in here. Seems that
ALL Apple iOS devices seem to reject or not respond to the bsd.