the newest jhm firmware seems good from initial impressions, no issues flashing through GUI, and it also defaults to 1508 so you dont even need to run the commands or edit anything on the modem. I have confirmed from tests (after adjusting aaisp control panel settings and pfsense) that I do now have a live 1500 byte mtu on pppoe. Thanks to everyone involved in the work on this.
--edit--
Some notes on the new firmware. These issues are not related to the patch I think.
On this firmware zyxel overhauled the UI, its not good. But the more concerning bits is what else I noticed.
The modem was powered down to send a dying gasp to dslam, dsl cable unplugged, and then I powered back up and flashed, I then waited 3 15 min cycles, and powered it down, then plugged dsl cable back in and powered it up.
On dslstats it logged 3200 ES which is very close to the dsl downtime. I dont see these ES anywhere in the telnet data so it is odd, but I have never seen that behaviour before when doing this process on older firmware versions. I do wonder if the modem now saves its stats on shut down to its storage so it can remember it, but as I Said I dont see it anywhere in the telnet data.
Also just to check if I am not going senile I looked at dslstats to see the modem uptime, but thats now "not available" so some things have moved around as well that affects the monitoring.
We will find out probably within a day if this becomes a DLM issue as 3200 exceeds the daily threshold, my feeling is only the stats "since link time" are passed on.
Yeah I see this which is modem uptime, and they also not there and confirm I did power down when I said, so no idea where dslstats got this 3200ES from.
"Total time = 13 hours 45 min 28 sec
FEC: 0 131
CRC: 131 13
ES: 97 13
SES: 0 0
UAS: 24 24
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0