Deco XE 75 Ver 2.60 - Slow Upload Speeds with Verizon FIOS 1 Gig
Deco XE 75 Ver 2.60 - Slow Upload Speeds with Verizon FIOS 1 Gig
DECO XE75 Slow upload speed with Verizon
Model: Deco XE75
Hardware Version: V2
Firmware Version:
Verizon 1000/1000 fiber.
Deco XE75 V2.6 Giving me 1/10 of the upload speed I should be getting. See speedtest below:
Speedtest via ethernet. Wireless is similarly slow.
https://www.speedtest.net/result/17300619327
Firmware is updated, QOS not enabled
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @Hikeleader
Welcome to the community!
If you're able to, can you confirm the following information to help our community better understand your situation?
- Is the Ethernet speed test being performed while directly connected to the main Deco node?
- Can similar results (high download, slow upload) be replicated with other devices - including ones connected over Wi-Fi?
- Have you tried bypassing the Deco to test directly at the source and compare the results?
- Is your Internet source (e.g., modem, ONT, gateway) connected to the top, middle, or bottom port on the main Deco?
- Is the main Deco connected to a modem, or to a modem + router gateway device?
- Copy Link
- Report Inappropriate Content
Ryan,
Thanks for your reply. Connectivity seems to have improved. This is what I see now.
- Is the Ethernet speed test being performed while directly connected to the main Deco node? - Did test at main node and got good speeds: 907/848
- Can similar results (high download, slow upload) be replicated with other devices - including ones connected over Wi-Fi? - So this is where it gets interesting. If I stand near a node (like three feet away), be it the main or the two used as satellites I get very good wifi. Main: 397/450 , Sat 1: 488/585, Sat 2: 478/388. However as I move away from any of the nodes the upload speeds degrade much more than the download speeds. For example from various locations in house that are at least 20 feet from node or through at least one wall I get: 306/126 , 193/17 , 156/54 ,376/227, 336/122
- Have you tried bypassing the Deco to test directly at the source and compare the results? Directly from FIOS Router I get very good speeds
- Is your Internet source (e.g., modem, ONT, gateway) connected to the top, middle, or bottom port on the main Deco? Bottom
- Is the main Deco connected to a modem, or to a modem + router gateway device? Connection from street is: ONT - Verizon Router (CR1000b) - TP Link Switch - Deco Main Node. I have ethernet backhauls running from all nodes.
- Copy Link
- Report Inappropriate Content
@Ryan Any thoughts?
- Copy Link
- Report Inappropriate Content
One thing that caught my attention was the topology of your network (Verizon Router → Switch → Main Deco → Ethernet Backhaul to other Deco Nodes).
Is your Deco currently set up in Access Point Mode?
If it is not and is instead operating in Router Mode, this could introduce various network anomalies and performance resulting from a Double NAT scenario.
Generally, with two Routing devices in the same network (your Verizon gateway and the Deco Mesh System), you'd want to assign one as the network router/gateway and the other as a network passthrough device. This can typically take the form of one of the two following configurations:
Scenario 1: You want to use the Verizon gateway as your main router, and have the Deco simply provide Wi-Fi connectivity
- In this case, you would need to set the Deco in Access Point Mode (Note: doing this will disable some of the Deco's router-exclusive features).
Scenario 2: You would prefer the Deco as the primary router on your network
- In this case, you would bypass your Verizon gateway entirely and connect the main Deco to your ONT via Ethernet or set the Verizon gateway in pass-through mode, effectively turning off its routing features so the Deco can handle that for your network.
Is there anything else connected to the switch between the Verizon Router and Main Deco?
- Copy Link
- Report Inappropriate Content
@Ryan One correction. Not sure it makes a difference.
(Ethernet Backhaul to other Deco Nodes). is actually Ethernet backhaul back to switch.
I don't have Deco in Access Point Mode.
I do need to keep the Verizon Router's wifi on as it is needed for the TV Set Top boxes to work.
I have to give this some thought as to whether I want to operate the Deco in AP Mode or if I just want to use the Verizon Router + Extenders for coverage.
The Verizon router is connected directly to the switch and all devices (Deco's and my office PC basically) are connected to the switch.
- Copy Link
- Report Inappropriate Content
![](https://static-community.tp-link.com/icon/76483dd4f29041109d0ccb7481bb7d3e.jpeg)
I appreciate the additional info, and I can understand why you'd need to keep that Verizon gateway for your TV Set Top Boxes.
That said, if the Deco is in Router Mode, and your PC is connected to the switch, then all of the PC's network traffic will be routed through the Verizon router—not your Deco's network.
To provide a bit more context, with both routers in the network, anything connected directly to the Verizon router (whether via Ethernet to the Verizon router itself, or to its Wi-Fi network, or even via the switch) will be in a separate network from the devices connecting to the Deco.
Depending on how you want to use the Deco, and your network overall, this can potentially lead to devices not seeing each other on the LAN, or network speed and connectivity issues stemming from the Double NAT scenario.
If I understand correctly, it sounds like your current options are:
1. Verizon Router + Wi-Fi Extenders
2. Verizon Router + Decos in AP Mode
I strongly encourage trying the latter option, especially since your Deco nodes are already using Ethernet backhaul. Depending on their implementation, universal Wi-Fi extenders may introduce latency and bandwidth loss.
Are there any particular router-exclusive Deco settings you are currently using that you are concerned about losing if they are set in AP Mode?
- Copy Link
- Report Inappropriate Content
One more correction (I need to get my eyes checked!)
The topology is: Verizon Router to Deco then Backhaul from Deco to switch. Then everything else is connected to switch.
If I go w/ option #2. I need to keep the Verizon Router wifi going as one of my TV set top boxes can only use wifi and (I am told by Verizon) that it must be connected to the Verizon router to work properly. So the Verizon network SSID is different from the SSID of my Deco's. Can I / should I make them all the same SSID and password or keep them different?
I'd only use the Verizon wifi SSID for the set top box.
If I make both the same SSID and password is there any harm in keeping the Verizon extenders as well?
In regards to this question: "Are there any particular router-exclusive Deco settings you are currently using that you are concerned about losing if they are set in AP Mode?"
I don't beleive so. I do have a number of wifi switches (over 70) and I was weighing whether or not to put them on a separate IoT network. Although I haven't experienced any connectivity issues so far and having to change the SSID and password on all of those devices would be a pain.
- Copy Link
- Report Inappropriate Content
![](https://static-community.tp-link.com/icon/76483dd4f29041109d0ccb7481bb7d3e.jpeg)
Thanks for the topology clarification - it looks good, as far as I can tell.
Regarding your question about separating the SSIDs:
Separating the SSIDs would be in your best interest if you absolutely must keep the Wi-Fi network broadcasting on the Verizon gateway, and you're really only using it for those boxes and nothing else. This way, your TV boxes can connect to the gateway SSID, and everything else can connect to the Deco SSID.
Having the same SSID (assuming you assign the Verizon gateway SSID to the entire network) across both your Verizon gateway and the Decos could potentially invite roaming issues. However, the most likely concern would be the time involved in migrating all of your smart devices over to the Verizon SSID - if they're currently connected to the Deco SSID.
On a related note:
If your Deco Mesh is set in AP mode, it theoretically shouldn't matter if you connect them to your Deco SSID—unless Verizon has implemented some sort of unorthodox protocols in their boxes. In AP mode, the Decos will hand everything over to your gateway for routing purposes and shouldn't interfere with the communication between your boxes and the gateway - in theory. It might be worth reaching out and verifying this with a knowledgeable Verizon support rep.
As mentioned before, if your Deco is in Router Mode, that's a whole different story. It is highly advised against using this mode behind another router (Verizon gateway) if you don't use any specific Deco Router Mode features and your ISP needs you to keep your Verizon gateway as the primary router.
Regarding the IoT Network:
I honestly agree with your assessment on the IoT network in your case. The time required to move 70+ devices to a new SSID is simply not worth it if you haven't noticed any points of concern with them on your main network.
- Copy Link
- Report Inappropriate Content
@Ryan If I do this. Since it goes Verizon Router to Deco in AP to switch...will any devices like my office PC that is connected via ethernet to that switch, have any issues?
- Copy Link
- Report Inappropriate Content
![](https://static-community.tp-link.com/icon/76483dd4f29041109d0ccb7481bb7d3e.jpeg)
There shouldn't be any issues since, in that configuration, both the Decos and your switch are behind the router in terms of topology; everything connected to them will be within your router's LAN.
That said, I'd also recommend reading through our FAQ on Connecting Decos via Ethernet Backhaul. It contains examples of the various and flexible ways you can connect Decos in AP mode while using Ethernet as a backhaul (including one very similar to yours). It also has a handful of helpful troubleshooting recommendations — in the unlikely event that anything unexpected occurs.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 308
Replies: 11
Voters 0
No one has voted for it yet.