Home Network CommunityDecoVPN on Deco BE65 not working after update.
Deco

VPN on Deco BE65 not working after update.

VPN on Deco BE65 not working after update.

VPN on Deco BE65 not working after update.
VPN on Deco BE65 not working after update.
Saturday
Tags: #Firmware Update #VPN
Model: Deco BE65  
Hardware Version: V2
Firmware Version: 1.3.2_build_26040912_rel_40631

Hello everyone!

I'm here to ask for help with a problem I'm facing. My deco was running version 1-2-0-P1[20250718-rel43949]_2025-07-18_20.48.38

because the version released in February had a problem for me regarding VPNs. Well, I saw there was a new update and decided to test it to see if the problem still persisted, in this case, this latest release launched in May 2026. And to my surprise, the problem still continues.

But what is the problem?

I have a Wireguard VPN configured on a Raspberry Pi 5, which is on the same network as the deco. Before the update, the VPN connection worked normally. I use this approach because on the Pi I have more than one VPN connected, and on the deco I can't connect two VPNs at the same time.

I really don't know what to do, I desperately need this to work again. I saw that it's not possible to downgrade, so I'm opening this forum for help.

0
0
#1
7 Reply
Re:VPN on Deco BE65 not working after update.
Saturday
Additional information: Before updating the firmware, I was using the Deco's built-in WireGuard VPN client. Through this VPN connection, all devices connected to my Deco network were able to access resources on my Tailscale tailnet without any issues. My setup includes a Raspberry Pi 5 connected to the same local network as the Deco. This Raspberry Pi is connected to my Tailscale tailnet, allowing devices behind the Deco to reach other Tailscale-connected devices and networks. After updating to firmware 1.3.2_build_26040912_rel_40631, this functionality stopped working. The WireGuard VPN connection on the Deco appears to establish successfully, and the status shows as connected. However, devices on my local network can no longer access any resources on the Tailscale tailnet. In addition, it seems that Internet connectivity is also affected when the WireGuard VPN is enabled. Although the VPN appears to connect successfully, devices behind the Deco are unable to reach the Internet as expected. This makes it seem as if traffic is no longer being routed correctly through the VPN connection. The exact same configuration worked correctly before the firmware update, and no changes were made to the Raspberry Pi, Tailscale, or WireGuard configurations. The only change was the Deco firmware upgrade. Could someone from TP-Link please confirm whether there were any routing, NAT, firewall, or VPN-related changes in recent firmware versions that could explain this behavior?
0
0
#2
Re:VPN on Deco BE65 not working after update.
Saturday

Logs on Deco:

 

Sat May 30 13:26:29 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:32 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:35 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:36 2026 daemon.err tmpsvr[13720]: Error: tmp_trans_relay

Sat May 30 13:26:38 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:41 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:43 2026 daemon.err tmpsvr[13720]: Error: tmp_trans_relay

Sat May 30 13:26:45 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:48 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:49 2026 daemon.err client_mgmt_arp: Invalid ip addr 192.168.3.71. start_ip: C0A80364, ind: 4294967267. Return NULL ping state.

Sat May 30 13:26:51 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:53 2026 daemon.err nrd[9742]: ar_pat_fill_stainfo[line 151]: Failed to find serving BSS for 4A6EBB8C1715

Sat May 30 13:26:53 2026 daemon.err nrd[9742]: ar_pat_fill_stainfo[line 142]: Failed to find entry in stadb!

Sat May 30 13:26:53 2026 daemon.err nrd[9742]: ar_pat_fill_stainfo[line 151]: Failed to find serving BSS for 2C9975EF579A

Sat May 30 13:26:53 2026 daemon.err nrd[9742]: ar_pat_fill_stainfo[line 151]: Failed to find serving BSS for 723EF95D393A

Sat May 30 13:26:53 2026 daemon.err nrd[9742]: ar_pat_fill_stainfo[line 151]: Failed to find serving BSS for 1EE39FF41C75

Sat May 30 13:26:53 2026 daemon.err nrd[9742]: ar_pat_fill_stainfo[line 151]: Failed to find serving BSS for 9AD742C4A84A

Sat May 30 13:26:54 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:57 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:57 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:57 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:57 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:26:58 2026 daemon.err udhcpd[10597]: Received SIGTERM

Sat May 30 13:26:59 2026 user.emerg : tp211,501[22494]:

Sat May 30 13:26:59 2026 user.emerg : tp211,501[22494]:

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: udhcpd (v1.22.1) started

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: start ip 0xc0a80364, end ip 0xc0a803fa, subnet:0xffffff00

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8038f

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80380

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80369

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8037c

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80365

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8038e

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80381

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80389

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8038b

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80377

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8037d

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80367

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8037e

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80378

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80364

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80347

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8036a

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8036e

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80370

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80372

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80375

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8038a

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8036c

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80368

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80391

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8036f

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8036d

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80374

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a803fa

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80373

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8037b

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80394

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80376

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8037a

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80379

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80385

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80395

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80388

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a80371

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8037f

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8036b

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: lease ip: 0xc0a8038c

