Hi, following up on this previous topic:
Hi, I'm using my Brume 2 as my main router. It's connected to an ONT.
Since the latest firmware update (I updated 2 days ago to v4.6.4) I started to encounter internet speeds of 0.1Mbs (If have 600mb FTTH which always worked.) Ping was working but websites loading terribly slowly. It took me two days to figure out what the issue was. From my ISP I get DHCP and my wan vlan is 20. Great that we can add this to the UI nowadays!
Tried to check all cables > no issues found
I tried to connect the o…
Hi - any update on this bug? I tried to enable hardware acceleration again but experience still the same issue.
Network Acceleration:
OFF → normal wifi speed
Software → normal wifi speed (look like..)
HARDWARE → slowness, pages not loading, etc.
Testing with: https://speed.measurementlab.net/
I’m on a 1Gb FFTH symmetrical fibre connection at home.
Internet settings:
Brume connected to my ONT.
DHCP with VLAN 10 (VLAN from my FTTH provider).
Other settings:
WireGuard server on
AdGuard Home on
IPv6 off
Firmware:
Version4.7.4 / release6Model: Brume 2 - MT2500A
Hi
Could you provide a detailed network topology so we can better understand what's happening?
It appears that a Wi-Fi router connected to Brume 2 is experiencing abnormal speeds when hardware acceleration is enabled.
If you connect the PC directly to Brume 2 with hardware acceleration enabled, are the speeds normal?
Here's the setup. Let me check when home as well to run a speedtest from a wired device.
Internet
│
▼
┌──────┐
│ FTTH │ Fibre to the Home
└──┬───┘
│
┌──▼───┐
│ ONT │ Optical Network Terminal
└──┬───┘
│
┌──▼────┐
│Brume2 │ Security Gateway/Router
└──┬────┘
│
┌──▼─────────────────┐
│ PoE Switch │ TP-Link JetStream Omada
└──┬─────────────────┘
│
┌──▼──────────┐
│ Ruckus R550 │ WiFi Access Point
└─────────────┘
│
▼
Clients
Right, weird - tested with wired connection and all OK. Now going back to wireless and suddenly seems working with full wireless speeds.
It sounds like it was just a loose network cable.
But regardless, I'm glad to hear the issue has been resolved.