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
EAP653 seems also be effected. I wrote a ticket some minutes ago.
- Copy Link
- Report Inappropriate Content
I also have the EAP650 v1.0 and EAP245v3 and can confirm EAP650 IPv6 conections seem not to work (tested on 1.0.3 and current linked beta). I wonder if only v1.0 is affected.
- Copy Link
- Report Inappropriate Content
FYI, TP-Link support sent me another beta firmware today that was supposed to fix the issue (1.0.0 Build 20221028 Rel. 54577). It doesn't work for me though. It seems to allow DHCPv6 Advertise packets to be transmitted now, but not DHCPv6 Reply packets, so clients still can't get a DHCPv6 lease... 
- Copy Link
- Report Inappropriate Content
Thanks, the update is much appreciated. I was wondering if they were being responsive. Cheers!
- Copy Link
- Report Inappropriate Content
Assuming the 670 and 650 have similar f/w...ipv6 works fine on the 670 except for the delay in getting an ipv6 address. I'm running the beta f/w mentioned at the top of this forum. I use SLAAC and no dhpv6 server. Receiving an ipv6 address can vary depending on how often your frequent router advertisements occur. Maybe it's different on a TPL Omada router, but in OPNsense, I can set the interval.
- Copy Link
- Report Inappropriate Content
I haven't captured traffic yet to investigate that fully since there is already a report, but I definitely experience problems with IPv6 traffic being fully dropped. Possibly it's after some specific circumstances in the configuration?
The delay you mention is not a result of the RA interval, but because your EAP seems to drop the Router Solicitation your client sends to trigger a Router Advertisement. There's no need to lower the interval for SLAAC to work under normal circumstances. So seems you lose some multicast traffic at least.
- Copy Link
- Report Inappropriate Content
CuBiC wrote
The delay you mention is not a result of the RA interval, but because your EAP seems to drop the Router Solicitation your client sends to trigger a Router Advertisement. There's no need to lower the interval for SLAAC to work under normal circumstances. So seems you lose some multicast traffic at least.
I agree with this point. I run both DHCPv6 (for ULAs) and SLAAC (for GUAs). When clients connect via my EAP245, SLAAC is relatively instant, whereas it can be a minute or so when connected via the EAP650 AP.
- Copy Link
- Report Inappropriate Content
codersr wrote
That's what I see here as well. That's why I suspected it was related to only the solicitation is getting dropped (i.e., the router never receives it). The periodic non-solicited advertisement broadcast seems to get through. It sounds like @CuBiC is having additional issues. I'm no expert in ipv6 so maybe I'm misunderstanding what I'm seeing. Hopefully this is resolved soon.
- Copy Link
- Report Inappropriate Content
I've been evaluating the EAP670 and I'm quite happy with it, but I also have run into this same bug. Using Wireshark I can see that the Router Solicitation messages from the client are being dropped by the access point.
As it seems the Router Advertisement messages are sent to the client without any problem, my workaround for the moment is to set the Router Advertisement Interval to 3-4 seconds. This delay is not very noticable to the user, but it does create unnecessary traffic.
- Copy Link
- Report Inappropriate Content
Finally got around to configuring the IPv6 on the setup, and yes, I'm also facing this issue.
Even once I'm able to get an IPv6 address over the WiFi distributed by the EAP650 (with the TCP bugfix firmware installed) the IPv6 Traffic is not flowing. Connecting only via the switch IPv6 connections work as expected.
@Fae , is there any ongoing work due to this and other possible known issues?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 9121
Replies: 42
Voters 1
