Gargoyle 1.15.x BETA - 2024-11-13 - Based on OpenWrt 23.05

[oliver44]

Hi,

@Lantis, the latest version proposed by you with Gl-mt6000 on the 5Ghz wifi side sees just channel 36 and 100, plus the wifi does not activate, does not appear active wifi does not activate, does not appear active wifi does not activate, does not appear active with160Mhz!

Code: Select all

Device Name:Gargoyle
Gargoyle Version:1.15.X (Built 20241014-0033 git@347e0534)
Model:GL.iNet GL-MT6000

on the other hand, I was impressed after disabling Bandwidth Monitor and activating packet steering in speed test, I get 928 download and 930 upload

on the wifi side 5Ghz with 80Mhz reach 740Mbps

[oliver44]

I managed to connect now with 160Mhz but I had to change the country from Romania to Germany, I will send you the system logs privately

with Xiaomi 14, which supports wifi 6, I got 860Mbps download and 930Mbps upload speed test on 160Mhz!

[Lantis]

Check OpenWrt 23.05.5 for the same behaviour and come back.

[ViBE]

looks like something wrong with mt7620(?) devices. or at least with Nexx WT3020F mini routers. i have two of this model. first i tested with 1.14, then with the beta 1.15. the wifi bandwidth is terrible and laggy. the top wifi speed is ~16 Mbps. i also tested the latest OpenWRT and it is affected by this issue too.

since i have the stock firmware and figured out how to install it i tested it too. with the stock there are no terrible lag spikes and the top wifi bandwidth is around ~93 Mbps. this is fine since this router only have 100 Mpbs lan.

i know this is not a Gargoyle issue, but i hardly ever use OpenWRT and reporting bugs to OpenWRT is kinda confusing.

[Lantis]

Unfortunately OpenWrt is where you need to report the issue.
Reproduce the problem on OpenWrt 23.05.5 and post in the forums if anyone has the same issue or can see an issue with your settings.

If you want to try a snapshot build you can check if that fixes the issue, in which case it is just a matter of time before the fix is available to you. Otherwise the problem will carry forward forever until someone finds it and says something.

If the forum confirms your issue or otherwise can’t disprove it, you would then post an issue on GitHub.

[angus]

Hi Lantis,
Band steering on 1.15.x_20241014 is not working. That was good for 1.15.x_20240811. Do you see same symptom? Thanks. My device is WRT3200ACM.

[Lantis]

I have not noticed anything significantly different no.
You are seeing connected hosts on other devices working correctly (to indicate that usteer is running)?

[angus]

Hi Lantis,
Band steering on 1.15.x_20241014 is not working. That was good for 1.15.x_20240811. Do you see same symptom? Thanks. My device is WRT3200ACM.

Ooops! 2.4G Wi-Fi seems to not act for unknown reason. Since 2.4G Wi-Fi LED is not blinking. Reboot the device and wait for a while but see it happens again.

[ViBE]

Unfortunately OpenWrt is where you need to report the issue.
Reproduce the problem on OpenWrt 23.05.5 and post in the forums if anyone has the same issue or can see an issue with your settings.

If you want to try a snapshot build you can check if that fixes the issue, in which case it is just a matter of time before the fix is available to you. Otherwise the problem will carry forward forever until someone finds it and says something.

If the forum confirms your issue or otherwise can’t disprove it, you would then post an issue on GitHub.

yeah... meanwhile i started a thread on owrt forum. atm moment it looks like it is an encryption related issue, because with WPA2 the wifi performance way better.

btw i would like to use these routers as extender. but maybe i'm doing something wrong. after a fresh start if i instantly set the repeater mode the wifi network not always visible. and if yes not all the devices can connect. it's like something interfering but i cannot figure out what.

[hillbilly]

Hi Lantis,

Thanks for the new 1.15.0 release. I've flased it on a TP-Link Archer A6 v3.0, have just configured it. I normally only enable https for admin, and also enable https admin from WAN. But I found a bug with https, I have tried Chrome and Edge browers, same error.
---------------
Your connection isn't private
Attackers might be trying to steal your information from 192.168.1.1 ...

192.168.1.1 uses encryption to protect your information. When Microsoft Edge tried to connect to 192.168.1.1 this time, the website sent back unusual and incorrect credentials. This may happen when an attacker is trying to pretend to be 192.168.1.1, or a Wi-Fi sign-in screen has interrupted the connection. Your information is still secure because Microsoft Edge stopped the connection before any data was exchanged.

You can't visit 192.168.1.1 right now because the website sent scrambled credentials that Microsoft Edge can't process. Network errors and attacks are usually temporary, so this page will probably work later.
---------------

With the previous versions, I could click on advance, "accept risk...", then it allows me in. But for 1.15.0, it is not working.