Arris NVG599 Passthrough Setup for Eero Pro 6E

So, utilizing the VPN is "fixing" it.  So, are there any QoS settings enabled on the eero that perhaps going to VPN is bypassing?

I don't suppose you know the actual server names you're connecting to so you can check to see if you're getting different IPs for those servers via VPN than when using the AT&T DNS servers.

Umm, up until now you've been showing us wired speed results. 

The two TaskManager graphs show Wifi.

Confused.

QoS is not on, on my computers or in the Eero app.

The Eero app shows that my ISP DNS is provided by 192.168.1.254.

The computers are getting a different DNS server:

SSID: Mxzxx
Protocol: Wi-Fi 5 (802.11ac)
Security type: WPA2-Personal
Network band: 5 GHz
Network channel: 36
Link speed (Receive/Transmit): 1300/866 (Mbps)
IPv4 address: 192.168.4.24
IPv4 DNS servers: 192.168.4.1
Manufacturer: Broadcom
Description: ASUS PCE-AC68 802.11ac Network Adapter
Driver version: 7.35.351.0
Physical address xxxxxxxxxxxxx

ProtonVPN assigns an IP address to whatever of their servers that I connect to, so yes, it would use whatever DNS they have.

I'm sorry, you missed my point.  I know that the DNS server will be different.  What I'm asking is if you know the exact DNS names of the destination hosts you're trying to download from so that you can compare the ANSWERS (i.e. the IP addresses) that you get from the DNS server while on VPN vs those you're getting from the eero (at 192.168.4.1), who is most likely forwarding requests to the AT&T Gateway at 192.168.1.254, who is forwarding the requests to 68.94.156.11 or 68.94.157.11 for resolution.

I am expecting that you're going to completely different servers via VPN.  Actually, even if the IP addresses are the same, due to geo-routing these days, you could still be going to different servers.

ipconfig /all | findstr "DNS\ Servers"
   DNS Servers . . . . . . . . . . . : 10.2.0.1   DNS Server on my computer when COnnected to VPN.
   DNS Servers . . . . . . . . . . . : 192.168.4.1

I'm not sure how to find what you're asking JefferMC,   Could you either tell me how to do it, or how to test on a server that you know?

Rather than checking via the DNS, when you (probably) don't know the actual server names you're downloading from, you could use a tool like NETSTAT to see what remote IPs your software is connecting to: open a CMD window in Administrator mode, and enter NETSTAT -b.  Look for lines that are owned by your downloader (the application executable appears in brackets under each line it applies to).  Note the foreign addresses.

I connected with ProtonVPN and downloaded files with Microsoft Edge.

I didn't use 4K Downloader for anything now, because that still only 25 mbps for Youtube.

Here is Netstat -b for downloading the newest GPU drivers from Nvidia through VPN: 

[msedge.exe]
  TCP    10.2.0.2:63803         63.140.36.101:https    ESTABLISHED
 [msedge.exe]
  TCP    10.2.0.2:63804         192.229.211.70:https   ESTABLISHED
 [msedge.exe]
  TCP    10.2.0.2:63805         sfo03s07-in-f115:https  ESTABLISHED
 [msedge.exe]
  TCP    10.2.0.2:63807         20.42.65.85:https      ESTABLISHED
 [msedge.exe]
  TCP    10.2.0.2:63808         ec2-34-205-91-201:https  ESTABLISHED
 [msedge.exe]
  TCP    10.2.0.2:63812         104:https              ESTABLISHED
 [msedge.exe]

One, you need to do the same thing with the VPN down if you can figure out which hosts have something to do with the driver download.

Unfortunately, none of these are conclusively connected with your driver download, and only one of them is located anywhere in particular.  If we knew which to focus on, that would help.  Edge (as with any browser) will connect to a lot of sites.

If you knew which server you were actually measure the speed of transfer with, when on VPN and when not on VPN, and could do a traceroute to them when connected that way, we might actually get somewhere.

Hi JefferMC,

This is the netstat -b info for downloading the same Nvidia GPU driver file from Nvidia.com:

  TCP    192.168.4.24:49972     52.226.139.185:https   ESTABLISHED
  WpnService
 [svchost.exe]
  TCP    192.168.4.24:54762     52.226.139.121:https   ESTABLISHED
 [OneDrive.exe]
  TCP    192.168.4.24:54775     13.107.21.200:https    ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54779     204.79.197.219:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54792     server-13-249-120-33:https  ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54805     104.46.162.226:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54845     mia09s20-in-f10:https  CLOSE_WAIT
 [HxTsr.exe]
  TCP    192.168.4.24:54846     sky400-1:imaps         CLOSE_WAIT
 [HxTsr.exe]
  TCP    192.168.4.24:54848     ua-in-f109:imaps       CLOSE_WAIT
 [HxTsr.exe]
  TCP    192.168.4.24:54849     52.96.44.162:https     ESTABLISHED
 [HxTsr.exe]
  TCP    192.168.4.24:54850     52.96.44.162:https     ESTABLISHED
 [HxTsr.exe]
  TCP    192.168.4.24:54854     e2-rr:https            CLOSE_WAIT
 [HxTsr.exe]
  TCP    192.168.4.24:54874     a23-34-63-66:https     ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54875     a23-34-63-66:https     ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54882     172.67.20.158:https    ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54885     server-18-64-155-93:https  TIME_WAIT
  TCP    192.168.4.24:54891     server-216-137-45-27:https  CLOSE_WAIT
 [msedge.exe]
  TCP    192.168.4.24:54892     mia09s26-in-f6:https   TIME_WAIT
  TCP    192.168.4.24:54897     a23-207-52-129:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54898     217:https              ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54905     ec2-54-185-100-133:https  CLOSE_WAIT
 [msedge.exe]
  TCP    192.168.4.24:54910     a23-207-48-129:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54921     ec2-34-205-91-201:https  TIME_WAIT
  TCP    192.168.4.24:54944     a23-34-63-65:https     ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54982     a104-97-127-44:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54995     192.229.210.202:https  ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:54996     mia09s20-in-f10:https  TIME_WAIT
  TCP    192.168.4.24:54997     mia07s60-in-f3:https   TIME_WAIT
  TCP    192.168.4.24:55015     219:https              ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55016     146.75.29.140:https    ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55017     152.199.2.76:https     ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55032     tzmiaa-ac-in-f19:https  ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55033     146.75.29.140:https    ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55037     a23-34-63-75:https     ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55041     a23-1-33-214:https     TIME_WAIT
  TCP    192.168.4.24:55055     236:https              ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55058     ec2-54-221-223-77:https  CLOSE_WAIT
 [msedge.exe]
  TCP    192.168.4.24:55060     146:https              ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55063     104.18.99.194:https    ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55064     8.43.72.97:https       ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55065     104.36.113.107:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55066     e1-rr:https            TIME_WAIT
  TCP    192.168.4.24:55067     141.226.124.48:https   TIME_WAIT
  TCP    192.168.4.24:55069     192.229.211.70:https   ESTABLISHED
 [msedge.exe]
  TCP    192.168.4.24:55087     a23-45-234-17:https    TIME_WAIT
  TCP    192.168.4.24:55095     1:https                ESTABLISHED
 [msedge.exe]

C:\Windows\system32>