Deco Firmware 1.6.1 problem
My network setup consists of a router with two ports connecting to the Deco units on the first and second floors, and the second-floor Deco is wired to the third-floor Deco. All Deco units are in Access Point mode.
However, after upgrading the Deco X55 from version 1.4.1 to 1.6.1, I encountered an issue where not all Deco units could maintain wired connections.
Only the third-floor Deco and one of the first or second-floor units show as connected via Ethernet, while the other shows as connected via 2.4G.
Even if I switch the primary device, the other unit still shows a 2.4G connection.
Restarting both all units together or individually did not solve the problem.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
My Route is OPNSense,
But when my deco frimware on 1.4.1 all deco can show as connected via Ethernet
so i think the problem is on frimware 1.6.1
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the update.
Can I have pictures of the network map on the Deco APP, such as:
After that, please also help me submit the Deco APP log: How to submit Deco APP log
Does it help if we update to the latest 1.6.4 beta here:
Deco X50_V1_1.6.4 Boosted Network Stability for Smart Home Devices
Wait for your reply and best regards.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, yes, the current hardware could update to the latest 1.6.4 beta for Deco X50/X55_V1.0.
By the way, the APP log has been received.
Please let me know how the beta works.
Best regards.
- Copy Link
- Report Inappropriate Content
@David-TP
Hi!
I have Deco x50 (firmware version is 1.6.1) as general device.
Wireguard VPN Client is configured by configuration file.
It contains many routes in "allowed addresses".
This configuration file works on Windows and Android clients without problems with the allowed addresses. But in Deco I can add up to 8 allowed addresses. This is extremely small and does not allow me to solve my problem.
Is there a ready-made solution, how can I remove the limit on the number of allowed addresses in the client's wireguard configuration on my Deco x50?
Or the only way out is to return my Deco to seller and purchase a cheaper and more functional third-party router that will face Deco and connect to the VPN via configured routes?
- Copy Link
- Report Inappropriate Content
Hi, Thanks for the feedback.
Did you refer to "Allowed IP/clients" here:
How would you like to configure the Allowed IPs?
If you can share more configuration details, the engineer might be able to help us find a workaround.
Thanks again and best regards.
- Copy Link
- Report Inappropriate Content
Hello, i already try 1.6.4beta and works like 1.6.1
The problem still exists
And new problem my opnsense cant not run 1Gbps just can run 100Mbps
So i back to 1.6.1 and this problem is settle
- Copy Link
- Report Inappropriate Content
Hi!
I didn't configure the VPN server on Deco, I did configure the VPN client.
So, I load the configuration file and automatically put the allowed subnet addresses in the field that's marked on the image.
If more than 8 subnet addresses added in field "Allowed IPs" client configuration can't be saved.
I can manually add just 8 subnet addresses in "Allowed IPs". When 9th address was added button "Save" turns to disable mode.
That's all about Wireguard VPN.
I decided to solve the problem by configuring the OpenVPN client on Deco using the routes specified in the client configuration file (the subnets that should go through the VPN server).It works on PC and Android. But doesn't work on Deco - all traffic is routed to the VPN server. Thus, part of the client configuration is simply ignored by Deco.
Routes added to the client configuration by directive of the form "route 77.88.8.8 255.255.255.255."
I need a solution that will allow to add more than 100 routes to the VPN server, and let the rest traffic through the provider (like with a disabled VPN).
- Copy Link
- Report Inappropriate Content
@David-TP
I found something interesting in the Deco logs (still trying to solve the problem using the OpenVPN client).
1. Fri Feb 21 17:53:56 2025 user.notice : [openvpn]: Pushed option removed by filter: 'redirect-gateway def1 bypass-dhcp'
This means that the client implementation in Deco is able to process instructions that do not need to direct all traffic to the VPN server.
2. Fri Feb 21 17:53:56 2025 user.notice : [openvpn]: net_route_v4_add: 77.88.8.8/32 via 10.8.0.1 dev [NULL] table 250 metric 200
Fri Feb 21 17:53:56 2025 user.notice : [openvpn]: role:48
Fri Feb 21 17:53:56 2025 user.notice : [openvpn]: works as client, add route to table 250(vpn)
Fri Feb 21 17:53:56 2025 user.notice : [openvpn]: net_route_v4_add: 1.1.1.1/32 via 10.8.0.1 dev [NULL] table 250 metric 200
This means that Deco's client implementation can add routes.
However, both of these facts do not help in solving the problem. All traffic is still routed to the VPN server.
P.S. I updated the firmware to 1.6.4, unfortunately it didn't help...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 190
Replies: 9
Voters 1
