jfunk wrote

  @Kevin_Z 

 

Want to chime in that after reverting to 116 I can confirm that the game detection just appears to be broken on 121.  On 121, it doesn't seem to detect when there are games active on the PCs (either plugged into the dedicated game port or manually added to the list).  When it does detect a game is launched, it tends to list it as some generic thing like "Unreal Engine" and it doesn't stay active.  Lists sessions of only a few Kb and only a couple minutes when the game was being played much longer.

Definitely concerning to see the primary feature of the product getting broken by a firmware update.  Is gaming prioritization no longer a focus of the product's ongoing development?  It's clear nobody tested it during the 116 to 121 changes.

 

 

Hello @jfunk, thanks for chiming in and providing your feedback.

The gaming feature is, of course, the most important feature that we're actively working on and improving. The development team did test it thoroughly to make it workable as expected on every release. However, there are cases where it is enabled for a particular environment that is unpredictable for the testing team.

I found you have an open thread/topic reporting the gaming issue you're experiencing with the new official 1.2.1 version. We will keep discussing on that topic instead of this one, since this thread is mainly open for the pre-released AI QoS feature of Archer GE800.

Pro-gamer wrote

Hello, if a router is vulnerable and does not have DDoS security, the router can easily be hacked, broken and seen everything including internet IP addresses and connected devices. That's why TP-Link should add DDoS security to its latest gaming router for free, just like Asus even modem providers give free security. why we buy router because latest technology and more options features

@Pro-gamer  @jfunk  @Bauhaus Thank you all for your feedback on the DDoS Protection feature on the GE800.

All of your feedback has been brought to the attention of our decision-makers, and I hope they will consider it seriously.

Gogolithic wrote

 

Gogolithic wrote

  @Kevin_Z I saw this issue even on older versions, I started using this router when it was version 1.1.5 then upgraded to 1.1.6 and issue was still there. No firmware update has changed anything related to this.

 

Every device that is on the 5Ghz band fails if the router has been powered on for days without a wall disconnect, I first noticied this issue on the FireTV Cube of my living room, I wanted to have the full signal (router is in my room) and the 6Ghz band wasn't strong enough so I opted for 5Ghz, same issue as with my Nintendo: videos stopped buffering, home page saying there's no internet connection, etc. The fix was to change the device to 6Ghz.

 

When the device fails:

 

- Still appears on client list

- Signal icon appears (on Nintendo Switch 2 home)

- Ping to gateway and Google DNS doesn't seem to work

 

And yes, I was refering to physically pull the power away from the router by pulling the cable from the wall or pushing the ON/OFF button, wait 10 seconds and then power it on again.

 

@Kevin_Z Any solution to my previous message? Thank you.

@Gogolithic Apologize for missing your response. I thought I responded to you earlier.

When the game freezes/disconnects, can you please check the 5G signal strength on the client devices? Is the signal not good enough to keep an active connection?

Additionally, please specify what 5G client devices you're using at that time. Are they all encountering a disconnect/freeze at the same time?

ATypicalYeti wrote

Any eta on the new firmware for stable release? As I have a strange issue where clients show as unknown with 1.2.1 on my ge800, and I'm hoping the new firmware corrects the problem. Also could you pass on the request for ipv6 dns link local addresses? Thanks for your time.  @Kevin_Z 

@ATypicalYeti 

Thank you very much for your feedback.

What kind of devices are shown as unknown on the GE800? Did they show up correctly on the previous 1.1.6 official version?

If you would like, you can upgrade to the 1.2.2 beta firmware to observe if it corrects the client display issue.

Regarding the 'ipv6 dns link local addresses', could you please provide more details about your specific requests?

@ATypicalYeti 

ATypicalYeti wrote

  @Kevin_Z  So it's all clients that show as unknown and yes it did work fine on 1.1.6

 

I'll try and load up the beta firmware this weekend and test when I have time to do so.

Kevin: Please let me know how the 1.2.2 pre-release firmware works then. Thank you.

ATypicalYeti wrote

The ipv6 dns link local address is for using a local client to host dns requests.

For example it currently only allows global addresses in the input field such as "2001:db8::1234:5678:9abc:def0".

I'd like to use a link local ipv6 dns address "fe80::1234:5678:9abc:def0". *These are example addresses only.

Kevin: This feature is not supported yet. We have received this feature request on other models, as seen in this thread. And we've brought it forward to the relevant team for consideration. You can also vote on that thread.