Different Broadcast behavior on Models TL-WR802N and TL-WR702N

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

Different Broadcast behavior on Models TL-WR802N and TL-WR702N

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Different Broadcast behavior on Models TL-WR802N and TL-WR702N
Different Broadcast behavior on Models TL-WR802N and TL-WR702N
2022-11-21 13:55:36
Model: TL-WR802N  
Hardware Version: V4
Firmware Version: 0.9.1 3.17 v0001.0 Build 200623 Rel.63672n

Hey there,

 

I have two Routers right now. TL-WR702N and TL-WR802N. They seem to be configured the same but they have a little bit different behavior when broadcast IP Addresses are used.

 

The router is used to get measured data of one or more sensors to mobile devices. These sensors provide their data as UDP Messages with a specific destination IP Address and Port. Configured parameters can be read by WebRequests and are stored as JSON files on each sensor. I have a mobile Application that performs specific tasks to connect to these sensors. First step is to read the JSON files, to get the configured IP and Port. Second Step is to open an UDP Client with that loaded configuration.

 

As long as i manually open an UPD Listener on my mobile device everything works fine, that means there is no problem on receiving UDP Messages with Broadcast IP configuration.

But when i want to get the configured parameters of the sensors my problem occurs but only on router TL-WR802N. Every try i did, the WebRequest returned wether Connection failed (No route to Host) or Timeout. Router TL-WR702N didn't had that kind of a problem.

(WebReuqest Address looks like this: "http://192.168.88.31/path/ETH1_DestinationIP.json")

 

For example: (Sensors, Router and Mobile device have Subnet mask 255.255.255.0)

Sensor 1 with IP Address 192.168.88.31, Destination IP Address 192.168.88.255, Destination Port 1500

Sensor 2 with IP Address 192.168.88.32, Destination IP Address 192.168.88.255, Destination Port 1700

TL-WR802N with Static IP Address 192.168.88.1

Mobile device with IP Address 192.168.88.151

 

When I perform a WebRequest on my mobile device to get the Destination IP of Sensor 1 or 2 only router WR702N is able to receive the JSON file.

 

If i change the configuration of the Sensors that they send their data directly to my mobile devices IP Address i can receive all files without a problem. If I use only one Sensor with Broadcast configuration, everything works fine as well.

 

Summarized:

one sensor with destination .255  -> Mobile device with IP .151 yes (TL-WR802N) yes (TL-WR702N)

two sensors with destination .151 -> Mobile device with IP .151 yes (TL-WR802N)  (TL-WR702N)

two sensors with destination .255 -> Mobile device with IP .151 no (TL-WR802N) ​​​​​​​ (TL-WR702N)

(two or more sensors with destination .255 -> Switch -> Laptop with IP .100 yes)

 

Sadfully TP Link doesn't sell routers TL-WR702N any more so i have to use the newer Version 802.

 

Does anyone know what WR802N could do different that the communication could be corrupted?

Btw: if i perform the same task in a webbrowser by entering the WebRequest Address directly, the same behavior is detectable.

 

​​​​​​​

 

  0      
  0      
#1
Options
1 Reply
Re:Different Broadcast behavior on Models TL-WR802N and TL-WR702N
2022-11-23 08:43:51

@NeanuenEfrael 

 

Thank you very much for detailed info.

 

Sorry that I'm not sure how do they handle the broadcast data on these two models, I would like to report this issue to our support engineers and would ask them to look into this further. They will contact you with your registered email address later. Please pay attention to your email box for follow-up.

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 EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX55V2 Supports WireGuard VPN, EasyMesh Ethernet Backhaul, IoT Network, Speed Limit,and More 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.
  2  
  2  
#2
Options

Information

Helpful: 0

Views: 580

Replies: 1

Related Articles