SomeWhereOverTheRainBow
Part of the Furniture
RT-AX88U is failing to flash Beta 2 for me. This is the continuous error message I get....
USA - I tried both the main download and mirror download on RMerlins set.This is weird - I flashed two AX88U (UK version) with RT-AX88U_386.1_beta2_cferom_ubi.w via WebUI normally. Have you checked hash code? Where did you download it from?
Region / model specific issue?
Checked H/W revisions on mine - A1.0 and A1.1, I think those are only availableUSA - I tried both the main download and mirror download on RMerlins set.
After attempting to flash it multiple times i got it to flash.Checked H/W revisions on mine - A1.0 and A1.1, I think those are only available
Nah, I know which file I downloaded. It is easy to read before you hit upload.Perhaps wrong model accidentally? It is first time AX86U download is around
question: why are you running both connmon and spdmerlin? I lean towards thinking that's unnecessary redundancy and processor/connection load
I used to run both too, mainly because I love graphs. I feel like the more data you can look at, the better. Of course that is ridiculous, but I still hear the call of the chart from time to time.
Not sure if this has already been mentioned or not but openvpn client traffic is now inverted (download traffic appears as upload and upload traffic appears as download). I know there has been a long standing issue where the bandwidth monitor tab had the traffic inverted in this way but the classification tab was always correct, now it is inverted as well (and so is FlexQoS). QoS still appears to function correctly for me despite this but it would be nice if anything could be done to place it under the correct area in classification tab.
Please confirm you have tested this with FlexQoS disabled or uninstalled, to ensure it is not interfering.About the only minor issue is that the Adaptive QOS/Bandwidth Monitor/Download Bandwidth (and possibly Upload Bandwidth) do not register properly. System Status/System/Internet Traffic does register correctly.
Yes, I have done a Hard Factory Reset coming from the alpha version.
Not a show stopper for me.
AC86U beta 2 FlexQOS Diversion
Check those clients aren't set for Static IP or Manual within the DHCP Pool.Flashed RT-AC86U Main and AIMesh both with Beta2 and getting following for quite a few mac addresses:
not mesh client, can't update it's ip
I am only using one (YazFI) 3rd party script.
Confirmed.Please confirm you have tested this with FlexQoS disabled or uninstalled, to ensure it is not interfering.
Mix - Some mac addresses belong to guest wifi IPs (randomly assigned by DHCP) and some are DCHP assignments using "Manually Assigned IP around the DHCP list".Check those clients aren't set for Static IP or Manual within the DHCP Pool.
I regret that I have but one thumbs up/like to offer this post.Believe it or not, my ISP provider is a small time operator that just had enough knowledge and resources to set up a 14 mile microwave link from the nearest point where fibre access was to be had to give our town of 300 wide area 5g unlimited internet (50mbs down/up). The owner has oftened asked me for the my 7 day graphs of both spdmerlin and cronmon to help him tune and update the system.
May 5 06:05:15 kernel: ubi1: attaching mtd10
May 5 06:05:15 kernel: ubi1: scanning is finished
May 5 06:05:15 kernel: ubi1: attached mtd10 (name "misc1", size 8 MiB)
May 5 06:05:15 kernel: ubi1: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
May 5 06:05:15 kernel: ubi1: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
May 5 06:05:15 kernel: ubi1: VID header offset: 2048 (aligned 2048), data offset: 4096
May 5 06:05:15 kernel: ubi1: good PEBs: 64, bad PEBs: 0, corrupted PEBs: 0
May 5 06:05:15 kernel: ubi1: user volume: 1, internal volumes: 1, max. volumes count: 128
May 5 06:05:15 kernel: ubi1: max/mean erase counter: 20/9, WL threshold: 4096, image sequence number: 1960956644
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 kernel: ubi1: available PEBs: 0, total reserved PEBs: 64, PEBs reserved for bad PEB handling: 4
May 5 06:05:15 kernel: ubi1: background thread "ubi_bgt1d" started, PID 1046
May 5 06:05:15 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" started, PID 1061
May 5 06:05:15 kernel: UBIFS (ubi1:0): UBIFS: mounted UBI device 1, volume 0, name "nvram"
May 5 06:05:15 kernel: UBIFS (ubi1:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
May 5 06:05:15 kernel: UBIFS (ubi1:0): FS size: 5840896 bytes (5 MiB, 46 LEBs), journal size 1015809 bytes (0 MiB, 6 LEBs)
May 5 06:05:15 kernel: UBIFS (ubi1:0): reserved for root: 275879 bytes (269 KiB)
May 5 06:05:15 kernel: UBIFS (ubi1:0): media format: w4/r0 (latest is w4/r0), UUID 700E756D-208E-4C91-B256-B51AA3EDE77F, small LPT model
May 5 06:05:15 kernel: UBIFS (ubi1:0): un-mount UBI device 1
May 5 06:05:15 kernel: UBIFS (ubi1:0): background thread "ubifs_bgt1_0" stops
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 kernel: ubi1: detaching mtd10
May 5 06:05:15 kernel: ubi1: mtd10 is detached
May 5 06:05:15 kernel: proc_dostring_crashlogsave: crash log filename is /jffs/crashlog.log
May 5 06:05:15 kernel: ++++ Powering up USB blocks
May 5 06:05:15 kernel: usb3 reseting..........
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 kernel: release usb3 reseting..........
May 5 06:05:15 kernel: hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 kernel: usb3 reseting..........
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
May 5 06:05:15 crashlog: <6>protocol 0800 is buggy, dev eth6
The Manually Assigned ones definitely do produce this result..Mix - Some mac addresses belong to guest wifi IPs (randomly assigned by DHCP) and some are DCHP assignments using "Manually Assigned IP around the DHCP list".
We use essential cookies to make this site work, and optional cookies to enhance your experience.