Semero wrote

(with some minor issues).

What are the "minor issues"? Thank you.

Hello,
I ask this beta version by email BUT i need the EU version ( not US ) , do you know if they have it ?

mrscientist wrote

What are the "minor issues"? Thank you.

The minor issues, at least two of them, has to do with ipv6. TP-Link for some reason block ICMPv6 packets, so it makes proper ipv6 usage an issue. Also, for 6to4 tunnel ipv6, tp-link does not let you specify your own ipv6 dns server, they instead force you to use google ipv6 dns; this is a problem for some people as opendns is faster.

Honestly, I'm just shocked by all the issues with TP-Link products. They are essentially misrepresenting the functionality of the products they sell. This is a lawsuit waiting to happen.

I did install the beta firmware and so far things appear to work OK.

Akin

You may contact them by email to check. I think they would check it out and find a solution for you even though there isn't one.

And... No cigars with US_beta_Archer_C3150v1_0.9.1_ 0.1_up_boot(170526)_2017-05- 27_10.33.57.bin

Just lost the 2.4 GHz wireless and the admin page was locked up. Had to reboot the box. Sigh...

Akin

Was sent US_beta_Archer_C3150v1_0.9.1_0.1_up_boot(170526)_2017-05-27_10.33.57 as well. Had to go back to 160707 - Wireless connection was ok, but my speeds took a big hit. I think whereas the current official firmware has MU-MIMO support, the beta takes it out...the option was gone in the settings (sys param -> sys tools). So they may fix one thing but the beta will definitely break another.

I'm getting pretty disgruntled on this crappy support. It's officially been over a year since the last update and TP-Link has admitted to knowing there are problems but are not doing anything about it. Either they need to fix it, or replace everyone's router with the V2. What good is a 2 year warranty if you're only going to support it for 1?

rolvy wrote

The minor issues, at least two of them, has to do with ipv6. TP-Link for some reason block ICMPv6 packets, so it makes proper ipv6 usage an issue. Also, for 6to4 tunnel ipv6, tp-link does not let you specify your own ipv6 dns server, they instead force you to use google ipv6 dns; this is a problem for some people as opendns is faster.

Honestly, I'm just shocked by all the issues with TP-Link products. They are essentially misrepresenting the functionality of the products they sell. This is a lawsuit waiting to happen.

I second this sentiment.

How did you know the ICMPv6 is blocked? Did you ping IPv6 address internally or externally?
Actually I found my C5400 V1 with old firmware has no option to put in ipv6 dns server manually.
I should try update to fix the signal disappearing issue.

Shield101 wrote

How did you know the ICMPv6 is blocked? Did you ping IPv6 address internally or externally?
Actually I found my C5400 V1 with old firmware has no option to put in ipv6 dns server manually.
I should try update to fix the signal disappearing issue.

I did a test using: http://ipv6-test.com & http://netalyzr.icsi.berkeley.edu