That is my understanding as well.
1 Like
Looking forward to trying it!
Thanks for your help 
I am going to flash some of these other devices I have as well, as they all still have stock firmware.
Please let us know how you fared?
Finally got round to switching back to the on-board DSL modem and, with the MTU set to 1492 on pppoe-wan, everything is working well.
I could now change the device in the interface wan, to be pppoe-wan, however it's working with the device beingg dsl0.101, so I don't see the point.
Happy to hear why I should though?
I also noticed a wan_6 interface has been created with protocol 'Virtual dynamic interface (DHCPv6 Client).
This might be because I already have a wan6 interface which is an alias of wan, but which is configure to not start on boot?
Does OpenWrt only create the virtual dynamic interface if the alias doesn't already exist?
I also managed to use UART and flash 4 other hh5a targets with 23.05
apk add = opkg install 
Honestly, I have no real good argument, assuming everything works. Personally I would try to configure this as closely as possible to how OpenWrt would do it by default, but that is just my personal preference...
I think wan_6 is indeed created if wan6 exists but is not active, but I have only vague recollections about this...
1 Like
I just realised the image I flashed to the 4 routers I had laying around, was 24.
I was wondering why it was APK not OPKG.
Thats snapshot, 24.10 still has opkg, but owut in place of ASU
1 Like
That is good advice 
I just noticed that, in the Network>>Interfaces page, it does show wan as using pppoe-wan, however, in Network>>Interfaces>>wan modal, it shows device as dsl0.101, so I suppose now that the pppoe-wan tunnel is up, that is automatically assigned to wan.
A little confusing as it appears to be the only interface that does that; all other interfaces show the device on the Network>>Interfaces page, which matches what is shown in the Device dropdown in the interface configuration modal.
So, the interface wan is showing as using pppoe-wan and it's device is dsl0.101. All is right now I think
Thanks for your help and advice with all of this 
I just tried an in-place upgrade of my own router because of
https://www.theregister.com/2024/12/09/openwrt_firmware_vulnerabilities/
and was expecting to find APK, but I'm on 23.05, so obviously not.
Maybe it would be better to downgrade the 4 routers I flashed to 23 for now?
I'm on one of those ISP that allow mini jumbo frames 1508 MTU via DSL.
All ethernet / dsl and related vlans are set to 1508 MTU . Both modem and router side (I use two devices)
PPPoE connection has 1500 MTU and behave same as regular DHCP client.
Below code will show 100% loss if configuration is wrong or ISP do not allows mini jumbo frames.
ping -n 1 -f -l 1472 8.8.8.8
Pinging 8.8.8.8 with 1472 bytes of data:
Reply from 8.8.8.8: bytes=1472 time=27ms TTL=118Ping statistics for 8.8.8.8:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 27ms, Average = 27ms
Note: That seems to be the windows ping invocation, the iputils ping equivalent would be:
ping -c 1 -M do -s 1465 8.8.8.8
busybox will not allow to control fragmentation behaviour (-f for windows, -M do for iputils):
ping -c 1 -s 1465 8.8.8.8
Probably the nicest test on a OpenWrt router involves tracepath:
If not installed, install tracepath:
opkg update , opkg install iputils-tracepath
# these will take a bit, and then show the estimated path MTU (should be 1500 with baby jumbo frames)
tracepath -b -4 one.one.one.one
tracepath -b -6 one.one.one.one