Sat May 30 13:27:00 2026 daemon.err udhcpd[23820]: udhcpd response_fd = 6

 

Sat May 30 13:27:00 2026 daemon.err miniupnpd[11805]: ioctl(s, SIOCGIFADDR, ...): Address not available

Sat May 30 13:27:00 2026 daemon.err miniupnpd[11805]: ioctl(s, SIOCGIFADDR, ...): Address not available

Sat May 30 13:27:00 2026 daemon.err miniupnpd[11805]: Failed to get IP for interface share-internet

Sat May 30 13:27:00 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:27:00 2026 daemon.err pppd[6701]: Failed to disconnect PPPoE socket: 114 Operation already in progress

Sat May 30 13:27:01 2026 daemon.err conn-indicator: [send_query] Failed to send DNS query: Network unreachable

Sat May 30 13:27:01 2026 cron.err crond[19618]: user root: parse error at 2026

Sat May 30 13:27:02 2026 user.emerg : tp211,501[24592]:

Sat May 30 13:27:02 2026 user.emerg : tp211,501[24592]:

Sat May 30 13:27:02 2026 user.emerg : tp219,606[24592]:

Sat May 30 13:27:03 2026 daemon.err /usr/bin/apsd: loop_avoidance_configure_bridge_with_mode:459: Error: configure hyfi bridge with mode FAP

Sat May 30 13:27:03 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:27:03 2026 user.emerg : tp217,505[26147]:

Sat May 30 13:27:03 2026 user.emerg : tp217,504[26147]:

Sat May 30 13:27:04 2026 daemon.err conn-indicator: [send_query] Failed to send DNS query: Network unreachable

Sat May 30 13:27:05 2026 user.emerg : tp279,508[27096]:

Sat May 30 13:27:05 2026 daemon.err udhcpd[23820]: Received SIGTERM

Sat May 30 13:27:06 2026 user.emerg : tp211,501[27180]:

Sat May 30 13:27:06 2026 daemon.err wandetect3: fopen /tmp/access_mode failed.

Sat May 30 13:27:06 2026 user.emerg : tp211,501[27180]:

Sat May 30 13:27:07 2026 daemon.err cloud-brd: set response error

Sat May 30 13:27:07 2026 user.emerg : tp219,606[27180]:

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: udhcpd (v1.22.1) started

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: start ip 0xc0a80364, end ip 0xc0a803fa, subnet:0xffffff00

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: lease ip: 0xc0a8038c

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: lease ip: 0xc0a8036b

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: lease ip: 0xc0a8037f

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: lease ip: 0xc0a80371

Sat May 30 13:27:07 2026 daemon.err udhcpd[28649]: lease ip: 0xc0a80388

0
0
#3
Re:VPN on Deco BE65 not working after update.
Saturday

I discovered something interesting. The VPN is only working on the main deco. In the satellite decos it has this behavior that I reported above. 

0
0
#4
Re:VPN on Deco BE65 not working after update.
Sunday

  @Delfanti 

 

Sorry for the late reply. There is a way to revert back to the older firmware but if you can deal with it for a few more days I would like you to submit your deco app log first which will open up a ticket on this.

 

Please use the directions in the following post. How to submit Deco APP log

 

Once it's open you should get an email with a TKID number please respond back to this post with that number,

 

Thanks 

Need help with the Deco app, setup, Ethernet backhaul, network switch or rolling back firmware? Router or AP mode? https://community.tp-link.com/us/home/forum/topic/699816?page=1
1
1
#5
Re:VPN on Deco BE65 not working after update.
18 hours ago

  @HelpFixDecoApp 

 

Hello!

 

I completed the process you requested yesterday; however, I still haven't received the email you mentioned.

0
0
#6
Re:VPN on Deco BE65 not working after update.
8 hours ago

  @HelpFixDecoApp 

protocolo Nº TP20260601028894

MDK28937T539305953

0
0
#7
Re:VPN on Deco BE65 not working after update.
an hour ago

  @Delfanti 

Hi, 
Please try turning off the main Deco and the satellite Deco, waiting for 10 seconds, turning them back on, and checking whether the devices connected to the satellite Deco can access the Tailscale tailnet.

 

If the same phenomenon persists, please confirm the following information.
  1. On the Deco app > Network tab, please tap a Deco, and send us the screenshots of the Show Map and Show List pages.
  2. Whether the client devices can connect to the satellite Deco's Wi-Fi, but can't access the Tailscale tailnet, and can't go to the internet?
  3. What's the LED status on the satellite Deco?
 

Best Regards

>> Check What's Currently Going on With Deco >> Deco Wi-Fi Heatmap ready for all Deco models
0
0
#8

Information

Helpful: 0

Views: 143

Replies: 7

Tags

Firmware Update VPN
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.