Skip to content
This repository has been archived by the owner on Aug 29, 2024. It is now read-only.

Latest commit

 

History

History
36 lines (21 loc) · 1.75 KB

CONTRIBUTING.md

File metadata and controls

36 lines (21 loc) · 1.75 KB

Contributing Guidelines for buptLab-protocol

Welcome to the buptLab-protocol repository! We appreciate your interest in contributing to this project. Below are some guidelines to help you get started:

How to Contribute

  1. Fork the Repository: Start by forking this repository to your own GitHub account.

  2. Clone the Repository: Clone the forked repository to your local machine using git clone.

  3. Create a New Branch: Before making any changes, create a new branch for your work. Use a descriptive name for the branch (e.g., feature/add-protocol-description).

  4. Make Changes: Add or modify content related to the protocols, data, or any other relevant information. Ensure that your changes align with the purpose of this repository.

  5. Commit and Push: Commit your changes with clear and concise commit messages. Push your changes to your forked repository.

  6. Submit a Pull Request (PR): Open a pull request from your branch to the main repository. Provide a detailed description of your changes and any relevant context.

Directory Structure

The protocol_data/ directory contains protocol data packets for the following network protocols:

  • arp.pcapng: ARP (Address Resolution Protocol) packets.
  • dhcp.pcapng: DHCP (Dynamic Host Configuration Protocol) packets.
  • icmp-l.pcapng: ICMP (Internet Control Message Protocol) packets (large size).
  • icmp.pcapng: ICMP packets.
  • tcp.pcapng: TCP (Transmission Control Protocol) packets.
  • tcp_retransmission.pcapng: TCP packets with retransmissions.

Feel free to explore and contribute to any of these protocol data files!

Contact

If you have any questions or need assistance, feel free to contact the maintainers or open an issue.

Thank you for contributing to buptLab-protocol!