In this scenario, since LINE application only sends 1 UDP packet every 10 seconds, only 3 packets will be received in 30 seconds at most. The UDP default timeout on the naver-line application is set to 30 seconds by default. If 16 packets are not received, the session is not refreshed and the session is closed due to timeout. Seems to be a keepalive mechanism.īy design, once the TCP/UDP session is offloaded on PA 3050, 30 series firewalls, 16 packets will have to be received on the offloaded sessions within the default session timeout. Once this happens, the endpoints send one UDP packet approximately every 10 seconds to the server. Which means the UDP packets will be sent directly between 10.10.10.1 and 10.10.10.2.
Then they start exchanging the data packets directly between the private IP addresses. When both endpoints are in the same LAN network, a few seconds after the call has started the application detects that both endpoints are in the same LAN segment. Then there will be UDP based connections from both endpoints to server on which the data traffic is sent and received once the call is connected. SSL based connection on port 443 to the server is used as control connection from both the endpoints. The application is called naver-line as per Paloalto application database.īoth are behind a PA (3050, 3060 or 5000 series) firewall and connect to internet through the firewall using Dynamic IP and Port NAT.īased on the observed behaviour of this application, below is how it seems to work.
This applies to only to PA 3050, 3060 and PA 5000 series of firewalls. When Line application installed endpoints (both PC and Mobile Phones) are in the same LAN behind the PA firewall, the Audio/video calls between these endpoints get disconnected after about a minute or two.Ĭalls to other endpoints out to internet or from internet will not face any issue.
0 kommentar(er)
