Home Network Community > All Threads > e4 mDNS flood
< All Threads

e4 mDNS flood

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

e4 mDNS flood

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
e4 mDNS flood
e4 mDNS flood
2020-04-06 07:02:36 - last edited 2020-04-07 06:58:25

The e4 in AP mode send's out a mDNS in-addr.arpa. request every 20th second. I'm not sure if these are only sent on the ethernet or also on the wireless side, currently I'm not able to capture network traffic on a wifi device in order to test that.

 

The requests are not only for associated WiFi clients, the requests are sent for all IP's seen on the local network.

 

09:03:01.767859 IP 192.168.0.245.44228 > 224.0.0.251.5353: 20761 PTR (QM)? 192.168.0.145.in-addr.arpa. (44)
09:03:21.065314 IP 192.168.0.245.57329 > 224.0.0.251.5353: 20781 PTR (QM)? 192.168.0.145.in-addr.arpa. (44)
09:03:41.207972 IP 192.168.0.245.42390 > 224.0.0.251.5353: 20801 PTR (QM)? 192.168.0.145.in-addr.arpa. (44)
 

Could this be stopped in the next firmware?

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:e4 mDNS flood-Solution
2020-04-07 06:58:04 - last edited 2020-04-07 06:58:25

@6b6561 

 

Hi, this mDNS in-addr.arpa. request is normal, it is used to indicate the local DNS, displaying the corresponding relations between the domain name of local devices and its IP address. 

 

Good day. 

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
Recommended Solution
  0  
  0  
#2
Options
2 Reply
Re:e4 mDNS flood-Solution
2020-04-07 06:58:04 - last edited 2020-04-07 06:58:25

@6b6561 

 

Hi, this mDNS in-addr.arpa. request is normal, it is used to indicate the local DNS, displaying the corresponding relations between the domain name of local devices and its IP address. 

 

Good day. 

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
Recommended Solution
  0  
  0  
#2
Options
Re:e4 mDNS flood
2020-04-07 07:08:34

I understand that a in-addr.arpa. request are done when a new device appears on the network, but running the request every 20s for all seen hosts on the network is not good practice. In addition to this there is a lot of netbios-ns requests that are sent periodically on the network.

 

 

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 941

Replies: 2

Related Articles
Igmp flood
1900 0
Flood of DNS requests to NTP server
4909 1
E4
456 0
Archer C2300 DHCP flood
2155 0
mDNS and Bonjour via Powerline
524 0
mDNS setting
812 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.