-
Posts
134 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Downloads
Blogs
Events
Everything posted by PriSonerS61
-
IntelliQoS Page (Smart Queue Management) - A few feature requests
PriSonerS61 replied to PriSonerS61's question in Web interface
I don't quite understand your first message. Aren't the "Smart Queue Management" and "Application classification and prioritization" features independent of each other? I just wanted an on/off feature for the Smart Queue Management feature because it limits the speed according to the value entered. Maybe the user may want to remove or disable it later. ------- Yes I agree with that, if we are not forced to enter integers in mbps, it will indirectly work the same as kbps. -
IntelliQoS Page (Smart Queue Management) - A few feature requests
PriSonerS61 posted a question in Web interface
Hello. I think IntelliQoS is missing a few controls. @eralde These are : 1) Enable / disable 2) MBPS / KBPS selection Feature 1 is needed because : SQM cannot be disabled, there is no control for this in the new interface. When you want to disable it, you cannot enter the value 0 or leave it empty. The 2nd feature is needed for the following reason: Sometimes users may want to fine tune the speed in KBPS. I think it would be good to give this choice to the user. https://ibb.co/mBtd1xD -
Hello @eralde. There is a small spelling mistake in the Turkish language. It says "ipv4" where it should say "ipv6". Actually, that is the ipv6 section. There is no problem in English language, there is this problem in Turkish language. Tr : https://ibb.co/F0fscdy En : https://ibb.co/yQ16cNr
-
[4.1.A.16] - Error in application names
PriSonerS61 replied to PriSonerS61's question in Web interface
Yes exactly, I noticed it in Alpha 15 but I forgot to report it. I thought you didn't report it because it wasn't fixed in Alpha 16, but as usual you did. -
Hello @eralde @Anna Zhelankina. There is an error in application names in the new interface. Also there is something called "private-cloud" in the new interface. What is this because there is no such thing in the old interface. https://ibb.co/ssNPCP8 https://ibb.co/cTMS0Vm
-
Hello. The title is a bit off. The reason is the 26px space on the left side. It will be fixed if the CSS rule is removed. @eralde @Anna Zhelankina Before After
-
Good news. I'm wondering, is the source of the problem related to the interface or something else ? Does it have anything to do with the old problem and fix I posted above?
-
Hello @eralde. @Padavan doesn't seem to be active for a long time. Were you able to determine the cause of the problem in the background?
-
This is another proof that in the data coming to the page via RCI, i.e. in "show mws member", it looks correct, but in the interface it looks wrong. https://ibb.co/vH6CvgK
-
In the "show mws member" output, "mode": "11ac". It also appears as "AC" in Selftest. If the data is taken from the "show mws member" output, how can it be wrong on the interface when the "show mws member" output has the correct data ? My device is already connected with 5ghz, not 2.4ghz. 5ghz 2x2 80mhz In this case, the data in the "show mws member" output matches the "mode" data on the interface of the extender device, but the data on the controller device does not match. Contrary to what you say, the data on the interface of the controller device should be corrected, not the data on the interface of the extender device. show mws member (controller) controller extender
-
Maybe the problem is related to the problem and fix in the link below. Maybe it could be a clue...
-
Hello. Thank you for your concern. The command "show mws associations" was executed on the "controller" device. Anyway, no response will be returned when this command is written to the extender device. In the next hidden message I will tag you and attach the self-test file from both devices. show ip hotspot
-
Hello @eralde. As I mentioned in the title, the "routing" page does not load. The following error appears in the chrome developer console. (Tested with chrome and microsoft edge)
-
Hi @eralde On the "Wi-fi system" page, the "standard" data appears incorrect. On this page it is 802.11N, while on the extender interface and in the "show mws associations" output it is 802.11AC There should be 802.11AC everywhere. show mws associations { "station": [ { "mac": "*******", "ap": "WifiMaster0/Backhaul0", "authenticated": true, "txrate": 702, "rxrate": 867, "uptime": 16144, "txbytes": 170933203, "rxbytes": 1501900948, "ht": 80, "mode": "11ac", "gi": 800, "rssi": -53, "mcs": 8, "txss": 2, "ebf": true, "dl-mu": true, "pmf": true, "security": "wpa2-psk" } ], "prompt": "(config)" }
-
Hello. If we log out while in the old interface, we are greeted by a blank screen and it stays there. When this happens, various errors occur in the chrome dev. console. I am attaching them as well. This does not happen when logging out of the new interface. Just refresh the page to get rid of this problem. @eralde@Anna Zhelankina Normal url : http://192.168.1.1/login?backUrl=%2Fdashboard When there is a problem url : http://192.168.1.1/
-
Hello. In the new interface, the "clear settings" button in the "WISP" tab seems to be forgotten. @eralde @Anna Zhelankina
-
Then I think this feature is a bit ridiculous. Our goal is to display the popup in any case. This prevents us from seeing more data at first glance and causes unnecessary scrolling. I think these pop-ups should be fixed after they are opened, as they were before.
-
I took a video and posted it hidden on youtube. I am sharing the youtube link as a hidden message just before this message. In the video I compared the popup in the old interface and the popup in the new interface. You will see it clearly from there. In the old interface: the popup page is at max page height and remains fixed. When the page is scrolled, only the page content is scrolled. But in the new interface: the popup does not take the max. page height at the start. When the page is scrolled with the scroll key, the pop-up scrolls to the max. page height. So it moves. This should not happen. It should be fixed like in the old interface. 1) windows 11 / chrome I don't write other details as they will be seen in the video.