Different Broadcast behavior on Models TL-WR802N and TL-WR702N
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 (TL-WR802N) (TL-WR702N)
two sensors with destination .151 -> Mobile device with IP .151 (TL-WR802N) (TL-WR702N)
two sensors with destination .255 -> Mobile device with IP .151 (TL-WR802N) (TL-WR702N)
(two or more sensors with destination .255 -> Switch -> Laptop with IP .100 )
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.