Then the picture changes and you need to reassess the situation.

If you have confirmed you are tracing with the right interface and you have correctly typed your display filter, and you /still/ not seeing any packets, then the only thing to conclude is that those packets were never sent or received on your network interface. Then you should /only/ see packets with a source or destination port 8080. Monitor port versus network tap Sniffing 802.1Q VLAN tags. Once the trace has started, then you should be able to use type your filter (the /display/ filter) into the filter toolbar in the Wireshark interface. If you are only trying to capture network traffic between the machine running Wireshark or. Then select that interface and click the Start button. The capture filter you'd want would be udp port 1000. Those are implemented by libpcap/WinPcap, and (due to the way they're implemented, often in the kernel-mode networking stack) have limited capabilities, so their syntax is different. To do this quickly and simply, I would click Capture > Interfaces and confirm which interface is receiving packets. However i want to capture packets of only one port That's what capture filters are for. tcp port 8080 is /capture/ filter, but tcp.port = 8080 is /display/ filter.įirst thing I would confirm is that I am using the right interface. You have to decide whether to use a /capture/ filter or a /display/ filter - the syntax is different between those two filter types.

Wireshark capture com port