Jump to content
  • 0

[4.1A.10] - Standard is wrong


Question

Posted

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.

Screenshot-2023-09-30-16-02-03-409-com-m

 

Screenshot-2023-09-30-16-06-43-585-com-m

 

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)"

}

  • Thanks 1

11 answers to this question

Recommended Posts

  • 0
Posted
В 30.09.2023 в 18:15, PriSonerS61 сказал:

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.

Please provide the output of the show ip hotspot command on the controller (only the extender device data block is needed), as well as the output of the show mws associations command (is it executed on the extender itself?) and the self-test files from both devices.

  • 0
Posted
18 minutes ago, eralde said:

Please provide the output of the show ip hotspot command on the controller (only the extender device data block is needed), as well as the output of the show mws associations command (is it executed on the extender itself?) and the self-test files from both devices.

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

Spoiler

{
            "mac": "50:ff:20:**:**:**",
            "via": "50:ff:20:**:**:**",
            "ip": "192.168.1.2",
            "hostname": "Sprinter",
            "name": "Sprinter (KN-3710)",
            "system-mode": "extender",
            "interface": {
                "id": "Bridge0",
                "name": "Home",
                "description": "Home network"
            },
            "dhcp": {
                "static": true
            },
            "registered": true,
            "access": "permit",
            "schedule": "",
            "priority": 6,
            "active": true,
            "rxbytes": 1808496,
            "txbytes": 3255177,
            "uptime": 152374,
            "first-seen": 152374,
            "last-seen": 18,
            "http-port": 80,
            "description": "Keenetic Sprinter (NDMS 4.01.A.10.0-0): KN-3710",
            "firmware": "4.01.A.10.0-0",
            "traffic-shape": {
                "rx": 0,
                "tx": 0,
                "mode": "mac",
                "schedule": ""
            },
            "mac-access": {
                "Bridge0": "deny",
                "Bridge1": "deny"
            }
        },

  • 0
Posted
1 час назад, PriSonerS61 сказал:

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

I apologize, but I misled you. We use data from the show mws member (on the controller) command output do display the Wi-Fi standard in the UI.
Still the show mws member command output is present in the self-test file, so I've checked it out.

It looks like the controller UI shows the correct standard, there is no 802.11ac for the 2.4 GHz band.
https://help.keenetic.com/hc/en-us/articles/213968949-What-you-need-to-know-about-Wi-Fi-5-IEEE-802-11ac-

We should fix the standard displayed in the extender UI.

  • 0
Posted
12 minutes ago, eralde said:

I apologize, but I misled you. We use data from the show mws member (on the controller) command output do display the Wi-Fi standard in the UI.
Still the show mws member command output is present in the self-test file, so I've checked it out.

It looks like the controller UI shows the correct standard, there is no 802.11ac for the 2.4 GHz band.
https://help.keenetic.com/hc/en-us/articles/213968949-What-you-need-to-know-about-Wi-Fi-5-IEEE-802-11ac-

We should fix the standard displayed in the extender UI.

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)

Spoiler

"backhaul": {
                "uplink": "WifiMaster1/WifiStation0",
                "root": "8000.50:ff:**:**:**:**",
                "bridge": "8000.50:ff:**:**:**:**",
                "cost": 50,
                "ap": "WifiMaster0/Backhaul0",
                "authenticated": true,
                "txrate": 702,
                "uptime": 4264,
                "ht": 80,
                "mode": "11ac",
                "gi": 800,
                "rssi": -52,
                "mcs": 8,
                "txss": 2,
                "ebf": true,
                "dl-mu": true,
                "pmf": true,
                "security": "wpa2-psk"
            },


controller

Spoiler

controller.png

 

extender

Spoiler

extender1.png

  • 0
Posted
В 13.10.2023 в 10:17, PriSonerS61 сказал:

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?

Looks like we've found the source of the issue. It will be fixed in one of the future builds.

  • Thanks 2
  • 0
Posted
9 minutes ago, eralde said:

Looks like we've found the source of the issue. It will be fixed in one of the future builds.

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?

  • 0
Posted
10 минут назад, PriSonerS61 сказал:

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?

No, at this point is looks like the issue is not related to the UI.

  • Thanks 1

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...