Hot Wlan

[Bowie Maur]

Wejust got a new 9800-40 in and I can't figure out where to go to map an interface to an SSID like we do on the previous controllers. I was trying to follow this document, but the commands don't work.

Unlike AireOS controllers, in 9800 it is not compulsory that you need an interface mapped to a WLAN. You can simply create a L2 VLAn like you do in a switch and tag it to the SSID using policy tag. As Scott suggested go through the workflow it will make your life wasy. If you going to do it in CLI you may follow below.

In IOS-XE, you do not want to define dynamic interface (or SVI) on your controller. In simple terms, it only has one SVI which is controller management interface IP. For all other SSID mapped interfaces, you simply has just L2 vlan define on the controller and trunk them to switchport which connect to switch.

In AireOS configuration, for Wlans that were anchored to an anchor controller we would create a bogus vlan/IP address on the AireOS controller and that would get anchored to the foreign controller where clients would receive their IP address. On the IOS-XE controllers, do you still need to specify a vlan for wlans that are anchored like this? Or do you just use the management vlan for the controller?

On IOS-XE you define a Policy Profile and map that to a VLAN name or VLAN Group name, and then you assign that Policy Profile to a WLAN profile under an Policy Tag. Then you create a Flex Profile with the VLAN Name to ID mapping and assign that to a Site Tag. Finally you assign those Tags to the corresponding APs.

It seems that simple egress limiting for wan with fq_codel and simplest.qos is quite enough for my fiber to achieve 700Mbps upload and matching download, with A quality for bufferbloat score of DLS speed test.

Mmmh, sqm requires you to set fix rate limits and will only work well, if these limits are below the actual wifi link rate it can work (and considerably so, for wifi I would guess you need to set the shaper to 60-70% of the reported stable link rate). But since wifi link rates depend on your RF environment and distance to the router, they typically are not stable but vary over time, making the sqm approach somewhat sub-optimal for wifi...

For the ath9k and more recently for the ath10k atheros/qualcomm wifi driver there is an airtime fairness mode implemented which does fq_codel in the wifi driver itself (which nows the link rate and hence can always work with a decent and recet estimate of the available linkrate) which helps quite a lot. I was under the impression that this would work for your mediatek based radio as well. I wonder why you see issues at all.

Let me elaborate, sqm in reality does not know about internet down- and upload directions, all it knows is the directionality of each interface it is instantiated on: for the transmit/TX/egress side, sqm will evaluate the "upload" option in /etc/config/sqm (for the respective interface) and for receive/RX/ingress side it will evaluate the download option (it will instantiate an IFB device to route packets through and instantiate the shaper there, as Linux does not allow to attach qdiscs directly to the ingress side of an interface). Why imply internet down and upload directions in the GUI and the UCI file then? Well, the whole directionality issue is a bit too opaque and complicated for most users, so instead of having to explain these intricacies to every user, we opted for keeping the typical case, SQM operating on the wan interface, somewhat intuitive, accepting that people using SQM on inward facing interfaces will have to research and understand this issue.

@Enig123, I strongly recommend you to move to an x86 router. If you can't afford that, move to a RPi 4 with an extra USB NIC which is cheaper. You can use your D-Link device as a smart switch and WiFi access point.

It's an MT7621AT processor. That's a dual core 880MHz MIPS. Those support offloading if I understand correctly, which is the only way you're going to route 700Mbps, but offloading is NOT compatible with SQM, so if you have offloading enabled then SQM isn't actually running.

Are you saying that you are able to instantiate a 700Mbps SQM interface on the WAN both directions, connect via ethernet so the wifi isn't involved, and run a speedtest without offloading and get the full 700Mbps throughput? Because that doesn't match anything else I've seen posted to this forum from others.

I concurr, impressive, could you by any chance run a dslreports speedtest and post the results here, please? (See -qos-recommended-settings-for-the-dslreports-speedtest-bufferbloat-testing/2803 for ecommendations for that test and how to link the results here in the forum)

I just did a speed test using my j1900 and ATT gigabit fiber. It reached 663 Mbps down and 580 up, peak overall CPU usage reached about 50%, with one core peaking at about 80% and devoted entirely to softirq, two other cores at 40% softirq each, and one core free for other processes...

Basically your results are expected. The router receives up to 700Mbps of packets from WAN, but can only send a couple tens to 100 megabits through the wifi, so you get a huge queue at the WiFi. by restricting your two wifi values to 12Mbps and 120Mbps you are managing those send queues. The only problem will be when for example you connect to wlan0 via wifi from "far away" so that the signal is not great and your modulation rate is say 32Mbps, while the queue assumes 120Mbps can pass. You will still get bufferbloat there.

The thing is that there is no single number you can put on wifi so it will always give good results no matter how far away you connect from, because wifi will degrade down to only 6Mbps or even 1Mbps if you still allow old modulation rates.

I managed to set up my Pi and installed Pi-Hole. The Pi-config was done headless via Wifi - easy so far

Since all is running well I now want to hardwire my Pi to FritzBox via cable.

Question: How can I achieve that under Webinterface -> Settings -> Pi-hole Ethernet Interface it changes to eth0 instead of wlan0 ?

Hi,

Does anybody know whats the issue here. We have multiple models they're all WIFI models and i know they have the WIFI cards in them but we have a lot of printers that we see with this message in the settings.

-Bluetooth

-802.11 WLAN-not installed

-Ethernet

-Serial

When we see "WLAN -Not Installed" on the display, it means that the printer doesn't have the WiFi module. We can verify that by issuing the following SGD command.

! U1 getvar "wlan.mac_addr"

If "00:00:00:00:00:00" is returned from the above command, it tells us that there is no mac address of a WiFi module, which can further confirms that there is no WiFi module installed on the printer. If a valid mac address is returned by the above SGD command while we still see "WLAN -Not Installed" on the display, then there could be a hardware issue. In the case of hardware issue, we should contact the Zebra Tech Support.

3a8082e126