trafiic generation on ax53

trafiic generation on ax53

14 Reply
Re:trafiic generation on ax53
19 hours ago - last edited 15 hours ago

  @BartekBB 

 

The ideal solution would be a new FW releasse, but that's up to the TP-Link development team.

I'm just pointing to a possible mitigation, described in my previous post hyperlink. 

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue as a "Recommended Solution". Tips:149wubkkfoLmNDjDbiTxx4ZU8mpcMA5CJt
  0  
  0  
#12
Options
Re:trafiic generation on ax53
19 hours ago
I think this should be changed in FW, by enabling the option to disable DNS queries, or at least change it to a simple ping.
  0  
  0  
#13
Options
Re:trafiic generation on ax53
14 hours ago - last edited 14 hours ago

  @BartekBB 

 

For some domains the echo requests (pings) may haven't been allowed and that's why the preferred way to detect an Internet connectivity is the DNS resolution.

If this was helpful click on the arrow pointing upward to make it blue. If this solves your issue, click the star to make it blue as a "Recommended Solution". Tips:149wubkkfoLmNDjDbiTxx4ZU8mpcMA5CJt
  0  
  0  
#14
Options
Re:trafiic generation on ax53
6 hours ago
I don't want to seem ungrateful or arrogant, but this is another reason to switch either entirely to MikroTik or Ubiquiti... there's no situation like here where we accidentally discover something is happening outside our control when installing a firewall... The same thing with the re605x, no Ethernet backhaul. You can't ask TP-Link to implement the EasyMesh controller on a device operating in AP mode, or to use the Omada hardware controller for this... if there's hardware, it's a matter of software. On the other hand, I realize that my wants are probably only 1% of my total needs.
  0  
  0  
#15
Options