312-50V11 · Question #137
Based on the below log, which of the following sentences are true? Mar 1, 2016, 7:33:28 AM 10.240.250.23 ?54373 10.249.253.15 - 22 tcp_ip
The correct answer is C. Application is SSH and 10.240.250.23 is the client and 10.249.253.15 is the server. The log entry shows destination port 22 (SSH) with 10.240.250.23 using an ephemeral source port, identifying it as the client connecting to the server at 10.249.253.15.
Question
Based on the below log, which of the following sentences are true? Mar 1, 2016, 7:33:28 AM 10.240.250.23 ?54373 10.249.253.15 - 22 tcp_ip
Options
- ASSH communications are encrypted it's impossible to know who is the client or the server
- BApplication is FTP and 10.240.250.23 is the client and 10.249.253.15 is the server
- CApplication is SSH and 10.240.250.23 is the client and 10.249.253.15 is the server
- DApplication is SSH and 10.240.250.23 is the server and 10.249.253.15 is the server
How the community answered
(36 responses)- A6% (2)
- B3% (1)
- C83% (30)
- D8% (3)
Why each option
The log entry shows destination port 22 (SSH) with 10.240.250.23 using an ephemeral source port, identifying it as the client connecting to the server at 10.249.253.15.
While SSH traffic is encrypted, the log metadata - including source IP, destination IP, and destination port - is visible in network logs and clearly identifies both endpoints and the protocol.
FTP uses ports 20 and 21, not port 22; the log shows destination port 22 which is SSH, not FTP.
Port 22 is the well-known port for SSH (Secure Shell). In a TCP connection log, the host using the high ephemeral source port (54373) is always the initiating client, while the host listening on the well-known service port (22) is the server. Therefore 10.240.250.23 is the SSH client and 10.249.253.15 is the SSH server.
10.249.253.15 is the server (listening on port 22) and 10.240.250.23 is the client (using ephemeral port 54373); the answer incorrectly labels 10.240.250.23 as the server.
Concept tested: Network log analysis and SSH port identification
Source: https://www.rfc-editor.org/rfc/rfc4251
Topics
Community Discussion
No community discussion yet for this question.