Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
If you mean "pair", you probably mean a request and reply pair?
Could post a scrubbed (rip our your IP using Snort or Netdude) dump somewhere? Else could you post a proper ASCII-fied packet from the dump for both?
I didn't think I was opening such a can of worms.... forget
the original question ...how can I scrub and/or ASCII-fied the packet dumps
that would be more important to learn .... thank you for your time
Well, that depends on what scrubbing it needs and your tools.
It's common for ppl to post packet dumps w/o their own network/whateverelse info, minimizing the risk of having more nosey ppl scanning your network, especially if you're dealing with (reporting) badly configured/vulnerable services.
If you have Snort, you can have it scrub a tcpdump for your $HOME_NET variable (option -B), which works well for streams, but if it's just one packet you're sending off you might as well scrub it using Netdude which can also fix the packet checksums.
To print a dump in ASCII, run it tru tcpdump (-r <dump>) and use -x -X to print a Hexadecimal *and* ASCII representation. If you don't want to wait for network/service translation add "-n -nn".
Of course you could as well do "tcpdump -r <infile> 'not icmp' | sed -e "s/11.22.33.44/my.network/g" > <outfile>".
Also note the "not icmp" between single quotes, that's called a BPF filter, with a syntax similar to how you would select following a TCP stream in Ethereal. It allows you to output only certain packets. read more in man tcpdump.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.