Archer A7/C7 wifi speed under 40Mbps

TL; DR:

I am getting measurements around 40Mbps over wifi 5 with OpenWRT on my Archer A7 and Archer C7. The link speed says it should be closer to 450MBps. I want it to be at least over 80Mbps, which is the speed of my Internet connection.

Data

I am running iperf3 -s on an older laptop (connected via ethernet and one 1Gbps router).

  • Running iperf3 -c on my phone to that laptop shows rates between 25Mbps and 45Mbps, average always under 40Mbps. This is a pixel 6 pro. The settings say it is "Wi-Fi 5" and the tx/rx link speeds are in the 300-400Mbps range. I am running iperf3 in termux.
  • Running iperf3 -c on my newer ubuntu laptop show similar rates of 40Mbps. The network connection info says "Speed: 351Mb/s". This is what the AP says about the connection: 351.0 Mbit/s, 80 MHz, VHT-MCS 4, VHT-NSS 2 468.0 Mbit/s, 80 MHz, VHT-MCS 5, VHT-NSS 2
  • Running iperf3 -c on that same laptop on Ethernet shows 950Mbps or so transfer rates.

OpenWRT hardware

  • an Archer C7 v4 as the dumb AP
  • an Archer A7 v5 as the router.
  • They are configured with the same ssid in 5GHz and 2.4Ghz.
  • They have the 802.11r FT enabled on both frequencies.
  • I have the channels set to auto. This is a suburb, with a lot of neighbors in range. Maybe picking something would be better, but I am not looking for incredible speed.
  • OpenWRT 22.03.3. Installed over the weekend. I was using dd-wrt and I remember similar speeds (but I don't have the numbers, so take that data with a grain of salt).

Additional Background

I see some other posts about these routers and the OPs are saying things like, "I can only get 300Mbps, and I want 900Mbps". Something is definitely different for me. I am not getting anywhere close to those speeds. I have a good GB ethernet network for the desks and servers in my house. So I really just need a wifi connection that is as fast as the 80Mbps DSL connection I have. If I need to do fast NAS transfers, I can just grab a cord.

I have a lot of wifi devices in my house. I have created a lot of wifi IoT devices and I have about 80 devices on my wifi. They are mostly tiny ESP32/ESP8266 devices running open source firmware. There are a handful of chromecasts and a dozen or so user devices (phones, tablets, laptops). There are few SBCs and servers doing things like NAS and Home Assistant. I suppose I could change the AP ssid and then force the channels to be separate, on a separate LAN to try to isolate these devices as the issue.

Config dumps (from my router)

iwinfo
root@OpenWrt:~# iwinfo
wlan0     ESSID: "xxxxxx"
          Access Point: D8:07:B6:F8:8B:5F
          Mode: Master  Channel: 36 (5.180 GHz)  HT Mode: VHT80
          Center Channel 1: 42 2: unknown
          Tx-Power: 23 dBm  Link Quality: 44/70
          Signal: -66 dBm  Noise: -99 dBm
          Bit Rate: 293.8 MBit/s
          Encryption: WPA2 PSK (CCMP)
          Type: nl80211  HW Mode(s): 802.11ac/n
          Hardware: 168C:003C 0000:0000 [Qualcomm Atheros QCA9880]
          TX power offset: none
          Frequency offset: none
          Supports VAPs: yes  PHY name: phy0

wlan1     ESSID: "xxxxxx"
          Access Point: D8:07:B6:F8:8B:60
          Mode: Master  Channel: 1 (2.412 GHz)  HT Mode: HT20
          Center Channel 1: 1 2: unknown
          Tx-Power: 24 dBm  Link Quality: 65/70
          Signal: -45 dBm  Noise: -95 dBm
          Bit Rate: 60.8 MBit/s
          Encryption: WPA2 PSK (CCMP)
          Type: nl80211  HW Mode(s): 802.11b/g/n
          Hardware: 168C:0033 168C:9560 [Qualcomm Atheros QCA9560]
          TX power offset: none
          Frequency offset: none
          Supports VAPs: yes  PHY name: phy1
os-release
root@OpenWrt:~# cat /etc/os-release
NAME="OpenWrt"
VERSION="22.03.3"
ID="openwrt"
ID_LIKE="lede openwrt"
PRETTY_NAME="OpenWrt 22.03.3"
VERSION_ID="22.03.3"
HOME_URL="https://openwrt.org/"
BUG_URL="https://bugs.openwrt.org/"
SUPPORT_URL="https://forum.openwrt.org/"
BUILD_ID="r20028-43d71ad93e"
OPENWRT_BOARD="ath79/generic"
OPENWRT_ARCH="mips_24kc"
OPENWRT_TAINTS=""
OPENWRT_DEVICE_MANUFACTURER="OpenWrt"
OPENWRT_DEVICE_MANUFACTURER_URL="https://openwrt.org/"
OPENWRT_DEVICE_PRODUCT="Generic"
OPENWRT_DEVICE_REVISION="v0"
OPENWRT_RELEASE="OpenWrt 22.03.3 r20028-43d71ad93e"
iw list
root@OpenWrt:~# iw list
Wiphy phy1
	wiphy index: 1
	max # scan SSIDs: 4
	max scan IEs length: 2257 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Device supports T-DLS.
	Available Antennas: TX 0x7 RX 0x7
	Configured Antennas: TX 0x7 RX 0x7
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * outside context of a BSS
	Band 1:
		Capabilities: 0x11ee
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 3839 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-23
		Frequencies:
			* 2412 MHz [1] (24.0 dBm)
			* 2417 MHz [2] (24.0 dBm)
			* 2422 MHz [3] (24.0 dBm)
			* 2427 MHz [4] (24.0 dBm)
			* 2432 MHz [5] (24.0 dBm)
			* 2437 MHz [6] (24.0 dBm)
			* 2442 MHz [7] (24.0 dBm)
			* 2447 MHz [8] (24.0 dBm)
			* 2452 MHz [9] (24.0 dBm)
			* 2457 MHz [10] (24.0 dBm)
			* 2462 MHz [11] (24.0 dBm)
			* 2467 MHz [12] (disabled)
			* 2472 MHz [13] (disabled)
			* 2484 MHz [14] (disabled)
	valid interface combinations:
		 * #{ managed } <= 2048, #{ AP, mesh point } <= 8, #{ P2P-client, P2P-GO } <= 1, #{ IBSS } <= 1,
		   total <= 2048, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz }

	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Supported extended features:
		* [ RRM ]: RRM
		* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
		* [ SCAN_RANDOM_SN ]: use random sequence numbers in scans
		* [ SCAN_MIN_PREQ_CONTENT ]: use probe request with only rate IEs in scans
		* [ CAN_REPLACE_PTK0 ]: can safely replace PTK 0 when rekeying
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ DEL_IBSS_STA ]: deletion of IBSS station support
		* [ MULTICAST_REGISTRATIONS ]: mgmt frame registration for multicast
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
Wiphy phy0
	wiphy index: 0
	max # scan SSIDs: 16
	max scan IEs length: 199 bytes
	max # sched scan SSIDs: 0
	max # match sets: 0
	Retry short limit: 7
	Retry long limit: 4
	Coverage class: 0 (up to 0m)
	Device supports AP-side u-APSD.
	Available Antennas: TX 0x7 RX 0x7
	Configured Antennas: TX 0x7 RX 0x7
	Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * AP/VLAN
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * P2P-device
	Band 2:
		Capabilities: 0x19ef
			RX LDPC
			HT20/HT40
			SM Power Save disabled
			RX HT20 SGI
			RX HT40 SGI
			TX STBC
			RX STBC 1-stream
			Max AMSDU length: 7935 bytes
			DSSS/CCK HT40
		Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
		Minimum RX AMPDU time spacing: 8 usec (0x06)
		HT TX/RX MCS rate indexes supported: 0-23
		VHT Capabilities (0x338001b2):
			Max MPDU length: 11454
			Supported Channel Width: neither 160 nor 80+80
			RX LDPC
			short GI (80 MHz)
			TX STBC
			RX antenna pattern consistency
			TX antenna pattern consistency
		VHT RX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT RX highest supported: 0 Mbps
		VHT TX MCS set:
			1 streams: MCS 0-9
			2 streams: MCS 0-9
			3 streams: MCS 0-9
			4 streams: not supported
			5 streams: not supported
			6 streams: not supported
			7 streams: not supported
			8 streams: not supported
		VHT TX highest supported: 0 Mbps
		Frequencies:
			* 5180 MHz [36] (23.0 dBm)
			* 5200 MHz [40] (23.0 dBm)
			* 5220 MHz [44] (23.0 dBm)
			* 5240 MHz [48] (23.0 dBm)
			* 5260 MHz [52] (24.0 dBm) (radar detection)
			* 5280 MHz [56] (24.0 dBm) (radar detection)
			* 5300 MHz [60] (24.0 dBm) (radar detection)
			* 5320 MHz [64] (24.0 dBm) (radar detection)
			* 5500 MHz [100] (24.0 dBm) (radar detection)
			* 5520 MHz [104] (24.0 dBm) (radar detection)
			* 5540 MHz [108] (24.0 dBm) (radar detection)
			* 5560 MHz [112] (24.0 dBm) (radar detection)
			* 5580 MHz [116] (24.0 dBm) (radar detection)
			* 5600 MHz [120] (24.0 dBm) (radar detection)
			* 5620 MHz [124] (24.0 dBm) (radar detection)
			* 5640 MHz [128] (24.0 dBm) (radar detection)
			* 5660 MHz [132] (24.0 dBm) (radar detection)
			* 5680 MHz [136] (24.0 dBm) (radar detection)
			* 5700 MHz [140] (24.0 dBm) (radar detection)
			* 5720 MHz [144] (24.0 dBm) (radar detection)
			* 5745 MHz [149] (30.0 dBm)
			* 5765 MHz [153] (30.0 dBm)
			* 5785 MHz [157] (30.0 dBm)
			* 5805 MHz [161] (30.0 dBm)
			* 5825 MHz [165] (30.0 dBm)
			* 5845 MHz [169] (27.0 dBm) (no IR)
			* 5865 MHz [173] (27.0 dBm) (no IR)
	valid interface combinations:
		 * #{ managed, P2P-client } <= 16, #{ P2P-GO } <= 3, #{ AP } <= 16, #{ IBSS } <= 1,
		   total <= 16, #channels <= 1, STA/AP BI must match, radar detect widths: { 20 MHz (no HT), 20 MHz, 40 MHz, 80 MHz, 80+80 MHz, 160 MHz }

	HT Capability overrides:
		 * MCS: ff ff ff ff ff ff ff ff ff ff
		 * maximum A-MSDU length
		 * supported channel width
		 * short GI for 40 MHz
		 * max A-MPDU length exponent
		 * min MPDU start spacing
	max # scan plans: 1
	max scan plan interval: -1
	max scan plan iterations: 0
	Maximum associated stations in AP mode: 0
	Supported extended features:
		* [ VHT_IBSS ]: VHT-IBSS
		* [ RRM ]: RRM
		* [ SET_SCAN_DWELL ]: scan dwell setting
		* [ FILS_STA ]: STA FILS (Fast Initial Link Setup)
		* [ CQM_RSSI_LIST ]: multiple CQM_RSSI_THOLD records
		* [ CONTROL_PORT_OVER_NL80211 ]: control port over nl80211
		* [ TXQS ]: FQ-CoDel-enabled intermediate TXQs
		* [ AIRTIME_FAIRNESS ]: airtime fairness scheduling
		* [ AQL ]: Airtime Queue Limits (AQL)
		* [ CONTROL_PORT_NO_PREAUTH ]: disable pre-auth over nl80211 control port support
		* [ DEL_IBSS_STA ]: deletion of IBSS station support
		* [ SCAN_FREQ_KHZ ]: scan on kHz frequency support
		* [ CONTROL_PORT_OVER_NL80211_TX_STATUS ]: tx status for nl80211 control port support
