EAP650 dropping IPv6 traffic
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have an EAP650 AP and an EAP245 AP. Both APs are connected to the same switch, have the same trunk (port profile) settings, the same WLAN and VLAN settings, pretty much everything is the same. Clients roam between the two APs and use both IPv4 and IPv6.
When clients connect to the EAP245 IPv4 and IPv6 traffic is working as expected, however, when clients connect via the EAP650 AP, all IPv6 traffic is dropped and I can't work out why!?! I have ruled out any issues with the router, VLANs, or WLAN configuration - everything is the same (other than the model of the APs and the physical port they are connected to on the switch).
I have also tried the latest Beta firmware for the EAP650, but it doesn't fix the issue.
Any ideas?
Thanks.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I checked again with my EAP650 and wireshark. As soon as I receive a RA and the device gets its IPv6, traffic is partially(?) blocked. TCP connection opens (I see the 3-way handshake, SYN, SYN/ACK, ACK) but the following HTTP requests to any server are not answered. I see TCP retransmissions with the same request until it fails. IPv4 works fine and as soon I connect to my EAP245 on the same SSID and port (everything else is untouched) I have no problems with IPv6 connections.
- Copy Link
- Report Inappropriate Content
Quick update: I had an interactive support session with TP-Link support this week. They collected some tcp dumps from the EAP250. Seems they think the problem is related to hardware offloading. No ETA on a fix.
Probably a good idea for others with the same issue to log a support case if you haven't already.
- Copy Link
- Report Inappropriate Content
I'm still wondering if only hardware rev. v1.0 is affected. Does anyone experience those issues with revisions v1.20 or v1.26?
- Copy Link
- Report Inappropriate Content
@CuBiC I know you're asking about the EAP650, but in any case my EAP670 model is shown as "EAP670(US) v1.0" (on the controller web page) with a hardware revision of v1.20 (as shown on the back of the unit) and it has this problem.
- Copy Link
- Report Inappropriate Content
Good news! TP-Link support sent me another beta firmware yesterday and it appears to resolve the issue. Clients can now obtain DHCPv6 leases when connected to my EAP650. Not sure how long it will take for the fix to be included in general release firmware.
- Copy Link
- Report Inappropriate Content
Great...I'm willing to test on an EAP670 if needed. Thanks for the update...hopefully it doesn't linger like that last patch has. Cheers.
- Copy Link
- Report Inappropriate Content
Seems like TP-Link does only test with their beta-users.
The R&D team must be really really small.
What about the actual EAP650 Beta version? It is still from August this year! Last final more than half a year old.
Don't know, if we will see any new final within this year. So sad to see.
- Copy Link
- Report Inappropriate Content
Since it looks like it's going to be months before they release this, can you tell me how you went about opening a ticket on this particular issue so I can do the same?
Thanks!
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
GPB wrote
Since it looks like it's going to be months before they release this, can you tell me how you went about opening a ticket on this particular issue so I can do the same?
Thanks!
BTW, firmware 1.0.6 was released a few days ago, https://www.tp-link.com/en/support/download/eap650/v1/#Firmware
I haven't installed it yet so I don't know if it includes a fix for the issue in this thread.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 6486
Replies: 42
Voters 1
