From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
# Ensure the {{package|wireshark}}, {{package|wireshark-gnome}} packages are installed. | # Ensure the {{package|wireshark}}, {{package|wireshark-gnome}} packages are installed. | ||
|actions= | |actions= | ||
# Add the current user to wireshark group: {{command|su -c 'usermod -a -G wireshark <username>'}} | # Add the current user <username> to wireshark group: {{command|su -c 'usermod -a -G wireshark <username>'}} | ||
# Start capturing network traffic on '''eth0''': {{command|wireshark -i eth0 -k}} | # Start capturing network traffic on '''eth0''': {{command|wireshark -i eth0 -k}} | ||
# Do some network activities, like go to some websites, ssh/ping a remote host. | # Do some network activities, like go to some websites, ssh/ping a remote host. | ||
Revision as of 07:45, 30 May 2011
Description
This test case tests the ability of Wireshark to capture and analyze network traffic.
Setup
- Ensure the
wireshark
How to test
- Add the current user <username> to wireshark group:
su -c 'usermod -a -G wireshark <username>' - Start capturing network traffic on eth0:
wireshark -i eth0 -k - Do some network activities, like go to some websites, ssh/ping a remote host.
- Stop capturing traffic.
- Save file as:
/tmp/test.pcap - Close Wireshark
- Open the saved file with Wireshark:
wireshark /tmp/test.pcap - Try to use the Filter eg: filter by HTTP, SSH etc...
- Try to use Follow TCP stream functionality.
- Close Wireshark
Expected Results
- You should see Wireshark capturing packets.
- Filter and Follow TCP stream should work.
- Wireshark should works as expected without crashes.