Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. D

    ROG Rapture GT-AC5300 (Owners)

    Administration / Feedback in the router interface. Didn’t run any diags but allowed the system log and setting file and filled out as much info as I could in the comments. Both times now received a reply within a day, I have been quite impressed by the response so far.
  2. D

    ROG Rapture GT-AC5300 (Owners)

    I received beta firmware 20311 but it didn’t resolve the 0800 errors. My link aggregation is disabled and they even come up after a factory reset. Received another response from asus today they are working on it and will have a new beta soon.
  3. D

    ROG Rapture GT-AC5300 (Owners)

    Submitted a case for my protocol is buggy spam in the syslog from the recent official firmware. Feb 1 20:38:14 kernel: protocol 0800 is buggy, dev br0 Feb 1 20:38:17 kernel: protocol 86dd is buggy, dev eth0 Feb 1 20:38:17 kernel: protocol 86dd is buggy, dev br0 Feb 1 20:38:21 kernel...
  4. D

    AiMesh for Tri-band routers: RT-AC5300, GT-AC5300

    I have the errors too and tried disabling bonding/link aggregation on my GT-AC5300 even though it was already set. Went through 20-30 seconds of applying even performed a reboot afterwards but the “protocol is buggy” messages are still being spammed in the syslog. I’ll stay on this new release...
  5. D

    AiMesh for Tri-band routers: RT-AC5300, GT-AC5300

    Also getting kernel: protocol 0800 is buggy messages on the new official firmware Version 3.0.0.4.384.20287 (GT-AC5300) Reverted back to beta build 19612. Is this official firmware stable enough for prime time?
Top