WOL (Wake On LAN) issues with Archer BE3600
WOL (Wake On LAN) issues with Archer BE3600
Hello,
I just bought an Archer BE3600 because it was the only one around with two actual 2.5Gbps ports. After i finished configuring all my settings i found out that WOL is not working on my PC anymore.
What's funny is that if the PC is on and i inspect the packets with wireshark i see the magic packet coming correctly and i even put back the old router to check and from there it works so the issue is caused by the new TP Link router.
Has anyone ever encountered this issue? Does TP-link put th eports in an "offline" state somehow ?
My configuration has DHCP static reservations and from what i can see the ARP table has the IP associated to the MAC address but i went anyway and made a static bing from the "Security > IP & MAC Binding" Menu
Furthermore i read on some forums to try disabling the IGMP proxy but still nothing.
Powersaving is in "Normal" so i cant assume it shuts down the ports when the PC is off
Device isolation is of course off else i wouldn't be able to access my NAS, server, and other devices on the network.
At this point im pretty sure it's a firmware issue and a total deal breaker and was thinking of returning the router.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
I handled to find the problem with the support. All my settings were correct but the 2.5G port does not support link down speed of 10Mbps so in the wake on lan settings on my PC I had to put the link speed to 100Mbps when hibernating for WOL. You can confirm the behavior by shutting down the PC and check on the network map menu of the router the port link speed. For the 1G the negotiation goes to 10Mbps and for the 2.5G goes in a disconnected state.
The 1G ports work fine on my end with the old settings.
You just need ARP reservation in the router like my screenshots above.
This is my port now with the PC off and after I changed the link speed.
This is where I set the WOL link speed on the PC
PS they told me it's a hardware issue and cannot be fixed by firmware. The 2.5G ports won't support 10Mbps
- Copy Link
- Report Inappropriate Content
We've also published a solution in the following thread. If anyone else encounters this similar issue, please check it out:
Wi-Fi Routers' 2.5G/10G LAN ports do not support 10Mbps negotiation, leading to Wake on LAN failure
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi, thanks for the link but my setup is already like that and it does not work. Also you cannot put ARP binding and DHCP reservation at the same time, it throws an error
You can either add a reservation or bind the IP in the other menu, both don't work either way.
this is the ARP bind
As i said the magic packet is properly broadcasted and received by the PC when it's on.
Pretty sure im going to return it and go back to the old router, too bad, this was the only valid modem in the that price range with 2 x 2.5GBps ports
- Copy Link
- Report Inappropriate Content
I'm sorry to hear that WOL/WOW isn't working as expected.
To assist you further, could you please provide some details? I would like to escalate your case to our support engineers for further investigation:
1. Were you trying to wake up the PC from the local network or a remote network? Based on your provided information, I assume it's from the local network, but I want to confirm.
2. You swapped the old router with the new BE3600 without changing the network topology, correct?
- Copy Link
- Report Inappropriate Content
Hi, yes the WoL is being sent from the local network from my home assistant instance and it works properly because I see the packet on the PC.
The only thing I changed was the network IP from a 192.168.1.0/24 to 10.10.0.10/24 but I tried plugging the old Technicolor router and it works when configured the same way and with the same IP on the PC. (Either way I even reset the BE3600 to default configuration with the standard subnet and still didn't work)
Test made:
WoL sent to the PC from TP-Link not working, changed the Ethernet cable to the old router and the PC turned on. Same IP same Mac address.
- Copy Link
- Report Inappropriate Content
Got you. There seem to be no issues with your settings.
To assist and figure it out efficiently, I've forwarded your case to the TP-Link support engineers who will contact you with your registered email address later. Please pay attention to your email box for follow-up. Thank you.
- Copy Link
- Report Inappropriate Content
Hi,
I just bought the Archer BE3600 myself yesterday, have it all set up with everything except WOL is not working for me either.
I'm just wondering if there was a resolution to this at all? It is running the latest firmware. I had WOL working previously with an ISP-specific TP-Link VX420 router which I could have kept using except it turns out it had an upload speed restriction of 20mbps and my new plan is 100mbps so had to buy a new router. Settings are identical to OP and my previous router - I have static IP addresses signed to two local PCs and the IP/ARP bindings set. Ports are forwarded for WoL as per my previous setup with NAT routing.
- Copy Link
- Report Inappropriate Content
Hi,
I handled to find the problem with the support. All my settings were correct but the 2.5G port does not support link down speed of 10Mbps so in the wake on lan settings on my PC I had to put the link speed to 100Mbps when hibernating for WOL. You can confirm the behavior by shutting down the PC and check on the network map menu of the router the port link speed. For the 1G the negotiation goes to 10Mbps and for the 2.5G goes in a disconnected state.
The 1G ports work fine on my end with the old settings.
You just need ARP reservation in the router like my screenshots above.
This is my port now with the PC off and after I changed the link speed.
This is where I set the WOL link speed on the PC
PS they told me it's a hardware issue and cannot be fixed by firmware. The 2.5G ports won't support 10Mbps
- Copy Link
- Report Inappropriate Content
Unfortunately hasn't helped. I have two PCs which I connect to the LAN and made the change on both. Interestingly though WoL isn't working within the LAN so I'll double check to make sure I haven't missed anything obvious.
- Copy Link
- Report Inappropriate Content
can't post the link but search for "wake on lan monitor" on the site "Depicus". download and put port 9 UDP and start the sniffing. Now send the WOL packet, if the destination is correct you should see the magic packet. On my end i sent the command from my home assistant instance and from command line on my phone with Termux and the wakeonlan python lib for the testings with the support.
- Copy Link
- Report Inappropriate Content
Thanks for that suggestion. The sniffer app has revealed that one of my wake up commands is coming in on random ports (not the one I've designed) and the other just isn't coming in at all. Don't seem to be picking up the commands that are supposed to be sent in on port 7 at all. So I'll try an alternative WoL app and see how that one goes
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 508
Replies: 12