/etc/config/wireless
root@OpenWrt:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'pci0000:00/0000:00:00.0'
	option band '5g'
	option htmode 'VHT80'
	option cell_density '0'
	option channel 'auto'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option encryption 'psk2'
	option key 'redacted'
	option ieee80211r '1'
	option nasid 'alsoredacted'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option ssid 'xxxxxx'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/ahb/18100000.wmac'
	option band '2g'
	option htmode 'HT20'
	option cell_density '0'
	option channel 'auto'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option encryption 'psk2'
	option key 'redacted'
	option ieee80211r '1'
	option nasid 'alsoredacted'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option ssid 'xxxxxx'

If you want these same dumps from the AP, I can get them.

Direct Questions

  1. What settings should I look at to test a difference?
  2. What logs or info would be helpful for debugging?
  3. I have seen a lot of warnings that theoretical maxes are higher than reality (which is totally fine). But they refer to something like a 25-50% reduction in speed, not 90% reduction. Am I right to want more from wifi?

Thank you for reading and responding. This community and project are awesome.

  1. I am not completely sure, but I think i have read somewhere that setting channels to "auto" is not really auto, but rather sets them to the lowest channel number, hence channel 36 in 5 GHz. Probably channel 1 in 2.4 GHz? You can check via wifi-analyzer

  2. My stock firmware (different device) did the same as you did: two radios configured to be on same SSID. Creating separate SSIDs for the 2.4 GHz and 5 GHz brought me tremendous improvements. In my case, my client devices were not "intelligent" enough to know, which GHZ band they should connect to, since the SSID was the same. Sometimes, when there were larger lags, they switched automatically to the other band, which created a mega lag. Also, in far distance, it often tried to switch to 5 GHz band, even though 2.4 GHz band was more stable. Installing OpenWrt and separating SSID's eliminated almost all problems I have. Maybe it is the same here: your client devices connect to 2.4 GHz, even though 5 GHz would allow much more throughput :slight_smile:

