Analysing the requests packet by packet may not give us the desired result we want when packets are encrypted with SSL/TLS. Since security is a big concern for organizations, they add a security layer to their applications. After following routine steps, if we can not fix the problem, we may need to analyse the requests packet by packet.ĪLSO READ: Configure VRRP using Keepalived and Cisco’s Router with Examples If we get a reply from the client, we measure latency with ping round trip time, if everything is ok with reaching the client, we move to the next step which could be checking firewall rules for upper layer protocols for ssl/tls or other protocols. Network and system administrators first check the routine procedures.įor example checking client reachability by ping is one of the first thing to do. Sometimes, we hear complaints from our clients(end users) about how slow the network or the server is. End users(clients) mostly use their browsers as client application to interact with the server. In return, the server processes the request and return an answer back. A Client creates a request and sends it to the server. In modern days, most of applications used in an organization are web based and in Client/Server architecture. Getting started with Wireshark to Decrypt SSL/TLS
0 kommentar(er)
