MENU
By default, Wireshark will only dissect port 443 traffic as SSL/TLS traffic. If you are using another port for SSL/TLS communications, you must add that port number in the HTTP preferences setting for SSL/TLS ports.
Suggested Answer: A
Get Premium WCNA Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
BR
Brock
10 months ago
Yup, I've had to change that setting before.
MA
Matthew
11 months ago
False! Wireshark can handle other ports without extra settings.
WI
Wilda
11 months ago
Wait, really? I thought it would auto-detect other ports too.
VA
Valentin
11 months ago
Totally agree, you have to add other ports manually.
MA
Martina
11 months ago
That's true, only port 443 is dissected by default.
BR
Brynn
12 months ago
I thought Wireshark automatically detects SSL/TLS on any port, but now I'm questioning if that's correct.
SH
Sheridan
12 months ago
I believe it's true, but I might be mixing it up with how other tools handle SSL/TLS traffic.
JE
Jennifer
12 months ago
I'm not entirely sure, but I feel like I saw a similar question about default ports in one of the practice exams.
VA
Val
1 year ago
I think this is true because I remember something about configuring ports in Wireshark settings.
ET
Ethan
1 year ago
Ah, I see. So Wireshark has a default setting to only recognize SSL/TLS traffic on port 443. But if I'm using a different port for my SSL/TLS communications, I'll need to manually add that port to the preferences. Good to know!
KA
Karon
1 year ago
I've got this! The key is that Wireshark only dissects port 443 traffic as SSL/TLS by default. So if I'm using a different port, I need to add that port number in the HTTP preferences setting for SSL/TLS ports. Easy peasy!
KA
Karina
1 year ago
Wait, I'm a little confused. Does that mean Wireshark won't recognize SSL/TLS traffic on any ports other than 443 unless I specify them? I need to make sure I have that right.
AL
Alecia
1 year ago
Okay, I think I understand this. Wireshark doesn't automatically recognize SSL/TLS traffic on ports other than 443, so I'll need to manually add those ports in the preferences.
JE
Jeannine
1 year ago
Hmm, this seems straightforward. I just need to remember that Wireshark only dissects port 443 traffic as SSL/TLS by default, so I'll need to add any other ports I'm using for SSL/TLS communications.
TO
Tonette
2 years ago
This is why I always carry a magic 8-ball with me during exams. It would've told me the answer in a much more entertaining way.
JO
Joseph
2 years ago
B) False
LO
Lorean
2 years ago
A) True
JO
Johnna
2 years ago
Hmm, I thought Wireshark was supposed to be the all-knowing network analysis tool. Guess it has its limitations when it comes to SSL/TLS.
RI
Ria
2 years ago
B) False
RI
Ria
2 years ago
A) True
EM
Emogene
2 years ago
Ah, I see. So if I'm using a custom port for my secure communication, I'll need to manually configure that in Wireshark. Good to know!
LI
Lisha
2 years ago
Wait, Wireshark doesn't automatically detect all SSL/TLS ports? That's a bit of a bummer.
EA
Earlean
2 years ago
I didn't know that, thanks for the heads up!
MA
Margret
2 years ago
B) False
JE
Jerilyn
2 years ago
Yeah, you have to manually add the port numbers in the preferences.
DY
Dylan
2 years ago
A) True
FR
Francis
2 years ago
I think it's true because Wireshark needs to know which ports to dissect for SSL/TLS traffic.
SH
Sharen
2 years ago
B) False
FR
Francis
2 years ago
A) True