[WireShark] shows only headers ? or even encapsulated Data ?
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Have you set the limit box to 60 bytes or some such? by default it will capture all the traffic. On the main wireshark screen you have three panels right? the bottom one shows the entire packet in hex, and the middle splits out the protocols, which the payload being at the bottom of the middle pane, IF it can decode what the payload is.
I'm using default settings, when I decode the pay load. Click on a perticular bit, it tells me which part of the header it belongs to , like this is the MAC , this is IP bit and so on. But every bit is related to the header. There isn't where it actually says Data.
Like it does in this windows application Packet Analyzer - Colasoft Capsa 6.9
I'd be confident the data is there, never seen that from any default wireshark install in windows or linux. expand ALL the entries in the middle pane and take a screenshot of what's at the bottom of that page and upload it somewhere for us. are you sure there actually IS amounts of decodeable data in the traffic your looking at?
Well, I did see the payload, must be something else. But not having a payload raises a question for me. If i am working on encryption and i want my Box to only accept encrypted packets. The acknowledgements and everything will not be encrypted, wouldn't that present a network delima?
Well you can't only accept "encrypted" packets as they take many forms at many layers. I'm not sure what dilema you're talking about here. in the case of HTTPS for example, the encrpytion is at session layer (SSL), not transport (TCP) so the network traffic looks the same until you really start devling into the payload.