In any case: having 80 devices connected, while doing tests could have an negative impact on throughput. Try to test with a single client first on channels without contestation and interference to find out max throughput. Only then later add other devices.

1 Like

I have some more information.

  • The iperf3 server was connected on a 1Gb switch, through a long cable to the router. The test where I acheived 950Mbps was also connected to that switch. So that is a bad test.
  • I moved the server to connect directly to the LAN port on the router. I saw improvements right away to about 100Mbps on wireless (and the same on wired, which I thought was super at 950).
    • I also unplugged the Gb switch and plugged it back in, and got 950 on the wired. So... weird. I think it thought the long cable was 10/100. I will inspect that cable a little more later.
  • I turned off the 2.4GHz band, and I renamed the AP to 'xxxxx-fast'. That kicked off almost all the devices and my laptop and phone are getting 220Mbps/450Mbps.
  • I turned the 2.4GHz back on, and reverted the change to the AP wifi radio name. I am getting 280 on my laptop still. But most devices haven't figured out they can reconnect.

So. It sounds like if I want to fix this, I need to be more detailed and diligent with which bits of hardware I have connected. I don't trust those long cable runs (they were terminated by myself. I have an ethernet pin tester, but it only checks they are connected, not one of these fancy ones that does frequency response). I also don't trust having 80 devices connected. I plan on pushing the IoT devices to another vlan (we'll see, I only have so much time and so many projects). Maybe I can do some A/B testing as I move them over.

You may be right. This, combined with whatever wiring issue I have, may be joining forces to hurt me. I really want them all to just Do-The-Right-Thing :tm:.

I'm happy to talk about this with anyone else who has an opinion. I want to learn more. I have dumped my whole wifi config here, so any other advice is welcome.

I have pretty much the same setup (although with RADIUS).
I see three differences:

  1. Band 1:Capabilities: 0x11ef (instead of 0x11ee)
  2. Country code missing for 5G
  3. hwmode for 2g is '11g' (for me)

Not sure if any of that helps. Apart from that, I do think you probably just want to set up a second radio for test purpose only.

Also, I am assuming default routing, and no fancy firewall stuff. FWIW - My firewall has a 50% impact on upload speed (quite a bit of rules to check).

1 Like

Thanks for taking a thorough look. :+1:

This is from the iw list. Is that something I can change? I thought the hardware dictated the results of that command. Both of my routers have 0x11ee in that field. I'm assuming that is a bit field and you have one more capability than I do. Not sure what it is though.

:man_facepalming:. Thanks. I will fix that. It was missing for all 4 networks.

I'm not sure what this is either. I have an htmode 'VHT80', and a band '2g'. I assumed that was the frequency (2.4GHz, and 5GHz). But that was a total guess :slight_smile:

band '2g' looks like it used to be called hwmode:

band string no (driver default) Specifies the band, possible values are 2g for 2.4 GHz, 5g for 5 GHz, 6g for 6 GHz and 60g for 60 GHz. (NEW since 21.02.2, replaces hwmode)

hwmode:

hwmode string no (driver default) Specifies the hardware mode, possible values are 11b for 2.4 GHz (used for legacy 802.11b only), 11g for 2.4 GHz (used for 802.11b, 802.11g and 802.11n) and 11a for 5 GHz (used for 802.11a, 802.11n and 802.11ac). Note that 11ng, 11na, 11n and 11ac are invalid options, this setting should largely be seen as controlling the frequency band. (DEPRECATED since 21.02.2, replaced with band)

So I think that is just because I am running 22.03.3.

1 Like
  1. agree - not sure if there are hw differences. I'm having C7v2's here
  2. ok - must be carry over from initial install. I started with 21.x :wink:

Curious to learn what in the end causes your low speeds. I do remember that in 21.x I sometimes after playing around with settings had low speeds too. Because I was learning, I just reflashed the device, which brought speeds back... Not sure that's helpful, but perhaps worth a try if all else fails..

1 Like

I had the same problem with slow speeds, solution for me is to go back to 21.02.05

https://github.com/openwrt/openwrt/issues/10224

1 Like

I did not look into your configuration files, but will share a few higher level suggestions.

In addition to keeping 2.4 GHz and 5 GHz on separate SSIDs, each AP should be on a different non-overlapping channel. You cannot control your neighbors, but interfering with your own AP's is something you can control. Enforcing different channels is also a good idea for 802.11r fast transfer. In general, if your AP signals are at least 20 dBm stronger than your neighbor's signals on a channel, interference from your neighbors won't be terrible.

For 2.4 GHz you only have three options: 1, 6 and 11 - so you might as well pick two (one for each AP) instead of using auto.

For 5 GHz, you only have 5 good choices assuming you are using 80 GHz wide channels: so pick two from 36, 149, 52, 100 and 132. These are the lowest channel numbers in each of the five 80 MhZ wide ranges associated with these channels. Channels 36 and 149 will offer the highest transit power, but the others are not terrible. I skipped over 116 because it overlaps the most common weather radar frequencies (TDWR channels 120, 124 and 128) and you're more likely to get kicked off by DFS on that channel, so might as well avoid it. I suggest starting with 36 and 149, since 5GHz does not travel as far, neighbor interference will be less of an issue on the 5GHz radios.

80 clients - wow! Fast transfer is great for you and your roaming phones and laptops in the house, but IOT clients do have a tendency to "stick" to the "wrong" AP sometimes. Especially if you reboot one AP and all 80 jump to the other AP and stay there.

You might consider setting up a separate VLAN for your IOT devices. This is just a good idea from a security standpoint anyway - how secure and updated is the firmware in all 80 of those IOT devices anyway? Yikes! I would not want to expose my main home network to 80 potential IOT "hack-bot" devices. Do not use fast transfer on the SSID's for this IOT VLAN, and use unique SSID's for the IOT VLAN on each AP. This way you can force your IOT clients to connect to specific AP's and assure your load is spread evenly between the two AP's.

If that is too much hassle (different SSID's for IOT on each AP), you can also use the mac filter option in your wireless configuration to exclude half your IOT devices from one AP and the other half from the other AP. That might be less time invested than the last two sentences of the preceding paragraph.

1 Like

I used wifi analizer and picked some.

The 5GHz band has nothing between 50-150. I tried setting it to 100 and the openwrt said it was disabled. So I think you're saying there are weather radio bands in my area that are blocking those bands.

This is on my road map. I have tried this before. I got stuck because I have some chromecasts and they talk to my phones via multicast (IIRC) and I had trouble separating them to another vlan.

Most of these devices are basically a single sensor or relay on a esp32. The code is esphome or tasmota or wled. This isn't code I wrote myself, but it is code I have read. It is local only, no cloud. They ping me when there is an update and I can batch update them with a few clicks. They don't need to be trusted though. They can live happily on a vlan. They only need to talk to my home assistant server. The only clients that ever visit their interface are my phone and my laptop.

I do have chromecasts and some shelly relays. Things like the kids tablets are honestly a bigger concern.

I have the firmware migration done. I am sorting my dhcp static leases. Getting these sorted into bins and getting good DNS values for all of them.

I will add some new ssids. Even if they go to the same LAN for now. Using ssids to force IoT stuff onto a specific 2.4GHz connection is a good idea.

Next will be changing my home assistant to use the hostnames and then I can move them anywhere without changing my config.

Then I can play with vlans and iptables and see what I can get away with. I can't block my wife's phone from the chromecasts.

I have to learn a lot with each of these steps. I really appreciate the advice and community here. I may make a new topic when I get to the vlan/mdns stuff. There is already excellent advice I have found reading other posts. Thank you.

I was actually thinking the same 2.4 GHz IOT SSID on both AP's, and the same 5 GHz IOT SSID on both AP's, but your approach is even simpler. With your approach, you will not have to use mac address filtering to force clients to particular AP's.

When you are ready for VLANs, This post and and the breadcrumbs it leads to may be a good start for you: https://forum.openwrt.org/t/what-switch-and-ap-running-with-latest-openwrt-would-you-recommend-me-for-my-new-iot-network/149774/19?u=eginnc.

1 Like

I made a ssid iot-dowstairs hidden on my router and iot-upstars hidden on my AP. They are both 2.4GHz. i am going through the devices and moving them over one at a time. For now, they are still connected to the main lan (which has a trunk link between the two). They are also still all getting static dhcp leases from the main router. Many of them are accessed by those IPs from home assitant. So I have to move them later. It is tedious. But hopefully I will only have to do each step once (famous last words).

At some point, I will see what it takes to change the ip address to hostname and change the connected lan to a vlan. Then I can find them at their new ip (by hostname) and start turning down the trust.

Just a few more days of this :slight_smile:

This is the main tutorial I was planning on following. The next one in the series is pushing the vlan tags over the trunk to the AP. I am still not sure where to put the chromecasts. They may need to just stay in the regular lan with my phones and computers.

OneMarcFifty does a good job explaining things. The second part in that series: https://www.youtube.com/watch?v=4t_S2oWsBpE will be of particular interest for your situation.

The posts I pointed you to do essentially the same things as those videos. Your Archer C7's are still using swconfig, not DSA, so be mindful of that difference.

It comes down to personal preference, but I use the following SSID's on all my AP's: Name-2G, Name-2G-IOT, Name-2G-GST, etc., Where Name-2G is the main home lan. And no, I do not know why I did not add "LAN" to it ;-). I repeat the same name sequence for the 5G network.

I previously used different SSID names for each AP, but I've since come around to the idea of not having 12+ visible SSID's and instead using 802.11r fast transfer, with some manual mac address filtering to force some troublesome clients to the AP I want them to use.

The advantage, beyond simplicity, is redundancy if one router is turned off or rebooted - clients auto shift to the other AP quickly and the house is peaceful, whereas previously it went something along the lines of "Are you messing with the internet, again !!!???!!!".

As you are discovering, it is a pain to reconnect various devices to a new SSID "layout," so whatever you do, begin with the long term end in mind is a great strategy.

Are you still running on 21.02.05, or have the newer 22.0.x solved the issue? I am currently only able to get 20Mbps from a newish iPhone to router using iperf, same as if I try to do a speedtest on fast.com, both unloaded and loaded.

Do you know if the non -ct drivers are bad for throughput, especially on 5GHz?